| < draft-ietf-iasa2-consolidated-upd-06.txt | draft-ietf-iasa2-consolidated-upd-07.txt > | |||
|---|---|---|---|---|
| IASA2 J. Klensin, Ed. | IASA2 J. Klensin, Ed. | |||
| Internet-Draft March 7, 2019 | Internet-Draft March 11, 2019 | |||
| Obsoletes: 3929, 4633 (if approved) | Updates: 2028, 2418, 3005, 3710, 3929, | |||
| Updates: 2028, 2418, 3005, 3710, 6702 | 4633, 6702 (if approved) | |||
| (if approved) | ||||
| Intended status: Best Current Practice | Intended status: Best Current Practice | |||
| Expires: September 8, 2019 | Expires: September 12, 2019 | |||
| Consolidated IASA 2.0 Updates of IETF Administrative Terminology | Consolidated IASA 2.0 Updates of IETF Administrative Terminology | |||
| draft-ietf-iasa2-consolidated-upd-06 | draft-ietf-iasa2-consolidated-upd-07 | |||
| 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 42 ¶ | skipping to change at page 1, line 41 ¶ | |||
| 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 September 8, 2019. | This Internet-Draft will expire on September 12, 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 22 ¶ | skipping to change at page 2, line 19 ¶ | |||
| 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 . . . . . . . 4 | |||
| 4. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 4 | 4. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 4 | |||
| 4.1. Obsoleted Documents . . . . . . . . . . . . . . . . . . . 4 | 4.1. Documents Whose Context is Changed by This Specification 4 | |||
| 4.2. Documents Whose Context is Changed by This Specification 5 | 4.2. General Description of the IETF Adminstrative Model . . . 5 | |||
| 4.3. General Description of the IETF Adminstrative Model . . . 5 | ||||
| 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 | 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 | 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 | |||
| 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 9.1. Normative References . . . . . . . . . . . . . . . . . . 6 | 9.1. Normative References . . . . . . . . . . . . . . . . . . 5 | |||
| 9.2. Informative References . . . . . . . . . . . . . . . . . 7 | 9.2. Informative References . . . . . . . . . . . . . . . . . 7 | |||
| Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8 | Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 7 | |||
| A.1. Changes from version -00 (2018-11-15) to -01 . . . . . . 8 | 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 . . . . . . . . . . . . . . . . 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 . . . . . . 9 | A.4. Changes from version -03 (2018-12-12) to -04 . . . . . . 8 | |||
| A.5. Changes from version -04 (2019-01-17) to -05 . . . . . . 9 | A.5. Changes from version -04 (2019-01-17) to -05 . . . . . . 9 | |||
| A.6. Changes from version -05 (2019-01-31) to -06 . . . . . . 10 | A.6. Changes from version -05 (2019-01-31) to -06 . . . . . . 9 | |||
| A.7. Changes from version -06 (2019-03-06) to -07 . . . . . . 10 | ||||
| Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 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 | |||
| skipping to change at page 3, line 13 ¶ | skipping to change at page 3, line 11 ¶ | |||
| 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, and 6702 | This document updates RFCs 2028, 2418, 3005, 3710, 3929, 4633, and | |||
| (citations in context below) to make those terminology and related | 6702 (citations in context below) to make those terminology and | |||
| changes. For clarity, it also obsoletes RFC 3929 which was an | related changes. In addition, with the authorization of the IAB, it | |||
| Experimental document that is no longer relevant and requests that it | ||||
| be made Historic. In addition, with the authorization of the IAB, it | ||||
| requests that the Informational RFC 3716 be made Historic (see | requests that the Informational RFC 3716 be made Historic (see | |||
| Section 4). The sections that follow identify the details of the | Section 4). The sections that follow identify the details of the | |||
| relevant documents and the required changes. | 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 | |||
| description of the new structural arrangements [RFC-Struct]. | description of the new structural arrangements [RFC-Struct]. | |||
| 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. | |||
| o RFC 2418, IETF Working Group Guidelines and Procedures [RFC2418] | o RFC 2418, IETF Working Group Guidelines and Procedures [RFC2418], | |||
| Section 1. | ||||
| o RFC 3710, An IESG Charter, Section 2[RFC3710]. | o RFC 3710, An IESG Charter, Section 2 [RFC3710]. | |||
| o RFC 3929, Alternative Decision Making Processes for Consensus- | ||||
| Blocked Decisions in the IETF [RFC3929], Sections 4.1.1 and 4.3 | ||||
| (twice). | ||||
| o RFC 4633, Experiment in Long-Term Suspensions From Internet | ||||
| Engineering Task Force (IETF) Mailing Lists [RFC4633], Section 1. | ||||
| 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]. | |||
| skipping to change at page 4, line 33 ¶ | skipping to change at page 4, line 35 ¶ | |||
| 4. Deprecated Documents | 4. Deprecated Documents | |||
| [[CREF1: Note to the WG, IESG, and RFC Editor: I hope this section | [[CREF1: Note to the WG, IESG, and RFC Editor: I hope this section | |||
| correctly reflects the conclusions of discussions in and with the WG. | correctly reflects the conclusions of discussions in and with the WG. | |||
| If it does not, the issues should certainly be identified and fixed. | If it does not, the issues should certainly be identified and fixed. | |||
| However, details of some of the actions are the responsibility of the | 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 | RFC Editor and RFC 3716 is an IAB document containing the report of | |||
| an IAB Advisory Committee. If that text, especially the phrasing of | an IAB Advisory Committee. If that text, especially the phrasing of | |||
| various actions, is not quite right, I hope those involved can sort | various actions, is not quite right, I hope those involved can sort | |||
| the language out with the RFC Editor rather than requiring that the | the language out with the RFC Editor rather than requiring that the | |||
| WG iterate on the draft. --JcK, editor]] | WG iterate on the draft. --JcK, editor. RFC Editor: should this | |||
| paragraph reach you, please remove it.]] | ||||
| 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. | ||||
| The result is that several Informational, Experimental, or other RFCs | ||||
| 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. | ||||
| 4.1. Obsoleted Documents | ||||
| This specification obsoletes the following, formerly Experimental, | ||||
| documents: | ||||
| RFC 3929 [RFC3929] touches on aspects of the administration of the | ||||
| IETF such as mentioning the IETF Executive Director. It dates to | ||||
| 2004; the results of the experiment were never documented in the | ||||
| RFC Series. | ||||
| RFC 4633 [RFC4633] refers to the IETF Executive Director. It | ||||
| describes a 2006 experiment that ran for 18 months and whose | ||||
| conclusions were never documented in the RFC Series. | ||||
| 4.2. Documents Whose Context is Changed by This Specification | 4.1. Documents Whose Context is Changed by This Specification | |||
| Both of the documents that follow were obsoleted in 2017 by RFC 8179 | Both of the documents that follow were obsoleted in 2017 by RFC 8179 | |||
| [RFC8179], which changed mentions of the IETF Executive Director to | [RFC8179], which changed mentions of the IETF Executive Director to | |||
| point to the IETF Secretariat more generally. | point to the IETF Secretariat more generally. | |||
| o RFC 3979 [RFC3979]. | o RFC 3979 [RFC3979]. | |||
| o RFC 4879 [RFC4879]. | o RFC 4879 [RFC4879]. | |||
| 4.3. General Description of the IETF Adminstrative Model | 4.2. General Description of the IETF Adminstrative Model | |||
| RFC 3716 [RFC3716] is a report of an IAB Advisory Committee that | 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 | 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. | 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, | The IAB approved a proposal to move RFC 3716 to Historic on March 6, | |||
| 2019. | 2019. | |||
| 5. Acknowledgments | 5. Acknowledgments | |||
| Brian Carpenter's careful checking and identification of documents | Brian Carpenter's careful checking and identification of documents | |||
| skipping to change at page 10, line 19 ¶ | skipping to change at page 10, line 5 ¶ | |||
| includes a statement about IAB action of 2019-03-06 that requests | includes a statement about IAB action of 2019-03-06 that requests | |||
| that the RFC Editor move RFC 3716 to Historic but does not | that the RFC Editor move RFC 3716 to Historic but does not | |||
| obsolete that Informational report. When minimal changes were | obsolete that Informational report. When minimal changes were | |||
| attempted, Section 4 became very hard to read and hence was | attempted, Section 4 became very hard to read and hence was | |||
| restructured and somewhat rewritten (and then further modified to | restructured and somewhat rewritten (and then further modified to | |||
| work around an xml2rfc glitch). Special attention should be paid | work around an xml2rfc glitch). Special attention should be paid | |||
| to the note at the beginning of that section. | to the note at the beginning of that section. | |||
| o Updated the Acknowledgments section. | o Updated the Acknowledgments section. | |||
| A.7. Changes from version -06 (2019-03-06) to -07 | ||||
| o Moved RFCs 3929 and 4633 from "obsoleted" to "updated" and | ||||
| stripped text requested that they be made Historic at the | ||||
| direction of the IETF Chair, WG Co-chair, and an author. | ||||
| o Added a section number for a document listed in Section 2 that was | ||||
| missing. | ||||
| o Added some notes to the RFC Editor and others. | ||||
| o Updated the 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. 16 change blocks. | ||||
| 49 lines changed or deleted | 46 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||