1770 Massachusetts Ave, Ste 322 Cambridge MA 02140 USA +1 617 245 1457 john-ietf@jck.com

General IASA2 IASA 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 .

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 () 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

• .  Introduction
• .  Where Appropriate, Replacement of the IETF Executive Director Position with the Managing Director, IETF Secretariat
• .  Removal of the IETF Executive Director as an Option
• .  Deprecated Documents
  • .  Documents Whose Context Is Changed by This Specification
  • .  General Description of the IETF Administrative Model
• .  Security Considerations
• .  References
  • .  Normative References
  • .  Informative References
• Acknowledgments
• Contributors
• Author's Address

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 . Key IASA 2.0 changes have been specified in a series of documents, including changes to the IETF Trust , the rationale for it , a new defining document for the IETF Administration LLC (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 . 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 ). The sections that follow identify the details of the relevant documents and the required changes.

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 . This document applies that change to the following:

• RFC 2028, "The Organizations Involved in the IETF Standards Process", .
• RFC 2418, "IETF Working Group Guidelines and Procedures", .
• RFC 3710, "An IESG Charter", .
• RFC 3929, "Alternative Decision Making Processes for Consensus-Blocked Decisions in the IETF", , Sections and (twice).
• RFC 4633, "Experiment in Long-Term Suspensions From Internet Engineering Task Force (IETF) Mailing Lists", .
• RFC 6702, "Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules", .

Note that the current description of the Internet Standards Process does not require an update by this document for this purpose because the reference to the IETF Executive Director in RFC 2026 was replaced by a document that precedes the current effort, and that document was, in turn, obsoleted by RFC 8179.

Removal of the IETF Executive Director as an Option In a few cases, it is no longer appropriate for either the Managing Director, IETF Secretariat (former IETF Executive Director position) or the new IETF Executive Director (for the LLC) to perform a particular historical function. The relevant documents are updated to remove the IETF Executive Director from the list of people with specific responsibilities or authority. Those documents will not be updated to use "Managing Director, IETF Secretariat" but, instead, the mention of the position will simply be dropped. This document applies that change to the following:

• RFC 3005, "IETF Discussion List Charter" , section titled "Charter for the IETF Discussion List". This document is modified to remove the authorization for the IETF Executive Director to restrict people from posting, etc.

Deprecated Documents

Documents Whose Context Is Changed by This Specification Both of the documents that follow were obsoleted in 2017 by RFC 8179, which changed mentions of the IETF Executive Director to point to the IETF Secretariat more generally.

• RFC 3979
• RFC 4879

General Description of the IETF Administrative Model RFC 3716 was a report of an IAB Advisory Committee that served as a starting point for the work that led to the original IASA structure. That report was an IAB document rather than an IETF one. The IAB approved a proposal to move RFC 3716 to Historic on March 6, 2019 .

Security Considerations The changes specified in this document are matters of terminology and organizational structure derived from documents it references. It should have no effect on Internet security.

References Normative References IETF Administration LLC This document describes the individuals and organizations involved in the IETF. This includes descriptions of the IESG, the IETF Working Groups and the relationship between the IETF and the Internet Society. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document describes the guidelines and procedures for formation and operation of IETF working groups. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. The Internet Engineering Task Force (IETF) discussion mailing list furthers the development and specification of Internet technology through discussion of technical issues, and hosts discussions of IETF direction, policy, meetings, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This memo provides a charter for the Internet Engineering Steering Group (IESG), a management function of the Internet Engineering Task Force (IETF). It is meant to document the charter of the IESG as it is presently understood. This memo provides information for the Internet community. The disclosure process for intellectual property rights (IPR) in documents produced within the IETF stream is essential to the accurate development of community consensus. However, this process is not always followed by IETF participants. Regardless of the cause or motivation, noncompliance with IPR disclosure rules can delay or even derail completion of IETF specifications. This document describes some strategies for promoting compliance with the IPR disclosure rules. These strategies are primarily intended for use by area directors, working group chairs, and working group secretaries. This document is not an Internet Standards Track specification; it is published for informational purposes. Informative References Internet Architecture Board This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. IAB Advisory Committee In the fall of 2003, the IETF Chair and the IAB Chair formed an IAB Advisory Committee (AdvComm), with a mandate to review the existing IETF administrative structure and relationships (RFC Editor, IETF Secretariat, IANA) and to propose changes to the IETF management process or structure to improve the overall functioning of the IETF. The AdvComm mandate did not include the standards process itself. This memo provides information for the Internet community. This document proposes an experimental set of alternative decision-making processes for use in IETF working groups. There are a small number of cases in IETF working groups in which the group has come to consensus that a particular decision must be made but cannot agree on the decision itself. This document describes alternative mechanisms for reaching a decision in those cases. This is not meant to provide an exhaustive list, but to provide a known set of tools that can be used when needed. This memo defines an Experimental Protocol for the Internet community. The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information about any IPR constraints on a technical proposal as possible. The policies are also intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders. This memo details the IETF policies concerning IPR related to technology worked on within the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026 and, with RFC 3978, replaces Section 10 of RFC 2026. This memo also updates paragraph 4 of Section 3.2 of RFC 2028, for all purposes, including reference [2] in RFC 2418. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Discussion in the community has begun to question whether RFC 3683 and RFC 3934 provide the appropriate flexibility for managing Internet Engineering Task Force (IETF) mailing lists. This document is an RFC 3933 experiment designed to allow the community to experiment with a broader set of tools for mailing list management while trying to determine what the long-term guidelines should be. This memo defines an Experimental Protocol for the Internet community. This document clarifies and updates a single sentence in RFC 3979. Specifically, when third party Intellectual Property Rights (IPR) disclosures are made, the intention is that the IETF Executive Director notify the IPR holder that a third party disclosure has been filed, and to ask the IPR holder whether they have any disclosure that needs to be made, per applicable RFC 3979 rules. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information as possible about any IPR constraints on a technical proposal as early as possible in the development process. The policies are intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders. This document sets out the IETF policies concerning IPR related to technology worked on within the IETF. It also describes the objectives that the policies are designed to meet. This document updates RFC 2026 and, with RFC 5378, replaces Section 10 of RFC 2026. This document also obsoletes RFCs 3979 and 4879.

Acknowledgments careful checking and identification of documents that did, and did not, require consideration was essential to the document in its current form. He also made several other significant contributions. also gave the document a careful reading and made useful suggestions. In additional to the above, , , (the RFC Series Editor), and the current membership to the IAB helped sort out the handing of RFC 3716.

Contributors did the hard work of identifying the documents that required updating and supplied considerable text used in this document.

Author's Address

1770 Massachusetts Ave, Ste 322 Cambridge MA 02140 USA +1 617 245 1457 john-ietf@jck.com