IASA2 J. Klensin, Ed.
Internet-Draft March 11, 2019
Updates: 2028, 2418, 3005, 3710, 3929,
4633, 6702 (if approved)
Intended status: Best Current Practice
Expires: September 12, 2019

Consolidated IASA 2.0 Updates of IETF Administrative Terminology


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 Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on September 12, 2019.

Copyright Notice

Copyright (c) 2019 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

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 [RFC-Struct]. Key IASA 2.0 changes have been specified in a series of documents, including changes to the IETF Trust [RFC-trust-update], the rationale for it [RFC-trust-rationale], 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 [RFC-7437bis].

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 been assigned to a new position (or at least title) of Managing Director of the 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 described in the description of the new structural arrangements [RFC-Struct].

This document applies that change to the following:

Note that the current description of the Internet Standards Process [RFC2026] 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 [RFC3979] and that was, in turn, obsoleted by RFC 8179.

3. Remove 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:

4. Deprecated Documents

[CREF1]Note to the WG, IESG, and RFC Editor: I hope this section correctly reflects the conclusions of discussions in and with the WG. If it does not, the issues should certainly be identified and fixed. However, details of some of the actions are the responsibility of the RFC Editor and RFC 3716 is an IAB document containing the report of an IAB Advisory Committee. If that text, especially the phrasing of various actions, is not quite right, I hope those involved can sort the language out with the RFC Editor rather than requiring that the WG iterate on the draft. --JcK, editor. RFC Editor: should this paragraph reach you, please remove it.

4.1. 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.

4.2. General Description of the IETF Adminstrative Model

RFC 3716 is 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 is an IAB document rather than an IETF one. The IAB approved a proposal to move RFC 3716 to Historic on March 6, 2019.

5. Acknowledgments

Brian Carpenter's careful checking and identification of documents that did, and did not, require consideration was essential to the draft in its current form. He also made several other significant contributions. Bob Hinden also gave the document a careful reading and made useful suggestions. In additional to the above, Alissa Cooper, Eliot Lear, Heather Flanagan (the RFC Series Editor), and the current membership to the IAB helped sort out the handing of RFC 3716.

6. Contributors

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

7. IANA Considerations

[CREF2]RFC Editor: Please remove this section before publication.

This memo includes no requests to or actions for IANA.

8. 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.

9. References

9.1. Normative References

[LLC-Agreement] IETF Administration LLC, "Limited Liability Company Agreement of IETF Administration LLC", August 2018.
[RFC-7437bis] Kucherawy, M., Hinden, R. and J. Livingood, "IAB, IESG, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees", 2018.
[RFC-Struct] Haberman, B., Hall, J. and J. Livingood, "Structure of the IETF Administrative Support Activity, Version 2.0", December 2018.
[RFC-trust-rationale] Arkko, J., "Discussion of the IASA 2.0 Changes as They Relate to the IETF Trust", 2018.
[RFC-trust-update] Arkko, J. and T. Hardie, "Update to the Process for Selection of Trustees for the IETF Trust", 2018.
[RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, DOI 10.17487/RFC2028, October 1996.
[RFC2418] Bradner, S., "IETF Working Group Guidelines and Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418, September 1998.
[RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, RFC 3005, DOI 10.17487/RFC3005, November 2000.
[RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, DOI 10.17487/RFC3710, February 2004.
[RFC6702] Polk, T. and P. Saint-Andre, "Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules", RFC 6702, DOI 10.17487/RFC6702, August 2012.

9.2. Informative References

[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996.
[RFC3716] IAB Advisory Committee, "The IETF in the Large: Administration and Execution", RFC 3716, DOI 10.17487/RFC3716, March 2004.
[RFC3929] Hardie, T., "Alternative Decision Making Processes for Consensus-Blocked Decisions in the IETF", RFC 3929, DOI 10.17487/RFC3929, October 2004.
[RFC3979] Bradner, S., "Intellectual Property Rights in IETF Technology", RFC 3979, DOI 10.17487/RFC3979, March 2005.
[RFC4633] Hartman, S., "Experiment in Long-Term Suspensions From Internet Engineering Task Force (IETF) Mailing Lists", RFC 4633, DOI 10.17487/RFC4633, August 2006.
[RFC4879] Narten, T., "Clarification of the Third Party Disclosure Procedure in RFC 3979", RFC 4879, DOI 10.17487/RFC4879, April 2007.
[RFC8179] Bradner, S. and J. Contreras, "Intellectual Property Rights in IETF Technology", BCP 79, RFC 8179, DOI 10.17487/RFC8179, May 2017.

Appendix A. Change Log

RFC Editor: Please remove this appendix before publication.

A.1. Changes from version -00 (2018-11-15) to -01

A.2. Changes from version -01 (dated 2018-12-06 but posted 2012-12-07) to -02

I accidentally omitted RFC 4844 from the document header "updates" list in Version 01 and noticed that in response to an unrelated question almost immediately after posting. The correction seemed important enough to justify almost immediate re-posting. Changes are only that header, the document file name, and the date. --JcK

A.3. Changes from version -02 (2018-12-07) to -03

A.4. Changes from version -03 (2018-12-12) to -04

A.5. Changes from version -04 (2019-01-17) to -05

A.6. Changes from version -05 (2019-01-31) to -06

A.7. Changes from version -06 (2019-03-06) to -07

Author's Address

John C Klensin (editor) 1770 Massachusetts Ave, Ste 322 Cambridge, MA 02140 USA Phone: +1 617 245 1457 EMail: john-ietf@jck.com