Hi, Thanks to Barry for putting this together and to the IESG for pushing it forwards. I support publication as an RFC. Two small comments: one of substance, one a trivial edit. Cheers, Adrian == I may have missed it in the discussion, but... If we have to form a recall committee in the period before we have worked out a long-term solution, I presume the same rules will apply. I think it would be wise to fill this hole now because if we need it (which we won't) then we'll need to sort it out in a real hurry. I think we can do this with simple edits such as the following. OTOH, if this was already discussed and discarded, then just say so and we can move on. Abstract OLD This document only affects the seating of the 2020-2021 NomCom, and does not set a precedent for the future. NEW This document only affects the seating of the 2020-2021 NomCom and the formation of any recall Committee before the end of IETF 108, and does not set a precedent for the future. END Section 1 OLD The 2020-2021 Nominating Committee (NomCom) needs to be formed between IETF 107 and IETF 108, and the issue of eligibility of who can serve on that NomCom needs clarification: a one-time interpretation of the eligibility rules is required for this particular exceptional situation, given the tight timeframe for seating this year's NomCom. NEW The 2020-2021 Nominating Committee (NomCom) needs to be formed between IETF 107 and IETF 108, and the issue of eligibility of who can serve on that NomCom needs clarification. Similarly, there is the possibility that a Recall Committee will need to be formed before IETF 108. A one-time interpretation of the eligibility rules is required for this particular exceptional situation. END Section 3 OLD This update is an emergency interpretation of the intent of BCP 10 for this current exceptional situation only, and applies only to the 2020-2021 NomCom, which is expected to be seated prior to IETF 108. It will explicitly not apply to any future NomCom and does not set precedent: another update to BCP 10 will be necessary to address future eligibility, as there will be time for proper community work on such an update. NEW This update is an emergency interpretation of the intent of BCP 10 for this current exceptional situation only, and applies only to the 2020-2021 NomCom, which is expected to be seated prior to IETF 108, And to the creation of any Recall Committee that may need to be Seated before IETF 108. It will explicitly not apply to any future NomCom or Recall Committee and does not set precedent: another update to BCP 10 will be necessary to address future eligibility, as there will be time for proper community work on such an update. END --- Minor edit Section 3 s/another update/an update/ -- -----Original Message----- From: IETF-Announce <ietf-announce-bounces@xxxxxxxx> On Behalf Of The IESG Sent: 02 April 2020 18:25 To: IETF-Announce <ietf-announce@xxxxxxxx> Cc: draft-iesg-nomcom-eligibility-2020@xxxxxxxx Subject: Last Call: <draft-iesg-nomcom-eligibility-2020-00.txt> (Eligibility for the 2020-2021 Nominating Committee) to Best Current Practice The IESG has received a request from an individual submitter to consider the following document: - 'Eligibility for the 2020-2021 Nominating Committee' <draft-iesg-nomcom-eligibility-2020-00.txt> as Best Current Practice The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@xxxxxxxx mailing lists by 2020-04-30. Exceptionally, comments may be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The 2020-2021 Nominating Committee (NomCom) needs to be formed between IETF 107 and IETF 108, and the issue of eligibility of who can serve on that NomCom needs clarification. This document provides a one-time interpretation of the eligibility rules that is required for the exceptional situation of the cancellation of the in-person IETF 107 meeting. This document only affects the seating of the 2020-2021 NomCom, and does not set a precedent for the future. The file can be obtained via https://datatracker.ietf.org/doc/draft-iesg-nomcom-eligibility-2020/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-iesg-nomcom-eligibility-2020/ballot/ No IPR declarations have been submitted directly on this I-D. _______________________________________________ IETF-Announce mailing list IETF-Announce@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf-announce -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
