idnits 2.17.1 draft-ietf-iasa2-consolidated-upd-06.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 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 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 (March 7, 2019) is 1870 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) -- 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 ** 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: 5 errors (**), 0 flaws (~~), 1 warning (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IASA2 J. Klensin, Ed. 3 Internet-Draft March 7, 2019 4 Obsoletes: 3929, 4633 (if approved) 5 Updates: 2028, 2418, 3005, 3710, 6702 6 (if approved) 7 Intended status: Best Current Practice 8 Expires: September 8, 2019 10 Consolidated IASA 2.0 Updates of IETF Administrative Terminology 11 draft-ietf-iasa2-consolidated-upd-06 13 Abstract 15 In 2018, the IETF began the transition to a new administrative 16 structure and updated its IETF Administrative Support Activity (IASA) 17 to a new "IASA 2.0" structure. In addition to more substantive 18 changes that are described in other documents, the transition to the 19 2018 IETF Administrative Support structure changes several position 20 titles and organizational relationships that are referenced 21 elsewhere. Rather than reissue those referencing documents 22 individually, this specification provides updates to them and 23 deprecates some now-obsolete documents to ensure that there is no 24 confusion due to these changes. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on September 8, 2019. 43 Copyright Notice 45 Copyright (c) 2019 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (https://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. Where Appropriate, Replacement of the IETF Executive Director 62 position with the Managing Director, IETF Secretariat . . . . 3 63 3. Remove the IETF Executive Director as an Option . . . . . . . 4 64 4. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 4 65 4.1. Obsoleted Documents . . . . . . . . . . . . . . . . . . . 4 66 4.2. Documents Whose Context is Changed by This Specification 5 67 4.3. General Description of the IETF Adminstrative Model . . . 5 68 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 69 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 70 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 71 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 72 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 73 9.1. Normative References . . . . . . . . . . . . . . . . . . 6 74 9.2. Informative References . . . . . . . . . . . . . . . . . 7 75 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8 76 A.1. Changes from version -00 (2018-11-15) to -01 . . . . . . 8 77 A.2. Changes from version -01 (dated 2018-12-06 but 78 posted 2012-12-07) to -02 . . . . . . . . . . . . . . . . 8 79 A.3. Changes from version -02 (2018-12-07) to -03 . . . . . . 8 80 A.4. Changes from version -03 (2018-12-12) to -04 . . . . . . 9 81 A.5. Changes from version -04 (2019-01-17) to -05 . . . . . . 9 82 A.6. Changes from version -05 (2019-01-31) to -06 . . . . . . 10 83 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 85 1. Introduction 87 In 2018, the IETF began the transition to a new administrative 88 structure, and updated its IETF Administrative Support Activity 89 (IASA) to a new "IASA 2.0" structure [RFC-Struct]. Key IASA 2.0 90 changes have been specified in a series of documents, including 91 changes to the IETF Trust [RFC-trust-update], the rationale for it 92 [RFC-trust-rationale], a new defining document for the IETF 93 Administration LLC [LLC-Agreement] (informally called the "IETF LLC" 94 or just "the LLC" in places in this document and elsewhere) and 95 adjustments to the procedures for nominations and selections for 96 relevant positions [RFC-7437bis]. 98 In addition to more substantive changes that are described in those 99 and other documents, the IASA 2.0 structure changes several position 100 titles and organizational relationships that are referenced in other 101 documents. Rather than reissue those documents individually, this 102 document provides a unified update to them. 104 This document updates RFCs 2028, 2418, 3005, 3710, and 6702 105 (citations in context below) to make those terminology and related 106 changes. For clarity, it also obsoletes RFC 3929 which was an 107 Experimental document that is no longer relevant and requests that it 108 be made Historic. In addition, with the authorization of the IAB, it 109 requests that the Informational RFC 3716 be made Historic (see 110 Section 4). The sections that follow identify the details of the 111 relevant documents and the required changes. 113 2. Where Appropriate, Replacement of the IETF Executive Director 114 position with the Managing Director, IETF Secretariat 116 Under the IASA 2.0 structure, most of the responsibilities of the 117 former position of IETF Executive Director been assigned to a new 118 position (or at least title) of Managing Director of the IETF 119 Secretariat. An "Executive Director" title is now associated with 120 different, and largely new, responsibilities as an Officer of the 121 IETF Administration LLC. These changes are described in the 122 description of the new structural arrangements [RFC-Struct]. 124 This document applies that change to the following: 126 o RFC 2028, The Organizations Involved in the IETF Standards Process 127 [RFC2028], Section 3.3. 129 o RFC 2418, IETF Working Group Guidelines and Procedures [RFC2418] 131 o RFC 3710, An IESG Charter, Section 2[RFC3710]. 133 o RFC 6702, Promoting Compliance with Intellectual Property Rights 134 (IPR) Disclosure Rules, Section 5 [RFC6702]. 136 Note that the current description of the Internet Standards Process 137 [RFC2026] does not require an update by this document for this 138 purpose because the reference to the IETF Executive Director in RFC 139 2026 was replaced by a document that precedes the current effort 140 [RFC3979] and that was, in turn, obsoleted by RFC 8179 [RFC8179]. 142 3. Remove the IETF Executive Director as an Option 144 In a few cases, it is no longer appropriate for either the Managing 145 Director, IETF Secretariat (former IETF Executive Director position) 146 or the new IETF Executive Director (for the LLC) to perform a 147 particular historical function. The relevant documents are updated 148 to remove the IETF Executive Director from the list of people with 149 specific responsibilities or authority. Those documents will not be 150 updated to use "Managing Director, IETF Secretariat" but, instead, 151 the mention of the position will simply be dropped. 153 This document applies that change to the following: 155 o RFC 3005, IETF Discussion List Charter [RFC3005], section titled 156 "Charter for the IETF Discussion List". This document is modified 157 to remove the authorization for the IETF Executive Director to 158 restrict people from posting, etc. 160 4. Deprecated Documents 162 [[CREF1: Note to the WG, IESG, and RFC Editor: I hope this section 163 correctly reflects the conclusions of discussions in and with the WG. 164 If it does not, the issues should certainly be identified and fixed. 165 However, details of some of the actions are the responsibility of the 166 RFC Editor and RFC 3716 is an IAB document containing the report of 167 an IAB Advisory Committee. If that text, especially the phrasing of 168 various actions, is not quite right, I hope those involved can sort 169 the language out with the RFC Editor rather than requiring that the 170 WG iterate on the draft. --JcK, editor]] 172 The IASA2 Working Group has also identified several RFCs that no 173 longer apply as a result of the change to the new IASA 2.0 structure. 174 The result is that several Informational, Experimental, or other RFCs 175 should be reclassified as necessary to avoid confusion. Because none 176 of them are directly relevant to the IASA 2.0 structure, it is also 177 requested that all of the documents listed in this section be 178 reclassified to Historic. 180 4.1. Obsoleted Documents 182 This specification obsoletes the following, formerly Experimental, 183 documents: 185 RFC 3929 [RFC3929] touches on aspects of the administration of the 186 IETF such as mentioning the IETF Executive Director. It dates to 187 2004; the results of the experiment were never documented in the 188 RFC Series. 190 RFC 4633 [RFC4633] refers to the IETF Executive Director. It 191 describes a 2006 experiment that ran for 18 months and whose 192 conclusions were never documented in the RFC Series. 194 4.2. Documents Whose Context is Changed by This Specification 196 Both of the documents that follow were obsoleted in 2017 by RFC 8179 197 [RFC8179], which changed mentions of the IETF Executive Director to 198 point to the IETF Secretariat more generally. 200 o RFC 3979 [RFC3979]. 202 o RFC 4879 [RFC4879]. 204 4.3. General Description of the IETF Adminstrative Model 206 RFC 3716 [RFC3716] is a report of an IAB Advisory Committee that 207 served as a starting point for the work that led to the original IASA 208 structure. That report is an IAB document rather than an IETF one. 209 The IAB approved a proposal to move RFC 3716 to Historic on March 6, 210 2019. 212 5. Acknowledgments 214 Brian Carpenter's careful checking and identification of documents 215 that did, and did not, require consideration was essential to the 216 draft in its current form. He also made several other significant 217 contributions. Bob Hinden also gave the document a careful reading 218 and made useful suggestions. In additional to the above, Alissa 219 Cooper, Eliot Lear, Heather Flanagan (the RFC Series Editor), and the 220 current membership to the IAB helped sort out the handing of RFC 221 3716. 223 6. Contributors 225 Jason Livingood did the hard work of identifying the documents that 226 required updating and supplied considerable text used in this 227 document. 229 7. IANA Considerations 231 [[CREF2: RFC Editor: Please remove this section before publication.]] 233 This memo includes no requests to or actions for IANA. 235 8. Security Considerations 237 The changes specified in this document are matters of terminology and 238 organizational structure derived from documents it references. It 239 should have no effect on Internet security. 241 9. References 243 9.1. Normative References 245 [LLC-Agreement] 246 IETF Administration LLC, "Limited Liability Company 247 Agreement of IETF Administration LLC", August 2018, 248 . 251 [RFC-7437bis] 252 Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood, 253 Ed., "IAB, IESG, and IETF LLC Selection, Confirmation, and 254 Recall Process: Operation of the IETF Nominating and 255 Recall Committees", 2018, 256 . 259 [RFC-Struct] 260 Haberman, B., Hall, J., and J. Livingood, "Structure of 261 the IETF Administrative Support Activity, Version 2.0", 262 December 2018, . 265 [RFC-trust-rationale] 266 Arkko, J., "Discussion of the IASA 2.0 Changes as They 267 Relate to the IETF Trust", 2018, 268 . 271 [RFC-trust-update] 272 Arkko, J. and T. Hardie, "Update to the Process for 273 Selection of Trustees for the IETF Trust", 2018, 274 . 277 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 278 the IETF Standards Process", BCP 11, RFC 2028, 279 DOI 10.17487/RFC2028, October 1996, 280 . 282 [RFC2418] Bradner, S., "IETF Working Group Guidelines and 283 Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418, 284 September 1998, . 286 [RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, 287 RFC 3005, DOI 10.17487/RFC3005, November 2000, 288 . 290 [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, 291 DOI 10.17487/RFC3710, February 2004, 292 . 294 [RFC6702] Polk, T. and P. Saint-Andre, "Promoting Compliance with 295 Intellectual Property Rights (IPR) Disclosure Rules", 296 RFC 6702, DOI 10.17487/RFC6702, August 2012, 297 . 299 9.2. Informative References 301 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 302 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 303 . 305 [RFC3716] IAB Advisory Committee, "The IETF in the Large: 306 Administration and Execution", RFC 3716, 307 DOI 10.17487/RFC3716, March 2004, 308 . 310 [RFC3929] Hardie, T., "Alternative Decision Making Processes for 311 Consensus-Blocked Decisions in the IETF", RFC 3929, 312 DOI 10.17487/RFC3929, October 2004, 313 . 315 [RFC3979] Bradner, S., Ed., "Intellectual Property Rights in IETF 316 Technology", RFC 3979, DOI 10.17487/RFC3979, March 2005, 317 . 319 [RFC4633] Hartman, S., "Experiment in Long-Term Suspensions From 320 Internet Engineering Task Force (IETF) Mailing Lists", 321 RFC 4633, DOI 10.17487/RFC4633, August 2006, 322 . 324 [RFC4879] Narten, T., "Clarification of the Third Party Disclosure 325 Procedure in RFC 3979", RFC 4879, DOI 10.17487/RFC4879, 326 April 2007, . 328 [RFC8179] Bradner, S. and J. Contreras, "Intellectual Property 329 Rights in IETF Technology", BCP 79, RFC 8179, 330 DOI 10.17487/RFC8179, May 2017, 331 . 333 Appendix A. Change Log 335 RFC Editor: Please remove this appendix before publication. 337 A.1. Changes from version -00 (2018-11-15) to -01 339 o Removed RFCs 3979 and 4879 from the "obsoletes" list because they 340 had already been obsoleted (by 8179). It also removes RFC 8179 341 from the "updates" list because 8179 uses "IETF Secretariat" 342 terminology rather than "IETF Executive Director". 344 [[CREF3: Note in Draft: That suggests an idea which might 345 considerably mitigate the name confusion issue: Instead of 346 singling out the Managing Director of the Secretariat as a named 347 individual, perhaps we should be referring to the Secretariat 348 itself, leaving the contact point or address up to them as an 349 internal administrative matter. Just a thought. --JcK]] 351 o Added text to explain why RFC 2026 is not on the hit list. 353 o Added an acknowledgment to Brian Carpenter. If he catches another 354 batch of errors and supplies text, he gets promoted to 355 Contributor. 357 o Adjusted reference [RFC-Struct] to point to 4071bis. 359 o Minor editorial corrections and changes. 361 A.2. Changes from version -01 (dated 2018-12-06 but posted 2012-12-07) 362 to -02 364 I accidentally omitted RFC 4844 from the document header "updates" 365 list in Version 01 and noticed that in response to an unrelated 366 question almost immediately after posting. The correction seemed 367 important enough to justify almost immediate re-posting. Changes are 368 only that header, the document file name, and the date. --JcK 370 A.3. Changes from version -02 (2018-12-07) to -03 372 o Removed discussion and pointers to RFC 7500 - IAB will publish 373 separately. 375 o Added text to describe (very superficially) RFC 3716. That 376 document was obsoleted in the previous version but not described. 378 o Removed rant about titles and responsibilities from Section 2 and 379 a subsequent editorial note I hope it is no longer needed --JcK. 380 In additional, several blocks of text that were commented out in 381 earlier versions of the XML have been removed entirely. 383 A.4. Changes from version -03 (2018-12-12) to -04 385 o Removed RFC 4844 from the update list and discussion because the 386 consensus in the WG seemed to be that it (and the RFC Editor) 387 should be handled separately. 389 o Removed RFC 5377 from the update list and discussion because it 390 involves the Trust. 392 o Editor's note in draft: 394 The above changes and the earlier removal of RFC 7500 so the 395 IAB could publish it own document completely eliminate the 396 earlier Sections 2 and 3. That may call for a revision of the 397 Introduction and/or Abstract, but I have not done a review for 398 this iteration of whether such changes are needed. 400 As documents and references are shuffled in and out of this 401 one, it occurred to me that having a non-normative appendix 402 somewhere that would identify all of the documents containing 403 changes to reflect the IASA 1.x to 2.0 transition would be of 404 great help to any future historian trying to understand what we 405 did and probably helpful to the IETF if some of these changes 406 don't work out and/or require further tuning. After a brief 407 discussion, Jason and I concluded that appendix did not belong 408 in this iteration of this document. 410 A.5. Changes from version -04 (2019-01-17) to -05 412 o Changed title from "Consolidated IASA2-Related Document Updates" 413 to "Consolidated IASA 2.0 Updates of IETF Administrative 414 Terminology" per suggestions from Brian Carpenter and Bob Hinden 415 and 2019-01-31 WG decision. 417 o Removed CREF from Section 1 (should have been done in -04). The 418 only remaining CREFs are the one in this section (above) that 419 should probably be preserved through IETF Last Call and notes to 420 the RFC Editor. 422 o Updated acknowledgments. 424 A.6. Changes from version -05 (2019-01-31) to -06 426 o Changes to text about documents that are updated and made 427 historic, per advice from RFC Editor, WG Chairs, and IAB. This 428 includes a statement about IAB action of 2019-03-06 that requests 429 that the RFC Editor move RFC 3716 to Historic but does not 430 obsolete that Informational report. When minimal changes were 431 attempted, Section 4 became very hard to read and hence was 432 restructured and somewhat rewritten (and then further modified to 433 work around an xml2rfc glitch). Special attention should be paid 434 to the note at the beginning of that section. 436 o Updated the Acknowledgments section. 438 Author's Address 440 John C Klensin (editor) 441 1770 Massachusetts Ave, Ste 322 442 Cambridge, MA 02140 443 USA 445 Phone: +1 617 245 1457 446 Email: john-ietf@jck.com