IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees
This specification has been revised 10 times since RFC 2027 (1996). Each document below formally obsoleted the one before it; the versions still in force are listed first.
Revision timeline
Current version — implement against this
Superseded versions — historical reference only
- RFC 2027IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoletedOctober 1996informationalreplaced by RFC2282
- RFC 2282IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoletedFebruary 1998informationalreplaced by RFC2727
- RFC 2727IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoletedFebruary 2000best current practicereplaced by RFC3777
- RFC 3777IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoletedJune 2004best current practicereplaced by RFC7437
- RFC 5078IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees TimelineObsoletedOctober 2007informationalreplaced by RFC7437
- RFC 5633Nominating Committee Process: Earlier Announcement of Open Positions and Solicitation of VolunteersObsoletedAugust 2009best current practicereplaced by RFC7437
- RFC 5680The Nominating Committee Process: Open Disclosure of Willing NomineesObsoletedOctober 2009best current practicereplaced by RFC7437
- RFC 6859Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF LeadershipObsoletedJanuary 2013best current practicereplaced by RFC7437
- RFC 7437IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoletedJanuary 2015best current practicereplaced by RFC8713
- RFC 8318IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: IAOC Advisor for the Nominating CommitteeObsoletedJanuary 2018best current practicereplaced by RFC8713
This lineage is derived automatically from the “obsoletes” relationships recorded in the public RFC Editor index — no editorial judgement is applied to the ordering. The most recent document in the chain is RFC 8713 (February 2020).