On Wednesday, September 06, 2006 02:08:06 PM -0700 "Hallam-Baker, Phillip"
<pbaker(_at_)verisign(_dot_)com> wrote:
One simple fix here would be to publish the list on IETF announce BEFORE
it goes to the secretariat and to ONLY use that list regardless of
whether people are excluded or not.
I like that approach; it's straightforward and easy to analyze.
This still leaves the question of what to do if people were left off the
list and need to be added in.
Yes; that's a hard one. The most common/likely failures can be handled by
publishing the list twice, and allowing anyone to add their name at any
time prior to the second publication. Anyone who wants to be sure they are
added will submit their name before the first publication, and check to
insure they are listed.
However, that doesn't prevent a person from being excluded due to malicious
interference or unusual communication problems. One possible answer would
be to allow multiple entities to publish lists of volunteers (say, the
Nomcom chair, the IETF secretariat, and the ISOC President), and use the
union of the published lists (which any party can easily compute). Under
this model, volunteers would normally be expected to submit their names as
usual to the Nomcom chair, but if they are then omitted from the first
list, would submit again to all three sources.
Once this is done, the selection process consists of computing the union of
the published lists, sorting according to a canonical order, and applying
RFC3797 until enough candidates have been selected.
Another safeguard that can be put in place here is to date the choice of
random seeds a fixed time after the list is posted.
What purpose would this requirement serve?
-- Jeff
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf