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