draft-ietf-iasa2-consolidated-upd-05.txt   draft-ietf-iasa2-consolidated-upd-06.txt 
IASA2 J. Klensin, Ed. IASA2 J. Klensin, Ed.
Internet-Draft January 31, 2019 Internet-Draft March 7, 2019
Obsoletes: 3716, 3929, 4633 (if Obsoletes: 3929, 4633 (if approved)
approved)
Updates: 2028, 2418, 3005, 3710, 6702 Updates: 2028, 2418, 3005, 3710, 6702
(if approved) (if approved)
Intended status: Best Current Practice Intended status: Best Current Practice
Expires: August 4, 2019 Expires: September 8, 2019
Consolidated IASA 2.0 Updates of IETF Administrative Terminology Consolidated IASA 2.0 Updates of IETF Administrative Terminology
draft-ietf-iasa2-consolidated-upd-05 draft-ietf-iasa2-consolidated-upd-06
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 42
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 August 4, 2019. This Internet-Draft will expire on September 8, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 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
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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. Where Appropriate, Replacement of the IETF Executive Director 2. Where Appropriate, Replacement of the IETF Executive Director
position with the Managing Director, IETF Secretariat . . . . 3 position with the Managing Director, IETF Secretariat . . . . 3
3. Remove the IETF Executive Director as an Option . . . . . . . 3 3. Remove the IETF Executive Director as an Option . . . . . . . 4
4. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 4 4. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Obsoleted Documents . . . . . . . . . . . . . . . . . . . 4
4.2. Documents Whose Context is Changed by This Specification 5
4.3. General Description of the IETF Adminstrative Model . . . 5
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . 5 9.1. Normative References . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . 6 9.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 7 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8
A.1. Changes from version -00 (2018-11-15) to -01 . . . . . . 7 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 . . . . . . . . . . . . . . . . 7 posted 2012-12-07) to -02 . . . . . . . . . . . . . . . . 8
A.3. Changes from version -02 (2018-12-07) to -03 . . . . . . 8 A.3. Changes from version -02 (2018-12-07) to -03 . . . . . . 8
A.4. Changes from version -03 (2018-12-12) to -04 . . . . . . 8 A.4. Changes from version -03 (2018-12-12) to -04 . . . . . . 9
A.5. Changes from version -04 (2019-01-17) to -05 . . . . . . 8 A.5. Changes from version -04 (2019-01-17) to -05 . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 A.6. Changes from version -05 (2019-01-31) to -06 . . . . . . 10
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 10 skipping to change at page 3, line 15
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, 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 RFC 3929 which was an
were Experimental or Informational documents that are no longer Experimental document that is no longer relevant and requests that it
relevant (see Section 4). The sections that follow identify the be made Historic. In addition, with the authorization of the IAB, it
details of the relevant documents and the required changes. 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 2. 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
skipping to change at page 4, line 16 skipping to change at page 4, line 25
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.
4. Deprecated Documents 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]]
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. should be reclassified as necessary to avoid confusion. Because none
of them are directly relevant to the IASA 2.0 structure, it is also
requested that all of the documents listed in this section be
reclassified to Historic.
This document deprecates the following: 4.1. Obsoleted Documents
o RFC 3716 [RFC3716], which describes the general administrative This specification obsoletes the following, formerly Experimental,
model of the IETF. documents:
o RFC 3929 [RFC3929], which touches on aspects of the administration RFC 3929 [RFC3929] touches on aspects of the administration of the
of the IETF, such as mentioning the IETF Executive Director. It IETF such as mentioning the IETF Executive Director. It dates to
dates to 2004 and is experimental. 2004; the results of the experiment were never documented in the
RFC Series.
o RFC 3979 [RFC3979], that is updated by [RFC8179], which corrects RFC 4633 [RFC4633] refers to the IETF Executive Director. It
mentions of the IETF Executive Director to the IETF Secretariat. describes a 2006 experiment that ran for 18 months and whose
conclusions were never documented in the RFC Series.
o RFC 4633 [RFC4633], which is an experimental document that refers 4.2. Documents Whose Context is Changed by This Specification
to IETF Executive Director. It describes a 2006 experiment that
ran for 18 months.
o RFC 4879 [RFC4879], that is updated by [RFC8179], which corrects Both of the documents that follow were obsoleted in 2017 by RFC 8179
mentions of the IETF Executive Director to the IETF Secretariat. [RFC8179], which changed mentions of the IETF Executive Director to
point to the IETF Secretariat more generally.
It is also recommended that the above documents be reclassified to o RFC 3979 [RFC3979].
Historic to further reduce the risk of any confusion.
o RFC 4879 [RFC4879].
4.3. General Description of the IETF Adminstrative Model
RFC 3716 [RFC3716] 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 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. He also made several other significant draft in its current form. He also made several other significant
contributions. Bob Hinden also gave the document a careful reading contributions. Bob Hinden also gave the document a careful reading
and made useful suggestions. 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 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.
7. IANA Considerations 7. IANA Considerations
[[CREF1: 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.
8. 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.
9. References 9. References
skipping to change at page 7, line 30 skipping to change at page 8, line 21
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".
[[CREF2: 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 14 skipping to change at page 10, line 5
Terminology" per suggestions from Brian Carpenter and Bob Hinden Terminology" per suggestions from Brian Carpenter and Bob Hinden
and 2019-01-31 WG decision. and 2019-01-31 WG decision.
o Removed CREF from Section 1 (should have been done in -04). The o Removed CREF from Section 1 (should have been done in -04). The
only remaining CREFs are the one in this section (above) that only remaining CREFs are the one in this section (above) that
should probably be preserved through IETF Last Call and notes to should probably be preserved through IETF Last Call and notes to
the RFC Editor. the RFC Editor.
o Updated acknowledgments. o Updated acknowledgments.
A.6. Changes from version -05 (2019-01-31) to -06
o Changes to text about documents that are updated and made
historic, per advice from RFC Editor, WG Chairs, and IAB. This
includes a statement about IAB action of 2019-03-06 that requests
that the RFC Editor move RFC 3716 to Historic but does not
obsolete that Informational report. When minimal changes were
attempted, Section 4 became very hard to read and hence was
restructured and somewhat rewritten (and then further modified to
work around an xml2rfc glitch). Special attention should be paid
to the note at the beginning of that section.
o Updated the Acknowledgments section.
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. 23 change blocks. 
42 lines changed or deleted 87 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/