RFC 8318: IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: IAOC Advisor for the Nominating Committee
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8713.
Current document in this lineage: RFC 8713 — IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees
In plain English — editorial summary, not part of the RFC
This specification formalizes an ad hoc practice used to provide advice to the IETF Nominating Committee (NomCom) about the operations of the IETF Administrative Oversight Committee (IAOC). This document updates RFC 7437.
Document record
- Document ID
- RFC8318
- Published
- January 2018
- Authors
- S. Dawkins
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 11 RFCs, each formally replacing the one before it.
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 6859Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF LeadershipObsoleted
January 2013
- RFC 8716Update to the IETF Anti-Harassment Procedures for the Replacement of the IETF Administrative Oversight Committee (IAOC) with the IETF Administration LLCCurrent
February 2020
- RFC 8788Eligibility for the 2020-2021 Nominating CommitteeObsoleted
May 2020
- RFC 9389Nominating Committee EligibilityCurrent
April 2023
- RFC 5078IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees TimelineObsoleted
October 2007
- RFC 4071Structure of the IETF Administrative Support Activity (IASA)Obsoleted
April 2005
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?