[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [ietf-nomcom Home]
Subject: RE: deadlock problem
> ISOC BoT have for *years* been following an RFC-specified > confirmation > process that does not appear to be in its bylaws. The bylaws specify voting procedures in general. The formal adoption of the ISOC Board's role in the nomination process is a resolution of the Board of Trustees: Resolution 98-03 Selection of IAB and IESG members. RESOLVED, that the Board accepts the process for selection of IAB and IESG members, as documented in RFC 2282, and accepts the role of the Board described in this process. This resolution amends the previous state, references to the "poised" documents adopted in 1992 and 1993. Presumably, when the new RFC is published, the board will review it. In fact, if an RFC specifies an ISOC action, the ISOC board will be part of the last call. > At best, your claim is late in the day -- years late. If IAB or > ISOC really had heartache over this (and I can say that the IAB had > *no* anxiety > about it during my 4 years on the IAB and I heard zero individual > complaints > about it), that REALLY should have been raised years ago (e.g. at any > of the > IAB Chair transitions or when the first RFC on Nomcom procedures was > published). Well, I have witnessed "some" anxiety, as in last minute phone conferences to make sure that the slate was voted on in time. > And I'll note that if you adhere to the position you outline above > (i.e. that how a confirming body decides stuff is their concern only), > then this WG should delete the current text and ought not be discussing > "the way we manage indecision". My point is that the RFC should not mention specific voting rules, e.g. simple majority rather than consensus or whatever else the confirmation body sees as appropriate. > As to how to do indecision, I think that boils down to (A) or (C) > versus (B) or (D). I can live with any of those 4. All of A, B, C and D have the drawback that they specify a voting rule. I would rather go for a choice between (E) and (F): (Proposal E) For a given nominee to be confirmed, an explicit confirmation by the confirming body is required. Nominees that are not confirmed under this rule are considered to be rejected. xor (Proposal F) For a given nominee to be rejected, an explicit rejection by the confirming body is required. Nominees that are not confirmed under this rule are considered to be confirmed. How the confirming bodies arrive to explicit confirmation or implicit rejection is their own cooking. -- Christian Huitema
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [ietf-nomcom Home]
Powered by eList eXpress LLC