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, 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
- 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.
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 8711Structure of the IETF Administrative Support Activity, Version 2.0Current
February 2020
- RFC 8717IETF Administrative Support Activity 2.0: Consolidated Updates to IETF Administrative TerminologyCurrent
February 2020
- RFC 8712The IETF-ISOC RelationshipCurrent
February 2020
- RFC 8715IETF Administrative Support Activity 2.0: Update to the Process for Selection of Trustees for the IETF TrustCurrent
February 2020
- RFC 8718IETF Plenary Meeting Venue Selection ProcessUpdated
February 2020
- RFC 8719High-Level Guidance for the Meeting Policy of the IETFUpdated
February 2020
- RFC 8721Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF DocumentsCurrent
February 2020
- RFC 8728RFC Editor Model (Version 2)Obsoleted
February 2020
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?