idnits 2.17.1 draft-ietf-iasa2-consolidated-upd-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document obsoletes RFC4633, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document obsoletes RFC3716, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document obsoletes RFC3929, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC3710, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC4844, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC2418, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC3005, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC2028, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC2028, updated by this document, for RFC5378 checks: 1996-02-22) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 12, 2018) is 1962 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC4071' is mentioned on line 127, but not defined ** Obsolete undefined reference: RFC 4071 (Obsoleted by RFC 8711) -- Possible downref: Non-RFC (?) normative reference: ref. 'LLC-Agreement' ** Downref: Normative reference to an Informational draft: draft-ietf-iasa2-trust-rationale (ref. 'RFC-trust-rationale') ** Obsolete normative reference: RFC 2028 (Obsoleted by RFC 9281) ** Obsolete normative reference: RFC 3005 (Obsoleted by RFC 9245) ** Downref: Normative reference to an Informational RFC: RFC 3710 ** Obsolete normative reference: RFC 4844 (Obsoleted by RFC 8729) ** Obsolete normative reference: RFC 5377 (Obsoleted by RFC 8721) ** Downref: Normative reference to an Informational RFC: RFC 6702 -- Obsolete informational reference (is this intentional?): RFC 3979 (Obsoleted by RFC 8179) -- Obsolete informational reference (is this intentional?): RFC 4879 (Obsoleted by RFC 8179) Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IASA2 J. Klensin, Ed. 3 Internet-Draft December 12, 2018 4 Obsoletes: 3716, 3929, 4633 (if 5 approved) 6 Updates: 2028, 2418, 3005, 3710, 4844, 7 5377, 6702 (if approved) 8 Intended status: Best Current Practice 9 Expires: June 15, 2019 11 Consolidated IASA2-Related Document Updates 12 draft-ietf-iasa2-consolidated-upd-03 14 Abstract 16 In 2018, the IETF began the transition to a new administrative 17 structure and updated its IETF Administrative Support Activity (IASA) 18 to a new "IASA 2.0" structure. In addition to more substantive 19 changes that are described in other documents, the transition to the 20 2018 IETF Administrative Support structure changes several position 21 titles and organizational relationships that are referenced 22 elsewhere. Rather than reissue those referencing documents 23 individually, this specification provides updates to them and 24 deprecates some now-obsolete documents to ensure that there is no 25 confusion due to these changes. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on June 15, 2019. 44 Copyright Notice 46 Copyright (c) 2018 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. Remove Text About the Connection Between the IAOC and IETF 63 Trust . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 3. Replacement of IAOC with IETF Administration LLC . . . . . . 3 65 4. Where Appropriate, Replacement of the IETF Executive Director 66 position with the Managing Director, IETF Secretariat . . . . 4 67 5. Remove the IETF Executive Director as an Option . . . . . . . 4 68 6. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 5 69 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 70 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 71 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 72 10. Security Considerations . . . . . . . . . . . . . . . . . . . 6 73 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 74 11.1. Normative References . . . . . . . . . . . . . . . . . . 6 75 11.2. Informative References . . . . . . . . . . . . . . . . . 7 76 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8 77 A.1. Changes from version -00 (2018-11-15) to -01 . . . . . . 8 78 A.2. Changes from version -01 (dated 2018-12-06 but 79 posted 2012-12-07) to -02 . . . . . . . . . . . . . . . . 9 80 A.3. Changes from version -02 (2018-12-07) to -03 . . . . . . 9 81 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 83 1. Introduction 85 In 2018, the IETF began the transition to a new administrative 86 structure, and updated its IETF Administrative Support Activity 87 (IASA) to a new "IASA 2.0" structure [RFC-Struct]. Key IASA 2.0 88 changes have been specified in a series of documents, including 89 changes to the IETF Trust [RFC-trust-update], the rationale for it 90 [RFC-trust-rationale], a new defining document for the IETF 91 Administration LLC [LLC-Agreement] (informally called the "IETF LLC" 92 or just "the LLC" in places in this document and elsewhere) and 93 adjustments to the procedures for nominations and selections for 94 relevant positions [RFC-7437bis]. 96 In addition to more substantive changes that are described in those 97 and other documents, the IASA 2.0 structure changes several position 98 titles and organizational relationships that are referenced in other 99 documents. Rather than reissue those documents individually, this 100 document provides a unified update to them. 102 This document updates RFCs 2028, 2418, 3005, 3710, 5377, and 6702 103 (citations in context below) to make those terminology and related 104 changes. For clarity, it also obsoletes RFCs 3716 and 3929 which 105 were Experimental or Informational documents that are no longer 106 relevant (see Section 6). The sections that follow identify the 107 details of the relevant documents and the required changes. 109 [[CREF1: Note in Draft: This document lists changes that the WG may 110 choose to process as standalone replacement documents instead. The 111 relevant sections are provided to speed things along should it decide 112 to not do that.]] 114 2. Remove Text About the Connection Between the IAOC and IETF Trust 116 Some documents that discuss the IETF Trust or its relationship to the 117 community describe it, or the Trustees, in relation to the IAOC. 118 That connection must be eliminated to reflect the new IASA 2.0 119 structure. 121 This document applies that change to the following: 123 o RFC 5377 [RFC5377], Advice to the Trustees of the IETF Trust on 124 Rights to Be Granted in IETF Documents. These changes require 125 dropping "made up of the members of the IAOC [RFC4371]" after 126 "board of trustees" in the first paragraph of Section 1 and "which 127 is made up of the members of the IAOC, as described in [RFC4071] 128 and [RFC4371]" in the first paragraph of Section 3. 129 [[CREF2: RFC Editor please note that the bracketed strings above 130 are quoted text, not references. ]] 132 3. Replacement of IAOC with IETF Administration LLC 134 All mentions of the IETF Administrative Oversight Committee (IAOC) 135 that are not removed by the prior section, shall be updated and 136 replaced by the IETF Administration LLC (IETF-LLC). This is 137 necessary because the IAOC is phased out under the IASA 2.0 138 structure. 140 This document applies that change to the following: 142 o RFC 4844 [RFC4844], the RFC Series and RFC Editor Sections 3.3, 143 3.4, and 4. 145 4. Where Appropriate, Replacement of the IETF Executive Director 146 position with the Managing Director, IETF Secretariat 148 Under the IASA 2.0 structure, most of the responsibilities of the 149 former position of IETF Executive Director been assigned to a new 150 position (or at least title) of Managing Director of the IETF 151 Secretariat. An "Executive Director" title is now associated with 152 different, and largely new, responsibilities as an Officer of the 153 IETF Administration LLC. These changes are described in the 154 description of the new structural arrangements [RFC-Struct]. 156 This document applies that change to the following: 158 o RFC 2028, The Organizations Involved in the IETF Standards Process 159 [RFC2028], Section 3.3. 161 o RFC 2418, IETF Working Group Guidelines and Procedures [RFC2418] 163 o RFC 3710, An IESG Charter, Section 2[RFC3710]. 165 o RFC 6702, Promoting Compliance with Intellectual Property Rights 166 (IPR) Disclosure Rules, Section 5 [RFC6702]. 168 Note that the current description of the Internet Standards Process 169 [RFC2026] does not require an update by this document for this 170 purpose because the reference to the IETF Executive Director in RFC 171 2026 was replaced by a document that precedes the current effort 172 [RFC3979] and that was, in turn, obsoleted by RFC 8179 [RFC8179]. 174 [[CREF3: Note in Draft: Bob Hinden's note of November 10, 2018 11:37 175 +0900 indicates that RFC4844 should continue to reference the IETF 176 Executive Director.]] 178 5. Remove the IETF Executive Director as an Option 180 In a few cases, it is no longer appropriate for either the Managing 181 Director, IETF Secretariat (former IETF Executive Director position) 182 or the new IETF Executive Director (for the LLC) to perform a 183 particular historical function. The relevant documents are updated 184 to remove the IETF Executive Director from the list of people with 185 specific responsibilities or authority. Those documents will not be 186 updated to use "Managing Director, IETF Secretariat" but, instead, 187 the mention of the position will simply be dropped. 189 This document applies that change to the following: 191 o RFC 3005, IETF Discussion List Charter [RFC3005], section titled 192 "Charter for the IETF Discussion List". This document is modified 193 to remove the authorization for the IETF Executive Director to 194 restrict people from posting, etc. 196 6. Deprecated Documents 198 The IASA2 Working Group has also identified several RFCs that no 199 longer apply as a result of the change to the new IASA 2.0 structure. 200 The result is that several informational, experimental, or other RFCs 201 can be deprecated. 203 This document deprecates the following: 205 o RFC 3716 [RFC3716], which describes the general administrative 206 model of the IETF. 208 o RFC 3929 [RFC3929], which touches on aspects of the administration 209 of the IETF, such as mentioning the IETF Executive Director. It 210 dates to 2004 and is experimental. 212 o RFC 3979 [RFC3979], that is updated by [RFC8179], which corrects 213 mentions of the IETF Executive Director to the IETF Secretariat. 215 o RFC 4633 [RFC4633], which is an experimental document that refers 216 to IETF Executive Director. It describes a 2006 experiment that 217 ran for 18 months. 219 o RFC 4879 [RFC4879], that is updated by [RFC8179], which corrects 220 mentions of the IETF Executive Director to the IETF Secretariat. 222 It is also recommended that the above documents be reclassified to 223 Historic to further reduce the risk of any confusion. 225 7. Acknowledgments 227 Brian Carpenter's careful checking and identification of documents 228 that did, and did not, require consideration was essential to the 229 draft in its current form. 231 8. Contributors 233 Jason Livingood did the hard work of identifying the documents that 234 required updating and supplied considerable text used in this 235 document. 237 9. IANA Considerations 239 [[CREF4: RFC Editor: Please remove this section before publication.]] 241 This memo includes no requests to or actions for IANA. 243 10. Security Considerations 245 The changes specified in this document are matters of terminology and 246 organizational structure derived from documents it references. It 247 should have no effect on Internet security. 249 11. References 251 11.1. Normative References 253 [LLC-Agreement] 254 IETF Administration LLC, "Limited Liability Company 255 Agreement of IETF Administration LLC", August 2018, 256 . 259 [RFC-7437bis] 260 Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood, 261 Ed., "IAB, IESG, and IETF LLC Selection, Confirmation, and 262 Recall Process: Operation of the IETF Nominating and 263 Recall Committees", 2018, 264 . 267 [RFC-Struct] 268 Haberman, B., Hall, J., and J. Livingood, "Structure of 269 the IETF Administrative Support Activity, Version 2.0", 270 December 2018, . 273 [RFC-trust-rationale] 274 Arkko, J., "Discussion of the IASA 2.0 Changes as They 275 Relate to the IETF Trust", 2018, 276 . 279 [RFC-trust-update] 280 Arkko, J. and T. Hardie, "Update to the Process for 281 Selection of Trustees for the IETF Trust", 2018, 282 . 285 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 286 the IETF Standards Process", BCP 11, RFC 2028, 287 DOI 10.17487/RFC2028, October 1996, 288 . 290 [RFC2418] Bradner, S., "IETF Working Group Guidelines and 291 Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418, 292 September 1998, . 294 [RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, 295 RFC 3005, DOI 10.17487/RFC3005, November 2000, 296 . 298 [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, 299 DOI 10.17487/RFC3710, February 2004, 300 . 302 [RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC 303 Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844, 304 July 2007, . 306 [RFC5377] Halpern, J., Ed., "Advice to the Trustees of the IETF 307 Trust on Rights to Be Granted in IETF Documents", 308 RFC 5377, DOI 10.17487/RFC5377, November 2008, 309 . 311 [RFC6702] Polk, T. and P. Saint-Andre, "Promoting Compliance with 312 Intellectual Property Rights (IPR) Disclosure Rules", 313 RFC 6702, DOI 10.17487/RFC6702, August 2012, 314 . 316 11.2. Informative References 318 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 319 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 320 . 322 [RFC3716] IAB Advisory Committee, "The IETF in the Large: 323 Administration and Execution", RFC 3716, 324 DOI 10.17487/RFC3716, March 2004, 325 . 327 [RFC3929] Hardie, T., "Alternative Decision Making Processes for 328 Consensus-Blocked Decisions in the IETF", RFC 3929, 329 DOI 10.17487/RFC3929, October 2004, 330 . 332 [RFC3979] Bradner, S., Ed., "Intellectual Property Rights in IETF 333 Technology", RFC 3979, DOI 10.17487/RFC3979, March 2005, 334 . 336 [RFC4633] Hartman, S., "Experiment in Long-Term Suspensions From 337 Internet Engineering Task Force (IETF) Mailing Lists", 338 RFC 4633, DOI 10.17487/RFC4633, August 2006, 339 . 341 [RFC4879] Narten, T., "Clarification of the Third Party Disclosure 342 Procedure in RFC 3979", RFC 4879, DOI 10.17487/RFC4879, 343 April 2007, . 345 [RFC8179] Bradner, S. and J. Contreras, "Intellectual Property 346 Rights in IETF Technology", BCP 79, RFC 8179, 347 DOI 10.17487/RFC8179, May 2017, 348 . 350 Appendix A. Change Log 352 RFC Editor: Please remove this appendix before publication. 354 A.1. Changes from version -00 (2018-11-15) to -01 356 o Removed RFCs 3979 and 4879 from the "obsoletes" list because they 357 had already been obsoleted (by 8179). It also removes RFC 8179 358 from the "updates" list because 8179 uses "IETF Secretariat" 359 terminology rather than "IETF Executive Director". 361 [[CREF5: Note in Draft: That suggests an idea which might 362 considerably mitigate the name confusion issue: Instead of 363 singling out the Managing Director of the Secretariat as a named 364 individual, perhaps we should be referring to the Secretariat 365 itself, leaving the contact point or address up to them as an 366 internal administrative matter. Just a thought. --JcK]] 368 o Added text to explain why RFC 2026 is not on the hit list. 370 o Added an acknowledgment to Brian Carpenter. If he catches another 371 batch of errors and supplies text, he gets promoted to 372 Contributor. 374 o Adjusted reference [RFC-Struct] to point to 4071bis. 376 o Minor editorial corrections and changes. 378 A.2. Changes from version -01 (dated 2018-12-06 but posted 2012-12-07) 379 to -02 381 I accidentally omitted RFC 4844 from the document header "updates" 382 list in Version 01 and noticed that in response to an unrelated 383 question almost immediately after posting. The correction seemed 384 important enough to justify almost immediate re-posting. Changes are 385 only that header, the document file name, and the date. --JcK 387 A.3. Changes from version -02 (2018-12-07) to -03 389 o Removed discussion and pointers to RFC 7500 - IAB will publish 390 separately. 392 o Added text to describe (very superficially) RFC 3716. That 393 document was obsoleted in the previous version but not described. 395 o Removed rant about titles and responsibilities from Section 4 and 396 a subsequent editorial note I hope it is no longer needed --JcK. 397 In additional, several blocks of text that were commented out in 398 earlier versions of the XML have been removed entirely. 400 Author's Address 402 John C Klensin (editor) 403 1770 Massachusetts Ave, Ste 322 404 Cambridge, MA 02140 405 USA 407 Phone: +1 617 245 1457 408 Email: john-ietf@jck.com