RFC 8788: Eligibility for the 2020-2021 Nominating Committee
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9389.
Current document in this lineage: RFC 9389 — Nominating Committee Eligibility
In plain English — editorial summary, not part of the RFC
The 2020-2021 Nominating Committee (NomCom) is to be formed between the IETF 107 and IETF 108 meetings, 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 any rules or processes that relate to NomCom eligibility before IETF 108; it does not set a precedent to be applied in the future.
Document record
- Document ID
- RFC8788
- Published
- May 2020
- Authors
- B. Leiba
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 5
- Also known as
- —
- Obsoleted by:
- RFC 9389
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 8788 (2020)
- RFC 8989 (2021)
- RFC 9389 (2023) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8318IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: IAOC Advisor for the Nominating CommitteeObsoleted
January 2018
- RFC 7437IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
January 2015
- RFC 6859Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF LeadershipObsoleted
January 2013
- RFC 5078IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees TimelineObsoleted
October 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?