draft-ietf-iasa2-consolidated-upd-00.txt   draft-ietf-iasa2-consolidated-upd-01.txt 
IASA2 J. Klensin, Ed. IASA2 J. Klensin, Ed.
Internet-Draft November 15, 2018 Internet-Draft December 6, 2018
Obsoletes: 3716, 3929, 3979, 4633, 4879, Obsoletes: 3716, 3929, 4633 (if
8179 (if approved) approved)
Updates: 2028, 2418, 3005, 3710, 5377, Updates: 2028, 2418, 3005, 3710, 5377,
6702, 7500 (if approved) 6702, 7500 (if approved)
Intended status: Best Current Practice Intended status: Best Current Practice
Expires: May 19, 2019 Expires: June 9, 2019
Consolidated IASA2-Related Document Updates Consolidated IASA2-Related Document Updates
draft-ietf-iasa2-consolidated-upd-00 draft-ietf-iasa2-consolidated-upd-01
Abstract Abstract
In 2018, the IETF began the transition to a new administrative In 2018, the IETF began the transition to a new administrative
structure, and updated its IETF Administrative Support Activity structure and updated its IETF Administrative Support Activity (IASA)
(IASA) to a new "IASA 2.0" structure. In addition to more to a new "IASA 2.0" structure. In addition to more substantive
substantive changes that are described in other documents, the changes that are described in other documents, the transition to the
transition to the 2018 IETF Administrative Support structure changes 2018 IETF Administrative Support structure changes several position
several position titles and organizational relationships that are titles and organizational relationships that are referenced
referenced in other documents. Rather than reissue those documents elsewhere. Rather than reissue those referencing documents
individually, this specification provides updates to them and individually, this specification provides updates to them and
deprecates some now-obsolete documents to ensure that there is no deprecates some now-obsolete documents to ensure that there is no
confusion due to these changes. confusion due to these changes.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 19, 2019. This Internet-Draft will expire on June 9, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 24 skipping to change at page 2, line 24
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Remove Text About the Connection Between the IAOC and IETF 2. Remove Text About the Connection Between the IAOC and IETF
Trust . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Trust . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Replacement of IAOC with IETF Administration LLC . . . . . . 3 3. Replacement of IAOC with IETF Administration LLC . . . . . . 3
4. Where Appropriate, Replacement of the IETF Executive Director 4. Where Appropriate, Replacement of the IETF Executive Director
position with the Managing Director, IETF Secretariat . . . . 4 position with the Managing Director, IETF Secretariat . . . . 4
5. Remove the IETF Executive Director as an Option . . . . . . . 5 5. Remove the IETF Executive Director as an Option . . . . . . . 5
6. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 5 6. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
10. Security Considerations . . . . . . . . . . . . . . . . . . . 6 10. Security Considerations . . . . . . . . . . . . . . . . . . . 7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
11.1. Normative References . . . . . . . . . . . . . . . . . . 6 11.1. Normative References . . . . . . . . . . . . . . . . . . 7
11.2. Informative References . . . . . . . . . . . . . . . . . 8 11.2. Informative References . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 9
A.1. Changes from version -00 (2018-11-15) to -01 . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
In 2018, the IETF began the transition to a new administrative In 2018, the IETF began the transition to a new administrative
structure, and updated its IETF Administrative Support Activity structure, and updated its IETF Administrative Support Activity
(IASA) to a new "IASA 2.0" structure [RFC-Struct]. Key IASA 2.0 (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 have been specified in a series of documents, including
changes to the IETF Trust [RFC-trust-update], the rationale for it changes to the IETF Trust [RFC-trust-update], the rationale for it
[RFC-trust-rationale], a new defining document for the IETF [RFC-trust-rationale], a new defining document for the IETF
Administration LLC [LLC-Agreement] (informally called the "IETF LLC" Administration LLC [LLC-Agreement] (informally called the "IETF LLC"
skipping to change at page 3, line 7 skipping to change at page 3, line 9
relevant positions [RFC-7437bis]. relevant positions [RFC-7437bis].
In addition to more substantive changes that are described in those In addition to more substantive changes that are described in those
and other documents, the IASA 2.0 structure changes several position and other documents, the IASA 2.0 structure changes several position
titles and organizational relationships that are referenced in other titles and organizational relationships that are referenced in other
documents. Rather than reissue those documents individually, this documents. Rather than reissue those documents individually, this
document provides a unified update to them. document provides a unified update to them.
This document updates RFCs 2028, 2418, 3005, 3710, 5377, 6702, and This document updates RFCs 2028, 2418, 3005, 3710, 5377, 6702, and
7500 (citations in context below) to make those terminology and 7500 (citations in context below) to make those terminology and
related changes. For clarity, it also obsoletes RFCs 3716, 3929, related changes. For clarity, it also obsoletes RFCs 3716 and 3929
3979, 4633, 4879, and 8179 which were Experimental or Informational which were Experimental or Informational documents that are no longer
documents that are no longer relevant (see Section 6). The sections relevant (see Section 6). The sections that follow identify the
that follow identify the details of the relevant documents and the details of the relevant documents and the required changes.
required changes.
[[CREF1: Note in Draft: This document lists changes that the WG may [[CREF1: Note in Draft: This document lists changes that the WG may
choose to process as standalone replacement documents instead. The choose to process as standalone replacement documents instead. The
relevant sections are provided to speed things along should it decide relevant sections are provided to speed things along should it decide
to not do that.]] to not do that.]]
2. Remove Text About the Connection Between the IAOC and IETF Trust 2. Remove Text About the Connection Between the IAOC and IETF Trust
Some documents that discuss the IETF Trust or its relationship to the Some documents that discuss the IETF Trust or its relationship to the
community describe it, or the Trustees, in relation to the IAOC. community describe it, or the Trustees, in relation to the IAOC.
skipping to change at page 5, line 23 skipping to change at page 5, line 26
proposed for the description of the RFC 2418 change below. The WG proposed for the description of the RFC 2418 change below. The WG
should decide what it wants.]] should decide what it wants.]]
o RFC 2418, IETF Working Group Guidelines and Procedures [RFC2418] o RFC 2418, IETF Working Group Guidelines and Procedures [RFC2418]
o RFC 3710, An IESG Charter, Section 2[RFC3710]. o RFC 3710, An IESG Charter, Section 2[RFC3710].
o RFC 6702, Promoting Compliance with Intellectual Property Rights o RFC 6702, Promoting Compliance with Intellectual Property Rights
(IPR) Disclosure Rules, Section 5 [RFC6702]. (IPR) Disclosure Rules, Section 5 [RFC6702].
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 [RFC8179].
[[CREF5: Note in Draft: Bob Hinden's note of November 10, 2018 11:37 [[CREF5: Note in Draft: Bob Hinden's note of November 10, 2018 11:37
+0900 indicates that RFC4844 should continue to reference the IETF +0900 indicates that RFC4844 should continue to reference the IETF
Executive Director.]] Executive Director.]]
5. Remove the IETF Executive Director as an Option 5. Remove the IETF Executive Director as an Option
In a few cases, it is no longer appropriate for either the Managing In a few cases, it is no longer appropriate for either the Managing
Director, IETF Secretariat (former IETF Executive Director position) Director, IETF Secretariat (former IETF Executive Director position)
or the new IETF Executive Director (for the LLC) to perform a or the new IETF Executive Director (for the LLC) to perform a
particular historical function. The relevant documents are updated particular historical function. The relevant documents are updated
skipping to change at page 6, line 24 skipping to change at page 6, line 31
o RFC 4633 [RFC4633], which is an experimental document that refers o RFC 4633 [RFC4633], which is an experimental document that refers
to IETF Executive Director. It describes a 2006 experiment that to IETF Executive Director. It describes a 2006 experiment that
ran for 18 months. ran for 18 months.
o RFC 4879 [RFC4879], that is updated by [RFC8179], which corrects o RFC 4879 [RFC4879], that is updated by [RFC8179], which corrects
mentions of the IETF Executive Director to the IETF Secretariat. mentions of the IETF Executive Director to the IETF Secretariat.
It is also recommended that the above documents be reclassified to It is also recommended that the above documents be reclassified to
Historic to further reduce the risk of any confusion. Historic to further reduce the risk of any confusion.
7. Acknowledgements 7. Acknowledgments
..to be supplied after version 00 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.
8. Contributors 8. Contributors
Jason Livingood did the hard work of identifying the documents that Jason Livingood did the hard work of identifying the documents that
required updating and supplied considerable text used in this required updating and supplied considerable text used in this
document. document.
9. IANA Considerations 9. IANA Considerations
[[CREF6: RFC Editor: Please remove this section before publication.]] [[CREF6: RFC Editor: Please remove this section before publication.]]
skipping to change at page 7, line 20 skipping to change at page 7, line 30
[RFC-7437bis] [RFC-7437bis]
Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood, Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood,
Ed., "IAB, IESG, and IETF LLC Selection, Confirmation, and Ed., "IAB, IESG, and IETF LLC Selection, Confirmation, and
Recall Process: Operation of the IETF Nominating and Recall Process: Operation of the IETF Nominating and
Recall Committees", 2018, Recall Committees", 2018,
<https://datatracker.ietf.org/doc/ <https://datatracker.ietf.org/doc/
draft-ietf-iasa2-rfc7437bis/>. draft-ietf-iasa2-rfc7437bis/>.
[RFC-Struct] [RFC-Struct]
Haberman, B., Hall, J., and J. Livingood, Ed., "Record of Haberman, B., Hall, J., and J. Livingood, "Structure of
Proposed Structure of the IETF Administrative Support the IETF Administrative Support Activity, Version 2.0",
Activity (IASA), Version 2.0", 2018, December 2018, <https://datatracker.ietf.org/doc/
<https://datatracker.ietf.org/doc/ draft-ietf-iasa2-rfc4071bis/>.
draft-ietf-iasa2-struct/>.
[RFC-StructS3]
Haberman, B., Hall, J., and J. Livingood, Ed., "Record of
Proposed Structure of the IETF Administrative Support
Activity (IASA), Version 2.0, Sectiion 3", 2018,
<https://tools.ietf.org/html/
draft-ietf-iasa2-struct-06#section-3>.
[RFC-trust-rationale] [RFC-trust-rationale]
Arkko, J., "Discussion of the IASA 2.0 Changes as They Arkko, J., "Discussion of the IASA 2.0 Changes as They
Relate to the IETF Trust", 2018, Relate to the IETF Trust", 2018,
<https://datatracker.ietf.org/doc/ <https://datatracker.ietf.org/doc/
draft-ietf-iasa2-trust-rationale/>. draft-ietf-iasa2-trust-rationale/>.
[RFC-trust-update] [RFC-trust-update]
Arkko, J. and T. Hardie, "Update to the Process for Arkko, J. and T. Hardie, "Update to the Process for
Selection of Trustees for the IETF Trust", 2018, Selection of Trustees for the IETF Trust", 2018,
skipping to change at page 8, line 34 skipping to change at page 8, line 38
RFC 6702, DOI 10.17487/RFC6702, August 2012, RFC 6702, DOI 10.17487/RFC6702, August 2012,
<https://www.rfc-editor.org/info/rfc6702>. <https://www.rfc-editor.org/info/rfc6702>.
[RFC7500] Housley, R., Ed. and O. Kolkman, Ed., "Principles for [RFC7500] Housley, R., Ed. and O. Kolkman, Ed., "Principles for
Operation of Internet Assigned Numbers Authority (IANA) Operation of Internet Assigned Numbers Authority (IANA)
Registries", RFC 7500, DOI 10.17487/RFC7500, April 2015, Registries", RFC 7500, DOI 10.17487/RFC7500, April 2015,
<https://www.rfc-editor.org/info/rfc7500>. <https://www.rfc-editor.org/info/rfc7500>.
11.2. Informative References 11.2. Informative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
<https://www.rfc-editor.org/info/rfc2026>.
[RFC3716] IAB Advisory Committee, "The IETF in the Large: [RFC3716] IAB Advisory Committee, "The IETF in the Large:
Administration and Execution", RFC 3716, Administration and Execution", RFC 3716,
DOI 10.17487/RFC3716, March 2004, DOI 10.17487/RFC3716, March 2004,
<https://www.rfc-editor.org/info/rfc3716>. <https://www.rfc-editor.org/info/rfc3716>.
[RFC3929] Hardie, T., "Alternative Decision Making Processes for [RFC3929] Hardie, T., "Alternative Decision Making Processes for
Consensus-Blocked Decisions in the IETF", RFC 3929, Consensus-Blocked Decisions in the IETF", RFC 3929,
DOI 10.17487/RFC3929, October 2004, DOI 10.17487/RFC3929, October 2004,
<https://www.rfc-editor.org/info/rfc3929>. <https://www.rfc-editor.org/info/rfc3929>.
skipping to change at page 9, line 14 skipping to change at page 9, line 23
[RFC4879] Narten, T., "Clarification of the Third Party Disclosure [RFC4879] Narten, T., "Clarification of the Third Party Disclosure
Procedure in RFC 3979", RFC 4879, DOI 10.17487/RFC4879, Procedure in RFC 3979", RFC 4879, DOI 10.17487/RFC4879,
April 2007, <https://www.rfc-editor.org/info/rfc4879>. April 2007, <https://www.rfc-editor.org/info/rfc4879>.
[RFC8179] Bradner, S. and J. Contreras, "Intellectual Property [RFC8179] Bradner, S. and J. Contreras, "Intellectual Property
Rights in IETF Technology", BCP 79, RFC 8179, Rights in IETF Technology", BCP 79, RFC 8179,
DOI 10.17487/RFC8179, May 2017, DOI 10.17487/RFC8179, May 2017,
<https://www.rfc-editor.org/info/rfc8179>. <https://www.rfc-editor.org/info/rfc8179>.
Appendix A. Change Log
RFC Editor: Please remove this appendix before publication.
A.1. Changes from version -00 (2018-11-15) to -01
o Removed RFCs 3979 and 4879 from the "obsoletes" list because they
had already been obsoleted (by 8179). It also removes RFC 8179
from the "updates" list because 8179 uses "IETF Secretariat"
terminology rather than "IETF Executive Director".
[[CREF7: Note in Draft: That suggests an idea which might
considerably mitigate the name confusion issue: Instead of
singling out the Managing Director of the Secretariat as a named
individual, perhaps we should be referring to the Secretariat
itself, leaving the contact point or address up to them as an
internal administrative matter. Just a thought. --JcK]]
o Added text to explain why RFC 2026 is not on the hit list.
o Added an acknowledgment to Brian Carpenter. If he catches another
batch of errors and supplies text, he gets promoted to
Contributor.
o Adjusted reference [RFC-Struct] to point to 4071bis.
o Minor editorial corrections and changes.
Author's Address Author's Address
John C Klensin (editor) John C Klensin (editor)
1770 Massachusetts Ave, Ste 322 1770 Massachusetts Ave, Ste 322
Cambridge, MA 02140 Cambridge, MA 02140
USA USA
Phone: +1 617 245 1457 Phone: +1 617 245 1457
Email: john-ietf@jck.com Email: john-ietf@jck.com
 End of changes. 15 change blocks. 
37 lines changed or deleted 70 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/