UpdatedBEST CURRENT PRACTICEIETF streamBCP10

RFC 8713: IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees

Still current, but amended. Parts of this document are changed or extended by RFC 9389. Read both.

In plain English — editorial summary, not part of the RFC

The process by which the members of the IAB and IESG, some Trustees of the IETF Trust, and some Directors of the IETF Administration LLC (IETF LLC) are selected, confirmed, and recalled is specified in this document. This document is based on RFC 7437. Only those updates required to reflect the changes introduced by IETF Administrative Support Activity (IASA) 2.0 have been included. Any other changes will be addressed in future documents. This document obsoletes RFC 7437 and RFC 8318.

Document record

Document ID
RFC8713
Published
February 2020
Authors
M. Kucherawy; R. Hinden; J. Livingood
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
gen
Pages
33
Also known as
BCP10
Obsoletes:
RFC 7437, RFC 8318
Updated by:
RFC 9389

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/8713-iab-iesg-ietf-trust-and-ietf-llc-selection-confirmation-and-recall-process-opera