RFC 8717: IETF Administrative Support Activity 2.0: Consolidated Updates to IETF Administrative Terminology
In plain English — editorial summary, not part of the RFC
In 2018, the IETF began the transition to a new administrative structure and updated its IETF Administrative Support Activity (IASA) to a new "IASA 2.0" structure. In addition to more substantive changes that are described in other documents, the transition to the 2018 IETF Administrative Support structure changes several position titles and organizational relationships that are referenced elsewhere. Rather than reissue those referencing documents individually, this specification provides updates to them and deprecates some now-obsolete documents to ensure that there is no confusion due to these changes.
Document record
- Document ID
- RFC8717
- Published
- February 2020
- Authors
- J. Klensin
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- gen
- Pages
- 7
- Also known as
- BCP101
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8713IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall CommitteesUpdated
February 2020
- RFC 8711Structure of the IETF Administrative Support Activity, Version 2.0Current
February 2020
- RFC 8718IETF Plenary Meeting Venue Selection ProcessUpdated
February 2020
- RFC 8715IETF Administrative Support Activity 2.0: Update to the Process for Selection of Trustees for the IETF TrustCurrent
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 8712The IETF-ISOC RelationshipCurrent
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?