Skip to main content

Nominating Committee Eligibility
RFC 9389 part of BCP 10

Revision differences

Document history

Date By Action
2023-12-12
(System) Imported membership of rfc9389 in bcp10 via sync to the rfc-index
2023-12-12
(System) No history of BCP10 is currently available in the datatracker before this point
2023-04-28
(System)
Received changes through RFC Editor sync (created alias RFC 9389, changed abstract to 'The IETF Nominating Committee (NomCom) appoints candidates to several IETF leadership …
Received changes through RFC Editor sync (created alias RFC 9389, changed abstract to 'The IETF Nominating Committee (NomCom) appoints candidates to several IETF leadership committees.  RFC 8713 provides criteria for NomCom membership that attempt to ensure NomCom volunteers are members of the loosely defined IETF community, by requiring in-person attendance in three of the past five in-person meetings.  In 2020 and 2021, the IETF had six consecutive fully online plenary meetings that drove rapid advancement in remote meeting technologies and procedures, including an experiment that included remote attendance for NomCom eligibility.  This document updates RFC 8713 by defining a new set of eligibility criteria from first principles, with consideration to the increased salience of remote attendance.  This document obsoletes RFCs 8788 and 8989.', changed pages to 9, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2023-04-28, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-elegy-rfc8989bis and RFC 8788, created obsoletes relation between draft-ietf-elegy-rfc8989bis and RFC 8989, created updates relation between draft-ietf-elegy-rfc8989bis and RFC 8713)
2023-04-28
(System) RFC published