< draft-ietf-iasa2-consolidated-upd-04.txt   draft-ietf-iasa2-consolidated-upd-05.txt >
IASA2 J. Klensin, Ed. IASA2 J. Klensin, Ed.
Internet-Draft January 17, 2019 Internet-Draft January 31, 2019
Obsoletes: 3716, 3929, 4633 (if Obsoletes: 3716, 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: July 21, 2019 Expires: August 4, 2019
Consolidated IASA2-Related Document Updates Consolidated IASA 2.0 Updates of IETF Administrative Terminology
draft-ietf-iasa2-consolidated-upd-04 draft-ietf-iasa2-consolidated-upd-05
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 July 21, 2019. This Internet-Draft will expire on August 4, 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 . . . . . . . 4 3. Remove the IETF Executive Director as an Option . . . . . . . 3
4. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 4 4. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
9.1. Normative References . . . . . . . . . . . . . . . . . . 5 9.1. Normative References . . . . . . . . . . . . . . . . . . 5
9.2. Informative References . . . . . . . . . . . . . . . . . 6 9.2. Informative References . . . . . . . . . . . . . . . . . 6
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 7 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 7
A.1. Changes from version -00 (2018-11-15) to -01 . . . . . . 7 A.1. Changes from version -00 (2018-11-15) to -01 . . . . . . 7
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 . . . . . . . . . . . . . . . . 8 posted 2012-12-07) to -02 . . . . . . . . . . . . . . . . 7
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 . . . . . . 8
A.5. Changes from version -04 (2019-01-17) to -05 . . . . . . 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 14 skipping to change at page 3, line 15
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 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 4). 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
choose to process as standalone replacement documents instead. The
relevant sections are provided to speed things along should it decide
to not do that.]]
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
description of the new structural arrangements [RFC-Struct]. description of the new structural arrangements [RFC-Struct].
skipping to change at page 5, line 9 skipping to change at page 4, line 47
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.
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. 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.
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
[[CREF2: RFC Editor: Please remove this section before publication.]] [[CREF1: 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 39 skipping to change at page 7, line 30
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".
[[CREF3: Note in Draft: That suggests an idea which might [[CREF2: 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 7 skipping to change at page 8, line 47
As documents and references are shuffled in and out of this As documents and references are shuffled in and out of this
one, it occurred to me that having a non-normative appendix one, it occurred to me that having a non-normative appendix
somewhere that would identify all of the documents containing somewhere that would identify all of the documents containing
changes to reflect the IASA 1.x to 2.0 transition would be of 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 great help to any future historian trying to understand what we
did and probably helpful to the IETF if some of these changes did and probably helpful to the IETF if some of these changes
don't work out and/or require further tuning. After a brief don't work out and/or require further tuning. After a brief
discussion, Jason and I concluded that appendix did not belong discussion, Jason and I concluded that appendix did not belong
in this iteration of this document. in this iteration of this document.
A.5. Changes from version -04 (2019-01-17) to -05
o Changed title from "Consolidated IASA2-Related Document Updates"
to "Consolidated IASA 2.0 Updates of IETF Administrative
Terminology" per suggestions from Brian Carpenter and Bob Hinden
and 2019-01-31 WG decision.
o Removed CREF from Section 1 (should have been done in -04). The
only remaining CREFs are the one in this section (above) that
should probably be preserved through IETF Last Call and notes to
the RFC Editor.
o Updated acknowledgments.
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. 13 change blocks. 
16 lines changed or deleted 28 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/