IETF Administrative Support Activity 2.0: Consolidated Updates to IETF Administrative Terminology
RFC 8717
Document | Type | RFC - Best Current Practice (February 2020) | |
---|---|---|---|
Author | Dr. John C. Klensin | ||
Last updated | 2020-02-27 | ||
Replaces | draft-klensin-iasa2-2418upd-5377upd | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Jon Peterson | ||
Shepherd write-up | Show Last changed 2019-03-13 | ||
IESG | IESG state | RFC 8717 (Best Current Practice) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | Alissa Cooper | ||
IESG note | |||
Send notices to | Jon Peterson <jon.peterson@neustar.biz> | ||
IANA | IANA review state | IANA OK - No Actions Needed | |
IANA action state | No IANA Actions |
RFC 8717
Internet Engineering Task Force (IETF) J. Klensin, Ed. Request for Comments: 8717 February 2020 BCP: 101 Updates: 2028, 2418, 3005, 3710, 3929, 4633, 6702 Category: Best Current Practice ISSN: 2070-1721 IETF Administrative Support Activity 2.0: Consolidated Updates to IETF Administrative Terminology Abstract 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. Status of This Memo This memo documents an Internet Best Current Practice. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8717. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction 2. Where Appropriate, Replacement of the IETF Executive Director Position with the Managing Director, IETF Secretariat 3. Removal of the IETF Executive Director as an Option 4. Deprecated Documents 4.1. Documents Whose Context Is Changed by This Specification 4.2. General Description of the IETF Administrative Model 5. Security Considerations 6. References 6.1. Normative References 6.2. Informative References Acknowledgments Contributors Author's Address 1. Introduction 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 [RFC8711]. Key IASA 2.0 changes have been specified in a series of documents, including changes to the IETF Trust [RFC8714], the rationale for it [RFC8715], a new defining document for the IETF Administration LLC [LLC-Agreement] (informally called the "IETF LLC" or just "the LLC" in places in this document and elsewhere), and adjustments to the procedures for nominations and selections for relevant positions [RFC8713]. In addition to more substantive changes that are described in those and other documents, the IASA 2.0 structure changes several position titles and organizational relationships that are referenced in other documents. Rather than reissue those documents individually, this document provides a unified update to them. This document updates RFCs 2028, 2418, 3005, 3710, 3929, 4633, and 6702 (citations in context below) to make those terminology and related changes. In addition, with the authorization of the IAB, it requests that the Informational RFC 3716 be made Historic (see Section 4). The sections that follow identify the details of the relevant documents and the required changes. 2. Where Appropriate, Replacement of the IETF Executive Director Position with the Managing Director, IETF Secretariat Under the IASA 2.0 structure, most of the responsibilities of the former position of IETF Executive Director have been assigned to a new position (or at least title) of Managing Director, IETF Secretariat. An "Executive Director" title is now associated with different, and largely new, responsibilities as an officer of the IETF Administration LLC. These changes are covered in the description of the new structural arrangements [RFC8711].