ObsoletedINFORMATIONALIETF stream

RFC 2027: 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 2282.

Current document in this lineage: RFC 8713IAB, 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 has been exercised four times since its formal creation. The evolution of the process has relied principally on oral tradition as a means by which the lessons learned could be passed on to successive committees. This document is a self-consistent, organized compilation of the process as it is known today. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC2027
Published
October 1996
Authors
J. Galvin
Status
INFORMATIONAL
Stream
IETF
Area
gen
Pages
11
Also known as
Obsoleted by:
RFC 2282

Topics

Standards lineage

This document is one revision in a chain of 11 RFCs, each formally replacing the one before it.

  1. RFC 2027 (1996)
  2. RFC 2282 (1998)
  3. RFC 2727 (2000)
  4. RFC 3777 (2004)
  5. RFC 5078 (2007)
  6. RFC 5633 (2009)
  7. RFC 5680 (2009)
  8. RFC 6859 (2013)
  9. RFC 7437 (2015)
  10. RFC 8318 (2018)
  11. RFC 8713 (2020)

Read the full history of IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees

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.

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?

canonical URL: /rfc/2027-iab-and-iesg-selection-confirmation-and-recall-process-operation-of-the-nominati