draft-ietf-iasa2-consolidated-upd-03.txt   draft-ietf-iasa2-consolidated-upd-04.txt 
IASA2 J. Klensin, Ed. IASA2 J. Klensin, Ed.
Internet-Draft December 12, 2018 Internet-Draft January 17, 2019
Obsoletes: 3716, 3929, 4633 (if Obsoletes: 3716, 3929, 4633 (if
approved) approved)
Updates: 2028, 2418, 3005, 3710, 4844, Updates: 2028, 2418, 3005, 3710, 6702
5377, 6702 (if approved) (if approved)
Intended status: Best Current Practice Intended status: Best Current Practice
Expires: June 15, 2019 Expires: July 21, 2019
Consolidated IASA2-Related Document Updates Consolidated IASA2-Related Document Updates
draft-ietf-iasa2-consolidated-upd-03 draft-ietf-iasa2-consolidated-upd-04
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 15, 2019. This Internet-Draft will expire on July 21, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
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. Where Appropriate, Replacement of the IETF Executive Director
Trust . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 position with the Managing Director, IETF Secretariat . . . . 3
3. Replacement of IAOC with IETF Administration LLC . . . . . . 3 3. Remove the IETF Executive Director as an Option . . . . . . . 4
4. Where Appropriate, Replacement of the IETF Executive Director 4. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 4
position with the Managing Director, IETF Secretariat . . . . 4 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
5. Remove the IETF Executive Director as an Option . . . . . . . 4 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 9.1. Normative References . . . . . . . . . . . . . . . . . . 5
10. Security Considerations . . . . . . . . . . . . . . . . . . . 6 9.2. Informative References . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 7
11.1. Normative References . . . . . . . . . . . . . . . . . . 6 A.1. Changes from version -00 (2018-11-15) to -01 . . . . . . 7
11.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . 9 posted 2012-12-07) to -02 . . . . . . . . . . . . . . . . 8
A.3. Changes from version -02 (2018-12-07) to -03 . . . . . . 9 A.3. Changes from version -02 (2018-12-07) to -03 . . . . . . 8
A.4. Changes from version -03 (2018-12-12) to -04 . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 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
skipping to change at page 3, line 11 skipping to change at page 3, line 7
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, and 6702 This document updates RFCs 2028, 2418, 3005, 3710, and 6702
(citations in context below) to make those terminology and related (citations in context below) to make those terminology and related
changes. For clarity, it also obsoletes RFCs 3716 and 3929 which changes. For clarity, it also obsoletes RFCs 3716 and 3929 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 4). 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. Where Appropriate, Replacement of the IETF Executive Director
Some documents that discuss the IETF Trust or its relationship to the
community describe it, or the Trustees, in relation to the IAOC.
That connection must be eliminated to reflect the new IASA 2.0
structure.
This document applies that change to the following:
o RFC 5377 [RFC5377], Advice to the Trustees of the IETF Trust on
Rights to Be Granted in IETF Documents. These changes require
dropping "made up of the members of the IAOC [RFC4371]" after
"board of trustees" in the first paragraph of Section 1 and "which
is made up of the members of the IAOC, as described in [RFC4071]
and [RFC4371]" in the first paragraph of Section 3.
[[CREF2: RFC Editor please note that the bracketed strings above
are quoted text, not references. ]]
3. Replacement of IAOC with IETF Administration LLC
All mentions of the IETF Administrative Oversight Committee (IAOC)
that are not removed by the prior section, shall be updated and
replaced by the IETF Administration LLC (IETF-LLC). This is
necessary because the IAOC is phased out under the IASA 2.0
structure.
This document applies that change to the following:
o RFC 4844 [RFC4844], the RFC Series and RFC Editor Sections 3.3,
3.4, and 4.
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].
skipping to change at page 4, line 34 skipping to change at page 4, line 5
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].
[[CREF3: Note in Draft: Bob Hinden's note of November 10, 2018 11:37 3. Remove the IETF Executive Director as an Option
+0900 indicates that RFC4844 should continue to reference the IETF
Executive Director.]]
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
specific responsibilities or authority. Those documents will not be specific responsibilities or authority. Those documents will not be
updated to use "Managing Director, IETF Secretariat" but, instead, updated to use "Managing Director, IETF Secretariat" but, instead,
the mention of the position will simply be dropped. the mention of the position will simply be dropped.
This document applies that change to the following: This document applies that change to the following:
o RFC 3005, IETF Discussion List Charter [RFC3005], section titled o RFC 3005, IETF Discussion List Charter [RFC3005], section titled
"Charter for the IETF Discussion List". This document is modified "Charter for the IETF Discussion List". This document is modified
to remove the authorization for the IETF Executive Director to to remove the authorization for the IETF Executive Director to
restrict people from posting, etc. restrict people from posting, etc.
6. Deprecated Documents 4. 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 o RFC 3716 [RFC3716], which describes the general administrative
model of the IETF. model of the IETF.
skipping to change at page 5, line 36 skipping to change at page 5, line 5
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. Acknowledgments 5. Acknowledgments
Brian Carpenter's careful checking and identification of documents Brian Carpenter's careful checking and identification of documents
that did, and did not, require consideration was essential to the that did, and did not, require consideration was essential to the
draft in its current form. draft in its current form.
8. Contributors 6. 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 7. IANA Considerations
[[CREF4: RFC Editor: Please remove this section before publication.]] [[CREF2: 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 8. 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 9. References
11.1. Normative References 9.1. Normative References
[LLC-Agreement] [LLC-Agreement]
IETF Administration LLC, "Limited Liability Company IETF Administration LLC, "Limited Liability Company
Agreement of IETF Administration LLC", August 2018, Agreement of IETF Administration LLC", August 2018,
<https://www.ietf.org/documents/180/ <https://www.ietf.org/documents/180/
IETF-LLC-Agreement.pdf>. IETF-LLC-Agreement.pdf>.
[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
skipping to change at page 7, line 22 skipping to change at page 6, line 34
September 1998, <https://www.rfc-editor.org/info/rfc2418>. September 1998, <https://www.rfc-editor.org/info/rfc2418>.
[RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, [RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45,
RFC 3005, DOI 10.17487/RFC3005, November 2000, RFC 3005, DOI 10.17487/RFC3005, November 2000,
<https://www.rfc-editor.org/info/rfc3005>. <https://www.rfc-editor.org/info/rfc3005>.
[RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710,
DOI 10.17487/RFC3710, February 2004, DOI 10.17487/RFC3710, February 2004,
<https://www.rfc-editor.org/info/rfc3710>. <https://www.rfc-editor.org/info/rfc3710>.
[RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC
Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844,
July 2007, <https://www.rfc-editor.org/info/rfc4844>.
[RFC5377] Halpern, J., Ed., "Advice to the Trustees of the IETF
Trust on Rights to Be Granted in IETF Documents",
RFC 5377, DOI 10.17487/RFC5377, November 2008,
<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>.
11.2. Informative References 9.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 8, line 34 skipping to change at page 7, line 39
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".
[[CREF5: Note in Draft: That suggests an idea which might [[CREF3: 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 9, line 22 skipping to change at page 8, line 24
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 A.3. Changes from version -02 (2018-12-07) to -03
o Removed discussion and pointers to RFC 7500 - IAB will publish o Removed discussion and pointers to RFC 7500 - IAB will publish
separately. separately.
o Added text to describe (very superficially) RFC 3716. That o Added text to describe (very superficially) RFC 3716. That
document was obsoleted in the previous version but not described. document was obsoleted in the previous version but not described.
o Removed rant about titles and responsibilities from Section 4 and o Removed rant about titles and responsibilities from Section 2 and
a subsequent editorial note I hope it is no longer needed --JcK. a subsequent editorial note I hope it is no longer needed --JcK.
In additional, several blocks of text that were commented out in In additional, several blocks of text that were commented out in
earlier versions of the XML have been removed entirely. earlier versions of the XML have been removed entirely.
A.4. Changes from version -03 (2018-12-12) to -04
o Removed RFC 4844 from the update list and discussion because the
consensus in the WG seemed to be that it (and the RFC Editor)
should be handled separately.
o Removed RFC 5377 from the update list and discussion because it
involves the Trust.
o Editor's note in draft:
The above changes and the earlier removal of RFC 7500 so the
IAB could publish it own document completely eliminate the
earlier Sections 2 and 3. That may call for a revision of the
Introduction and/or Abstract, but I have not done a review for
this iteration of whether such changes are needed.
As documents and references are shuffled in and out of this
one, it occurred to me that having a non-normative appendix
somewhere that would identify all of the documents containing
changes to reflect the IASA 1.x to 2.0 transition would be of
great help to any future historian trying to understand what we
did and probably helpful to the IETF if some of these changes
don't work out and/or require further tuning. After a brief
discussion, Jason and I concluded that appendix did not belong
in this iteration of this document.
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. 25 change blocks. 
84 lines changed or deleted 65 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/