RFC 2282: IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2727.
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
The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2282
- Published
- February 1998
- Authors
- J. Galvin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- gen
- Pages
- 14
- 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 3177IAB/IESG Recommendations on IPv6 Address Allocations to SitesObsoleted
September 2001
- RFC 2130The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996Updated
April 1997
- RFC 2101IPv4 Address Behaviour TodayCurrent
February 1997
- RFC 2031IETF-ISOC relationshipObsoleted
October 1996
- RFC 2028The Organizations Involved in the IETF Standards ProcessObsoleted
October 1996
- RFC 1862Report of the IAB Workshop on Internet Information Infrastructure, October 12-14, 1994Current
November 1995
- RFC 2777Publicly Verifiable Nomcom Random SelectionObsoleted
February 2000
- RFC 2902Overview of the 1998 IAB Routing WorkshopCurrent
August 2000
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?