draft-ietf-iasa2-consolidated-upd-02.txt   draft-ietf-iasa2-consolidated-upd-03.txt 
IASA2 J. Klensin, Ed. IASA2 J. Klensin, Ed.
Internet-Draft December 7, 2018 Internet-Draft December 12, 2018
Obsoletes: 3716, 3929, 4633 (if Obsoletes: 3716, 3929, 4633 (if
approved) approved)
Updates: 2028, 2418, 3005, 3710, 4844, Updates: 2028, 2418, 3005, 3710, 4844,
5377, 6702, 7500 (if approved) 5377, 6702 (if approved)
Intended status: Best Current Practice Intended status: Best Current Practice
Expires: June 10, 2019 Expires: June 15, 2019
Consolidated IASA2-Related Document Updates Consolidated IASA2-Related Document Updates
draft-ietf-iasa2-consolidated-upd-02 draft-ietf-iasa2-consolidated-upd-03
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 (IASA) structure and updated its IETF Administrative Support Activity (IASA)
to a new "IASA 2.0" structure. In addition to more substantive to a new "IASA 2.0" structure. In addition to more substantive
changes that are described in other documents, the transition to the changes that are described in other documents, the transition to the
2018 IETF Administrative Support structure changes several position 2018 IETF Administrative Support structure changes several position
titles and organizational relationships that are referenced titles and organizational relationships that are referenced
elsewhere. Rather than reissue those referencing documents elsewhere. Rather than reissue those referencing documents
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 June 10, 2019. This Internet-Draft will expire on June 15, 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 23 skipping to change at page 2, line 23
described in the Simplified BSD License. described in the Simplified BSD License.
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 . . . . . . . 4
6. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 6 6. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
10. Security Considerations . . . . . . . . . . . . . . . . . . . 7 10. Security Considerations . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
11.1. Normative References . . . . . . . . . . . . . . . . . . 7 11.1. Normative References . . . . . . . . . . . . . . . . . . 6
11.2. Informative References . . . . . . . . . . . . . . . . . 8 11.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 9 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8
A.1. Changes from version -00 (2018-11-15) to -01 . . . . . . 9 A.1. Changes from version -00 (2018-11-15) to -01 . . . . . . 8
A.2. Changes from version -01 (dated 2018-12-06 but A.2. Changes from version -01 (dated 2018-12-06 but
posted 2012-12-07) to -02 . . . . . . . . . . . . . . . . 10 posted 2012-12-07) to -02 . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 A.3. Changes from version -02 (2018-12-07) to -03 . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
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"
or just "the LLC" in places in this document and elsewhere) and or just "the LLC" in places in this document and elsewhere) and
adjustments to the procedures for nominations and selections for adjustments to the procedures for nominations and selections for
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, and 6702
7500 (citations in context below) to make those terminology and (citations in context below) to make those terminology and related
related changes. For clarity, it also obsoletes RFCs 3716 and 3929 changes. For clarity, it also obsoletes RFCs 3716 and 3929 which
which were Experimental or Informational documents that are no longer were Experimental or Informational documents that are no longer
relevant (see Section 6). The sections that follow identify the relevant (see Section 6). The sections that follow identify the
details of the relevant documents and the required changes. details of the relevant documents and the 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
skipping to change at page 4, line 5 skipping to change at page 4, line 5
that are not removed by the prior section, shall be updated and that are not removed by the prior section, shall be updated and
replaced by the IETF Administration LLC (IETF-LLC). This is replaced by the IETF Administration LLC (IETF-LLC). This is
necessary because the IAOC is phased out under the IASA 2.0 necessary because the IAOC is phased out under the IASA 2.0
structure. structure.
This document applies that change to the following: This document applies that change to the following:
o RFC 4844 [RFC4844], the RFC Series and RFC Editor Sections 3.3, o RFC 4844 [RFC4844], the RFC Series and RFC Editor Sections 3.3,
3.4, and 4. 3.4, and 4.
o RFC 7500 [RFC7500] Principles for Operation of Internet Assigned
Numbers Authority (IANA) Registries, Section 3.4. This means that
the IETF LLC, the body responsible for IETF administrative and
financial matters, maintains an SLA with the current registry
operator, the Internet Corporation for Assigned Names and Numbers
(ICANN). It also means that both the Internet Architecture Board
(IAB) and the IETF LLC are accountable to the larger Internet
community for the IANA registries.
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 position with the Managing Director, IETF Secretariat
Under the IASA 2.0 structure, most of the responsibilities of the Under the IASA 2.0 structure, most of the responsibilities of the
former position of IETF Executive Director been assigned to a new former position of IETF Executive Director been assigned to a new
position (or at least title) of Managing Director of the IETF position (or at least title) of Managing Director of the IETF
Secretariat. An "Executive Director" title is now associated with Secretariat. An "Executive Director" title is now associated with
different, and largely new, responsibilities as an Officer of the different, and largely new, responsibilities as an Officer of the
IETF Administration LLC. These changes are described in the IETF Administration LLC. These changes are described in the
description of the new structural arrangements [RFC-Struct]. description of the new structural arrangements [RFC-Struct].
[[CREF3: Editorial comment/rant (JcK 20181114): Or at least they had
better be clearly described there because, if they are not, this
document is the wrong place to try to fix it. I've done the best I
could to combine my view of what this should say (which does not
necessarily align with WG discussions) and Jason's (which presumably
does, but had another issue or two). Basically, from the standpoint
of a clear understanding of the new roles and titles, taking the old
roles of "IETF Executive Director" and "IETF Administrative Director"
and renaming the Secretariat management part of the former role to
"Managing Director, IETF Secretariat" would have been a little
confusing because the old "IETF Executive Director" position had
functions that were not inherently limited to the Secretariat
function as the IETF has understood it. But then taking some of the
IAD functions and calling them "Executive Director" (without "IETF",
but the term with "IETF" is still present in older documents that the
WG has concluded it doesn't need to update and in some more recent
sloppy usage) while distributing other IAD functions to the
Secretariat is a recipe for complete confusion... and I've seen
messages in which several people who have been active in the WG
appear to be confused. I accept Alissa's judgment that it is too
late to change this, or at least the association of the "Executive
Director" title with that LLC function, but suggest we need to be
_very_ careful -- much more careful than we have apparently been so
far -- about good-quality explanations and absolute consistency about
terminology. ]]
This document applies that change to the following: This document applies that change to the following:
o RFC 2028, The Organizations Involved in the IETF Standards Process o RFC 2028, The Organizations Involved in the IETF Standards Process
[RFC2028], Section 3.3. [RFC2028], Section 3.3.
[[CREF4: Editorial note (JcK 20181115) Jason suggested somewhat
different text, specifically "This means that the administrative
functions necessary to support the activities of the IETF are
performed by a Secretariat, led by the Managing Director, IETF
Secretariat, and consisting of his or her staff in the IETF
Secretariat." I don't think "This" (the change) means any such
thing because 2028 fairly clearly establishes the administrative
function role of the Secretariat and its staff. All this change
does is what is described in the first paragraph of this section,
i.e., switch titles, so the additional attempted explanation is
unnecessary and likely to be confusing. A similar change was
proposed for the description of the RFC 2418 change below. The WG
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 Note that the current description of the Internet Standards Process
[RFC2026] does not require an update by this document for this [RFC2026] does not require an update by this document for this
purpose because the reference to the IETF Executive Director in RFC purpose because the reference to the IETF Executive Director in RFC
2026 was replaced by a document that precedes the current effort 2026 was replaced by a document that precedes the current effort
[RFC3979] and that was, in turn, obsoleted by RFC 8179 [RFC8179]. [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 [[CREF3: 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
to remove the IETF Executive Director from the list of people with to remove the IETF Executive Director from the list of people with
skipping to change at page 6, line 16 skipping to change at page 5, line 16
6. Deprecated Documents 6. Deprecated Documents
The IASA2 Working Group has also identified several RFCs that no The IASA2 Working Group has also identified several RFCs that no
longer apply as a result of the change to the new IASA 2.0 structure. longer apply as a result of the change to the new IASA 2.0 structure.
The result is that several informational, experimental, or other RFCs The result is that several informational, experimental, or other RFCs
can be deprecated. can be deprecated.
This document deprecates the following: This document deprecates the following:
o RFC 3716 [RFC3716], which describes the general administrative
model of the IETF.
o RFC 3929 [RFC3929], which touches on aspects of the administration o RFC 3929 [RFC3929], which touches on aspects of the administration
of the IETF, such as mentioning the IETF Executive Director. It of the IETF, such as mentioning the IETF Executive Director. It
dates to 2004 and is experimental. dates to 2004 and is experimental.
o RFC 3979 [RFC3979], that is updated by [RFC8179], which corrects o RFC 3979 [RFC3979], 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.
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.
skipping to change at page 6, line 47 skipping to change at page 6, line 7
draft in its current form. 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.]] [[CREF4: RFC Editor: Please remove this section before publication.]]
This memo includes no requests to or actions for IANA. This memo includes no requests to or actions for IANA.
10. Security Considerations 10. Security Considerations
The changes specified in this document are matters of terminology and The changes specified in this document are matters of terminology and
organizational structure derived from documents it references. It organizational structure derived from documents it references. It
should have no effect on Internet security. should have no effect on Internet security.
11. References 11. References
skipping to change at page 8, line 31 skipping to change at page 7, line 36
[RFC5377] Halpern, J., Ed., "Advice to the Trustees of the IETF [RFC5377] Halpern, J., Ed., "Advice to the Trustees of the IETF
Trust on Rights to Be Granted in IETF Documents", Trust on Rights to Be Granted in IETF Documents",
RFC 5377, DOI 10.17487/RFC5377, November 2008, RFC 5377, DOI 10.17487/RFC5377, November 2008,
<https://www.rfc-editor.org/info/rfc5377>. <https://www.rfc-editor.org/info/rfc5377>.
[RFC6702] Polk, T. and P. Saint-Andre, "Promoting Compliance with [RFC6702] Polk, T. and P. Saint-Andre, "Promoting Compliance with
Intellectual Property Rights (IPR) Disclosure Rules", Intellectual Property Rights (IPR) Disclosure Rules",
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
Operation of Internet Assigned Numbers Authority (IANA)
Registries", RFC 7500, DOI 10.17487/RFC7500, April 2015,
<https://www.rfc-editor.org/info/rfc7500>.
11.2. Informative References 11.2. Informative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
<https://www.rfc-editor.org/info/rfc2026>. <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>.
skipping to change at page 9, line 34 skipping to change at page 8, line 34
RFC Editor: Please remove this appendix before publication. RFC Editor: Please remove this appendix before publication.
A.1. Changes from version -00 (2018-11-15) to -01 A.1. Changes from version -00 (2018-11-15) to -01
o Removed RFCs 3979 and 4879 from the "obsoletes" list because they o Removed RFCs 3979 and 4879 from the "obsoletes" list because they
had already been obsoleted (by 8179). It also removes RFC 8179 had already been obsoleted (by 8179). It also removes RFC 8179
from the "updates" list because 8179 uses "IETF Secretariat" from the "updates" list because 8179 uses "IETF Secretariat"
terminology rather than "IETF Executive Director". terminology rather than "IETF Executive Director".
[[CREF7: Note in Draft: That suggests an idea which might [[CREF5: Note in Draft: That suggests an idea which might
considerably mitigate the name confusion issue: Instead of considerably mitigate the name confusion issue: Instead of
singling out the Managing Director of the Secretariat as a named singling out the Managing Director of the Secretariat as a named
individual, perhaps we should be referring to the Secretariat individual, perhaps we should be referring to the Secretariat
itself, leaving the contact point or address up to them as an itself, leaving the contact point or address up to them as an
internal administrative matter. Just a thought. --JcK]] internal administrative matter. Just a thought. --JcK]]
o Added text to explain why RFC 2026 is not on the hit list. 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 o Added an acknowledgment to Brian Carpenter. If he catches another
batch of errors and supplies text, he gets promoted to batch of errors and supplies text, he gets promoted to
skipping to change at page 10, line 14 skipping to change at page 9, line 14
A.2. Changes from version -01 (dated 2018-12-06 but posted 2012-12-07) A.2. Changes from version -01 (dated 2018-12-06 but posted 2012-12-07)
to -02 to -02
I accidentally omitted RFC 4844 from the document header "updates" I accidentally omitted RFC 4844 from the document header "updates"
list in Version 01 and noticed that in response to an unrelated list in Version 01 and noticed that in response to an unrelated
question almost immediately after posting. The correction seemed question almost immediately after posting. The correction seemed
important enough to justify almost immediate re-posting. Changes are important enough to justify almost immediate re-posting. Changes are
only that header, the document file name, and the date. --JcK only that header, the document file name, and the date. --JcK
A.3. Changes from version -02 (2018-12-07) to -03
o Removed discussion and pointers to RFC 7500 - IAB will publish
separately.
o Added text to describe (very superficially) RFC 3716. That
document was obsoleted in the previous version but not described.
o Removed rant about titles and responsibilities from Section 4 and
a subsequent editorial note I hope it is no longer needed --JcK.
In additional, several blocks of text that were commented out in
earlier versions of the XML have been removed entirely.
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. 18 change blocks. 
77 lines changed or deleted 41 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/