idnits 2.17.1 draft-ietf-iasa2-consolidated-upd-00.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 RFC3979, but the abstract doesn't seem to mention this, which it should. -- 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 obsoletes RFC4879, 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 RFC5377, 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 (November 15, 2018) is 1989 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 123, but not defined ** Obsolete undefined reference: RFC 4071 (Obsoleted by RFC 8711) == Unused Reference: 'RFC-StructS3' is defined on line 307, but no explicit reference was found in the text == Unused Reference: 'RFC3716' is defined on line 364, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'LLC-Agreement' ** Downref: Normative reference to an Informational draft: draft-ietf-iasa2-struct (ref. 'RFC-Struct') -- Duplicate reference: draft-ietf-iasa2-struct, mentioned in 'RFC-StructS3', was also mentioned in 'RFC-Struct'. ** Downref: Normative reference to an Informational draft: draft-ietf-iasa2-struct (ref. 'RFC-StructS3') ** 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 normative reference: RFC 7500 (Obsoleted by RFC 8720) -- 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: 11 errors (**), 0 flaws (~~), 4 warnings (==), 16 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IASA2 J. Klensin, Ed. 3 Internet-Draft November 15, 2018 4 Obsoletes: 3716, 3929, 3979, 4633, 4879, 5 8179 (if approved) 6 Updates: 2028, 2418, 3005, 3710, 5377, 7 6702, 7500 (if approved) 8 Intended status: Best Current Practice 9 Expires: May 19, 2019 11 Consolidated IASA2-Related Document Updates 12 draft-ietf-iasa2-consolidated-upd-00 14 Abstract 16 In 2018, the IETF began the transition to a new administrative 17 structure, and updated its IETF Administrative Support Activity 18 (IASA) to a new "IASA 2.0" structure. In addition to more 19 substantive changes that are described in other documents, the 20 transition to the 2018 IETF Administrative Support structure changes 21 several position titles and organizational relationships that are 22 referenced in other documents. Rather than reissue those 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 May 19, 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 . . . . . . . 5 68 6. Deprecated Documents . . . . . . . . . . . . . . . . . . . . 5 69 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 70 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . 8 76 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 78 1. Introduction 80 In 2018, the IETF began the transition to a new administrative 81 structure, and updated its IETF Administrative Support Activity 82 (IASA) to a new "IASA 2.0" structure [RFC-Struct]. Key IASA 2.0 83 changes have been specified in a series of documents, including 84 changes to the IETF Trust [RFC-trust-update], the rationale for it 85 [RFC-trust-rationale], a new defining document for the IETF 86 Administration LLC [LLC-Agreement] (informally called the "IETF LLC" 87 or just "the LLC" in places in this document and elsewhere) and 88 adjustments to the procedures for nominations and selections for 89 relevant positions [RFC-7437bis]. 91 In addition to more substantive changes that are described in those 92 and other documents, the IASA 2.0 structure changes several position 93 titles and organizational relationships that are referenced in other 94 documents. Rather than reissue those documents individually, this 95 document provides a unified update to them. 97 This document updates RFCs 2028, 2418, 3005, 3710, 5377, 6702, and 98 7500 (citations in context below) to make those terminology and 99 related changes. For clarity, it also obsoletes RFCs 3716, 3929, 100 3979, 4633, 4879, and 8179 which were Experimental or Informational 101 documents that are no longer relevant (see Section 6). The sections 102 that follow identify the details of the relevant documents and the 103 required changes. 105 [[CREF1: Note in Draft: This document lists changes that the WG may 106 choose to process as standalone replacement documents instead. The 107 relevant sections are provided to speed things along should it decide 108 to not do that.]] 110 2. Remove Text About the Connection Between the IAOC and IETF Trust 112 Some documents that discuss the IETF Trust or its relationship to the 113 community describe it, or the Trustees, in relation to the IAOC. 114 That connection must be eliminated to reflect the new IASA 2.0 115 structure. 117 This document applies that change to the following: 119 o RFC 5377 [RFC5377], Advice to the Trustees of the IETF Trust on 120 Rights to Be Granted in IETF Documents. These changes require 121 dropping "made up of the members of the IAOC [RFC4371]" after 122 "board of trustees" in the first paragraph of Section 1 and "which 123 is made up of the members of the IAOC, as described in [RFC4071] 124 and [RFC4371]" in the first paragraph of Section 3. 125 [[CREF2: RFC Editor please note that the bracketed strings above 126 are quoted text, not references. ]] 128 3. Replacement of IAOC with IETF Administration LLC 130 All mentions of the IETF Administrative Oversight Committee (IAOC) 131 that are not removed by the prior section, shall be updated and 132 replaced by the IETF Administration LLC (IETF-LLC). This is 133 necessary because the IAOC is phased out under the IASA 2.0 134 structure. 136 This document applies that change to the following: 138 o RFC 4844 [RFC4844], the RFC Series and RFC Editor Sections 3.3, 139 3.4, and 4. 141 o RFC 7500 [RFC7500] Principles for Operation of Internet Assigned 142 Numbers Authority (IANA) Registries, Section 3.4. This means that 143 the IETF LLC, the body responsible for IETF administrative and 144 financial matters, maintains an SLA with the current registry 145 operator, the Internet Corporation for Assigned Names and Numbers 146 (ICANN). It also means that both the Internet Architecture Board 147 (IAB) and the IETF LLC are accountable to the larger Internet 148 community for the IANA registries. 150 4. Where Appropriate, Replacement of the IETF Executive Director 151 position with the Managing Director, IETF Secretariat 153 Under the IASA 2.0 structure, most of the responsibilities of the 154 former position of IETF Executive Director been assigned to a new 155 position (or at least title) of Managing Director of the IETF 156 Secretariat. An "Executive Director" title is now associated with 157 different, and largely new, responsibilities as an Officer of the 158 IETF Administration LLC. These changes are described in the 159 description of the new structural arrangements [RFC-Struct]. 161 [[CREF3: Editorial comment/rant (JcK 20181114): Or at least they had 162 better be clearly described there because, if they are not, this 163 document is the wrong place to try to fix it. I've done the best I 164 could to combine my view of what this should say (which does not 165 necessarily align with WG discussions) and Jason's (which presumably 166 does, but had another issue or two). Basically, from the standpoint 167 of a clear understanding of the new roles and titles, taking the old 168 roles of "IETF Executive Director" and "IETF Administrative Director" 169 and renaming the Secretariat management part of the former role to 170 "Managing Director, IETF Secretariat" would have been a little 171 confusing because the old "IETF Executive Director" position had 172 functions that were not inherently limited to the Secretariat 173 function as the IETF has understood it. But then taking some of the 174 IAD functions and calling them "Executive Director" (without "IETF", 175 but the term with "IETF" is still present in older documents that the 176 WG has concluded it doesn't need to update and in some more recent 177 sloppy usage) while distributing other IAD functions to the 178 Secretariat is a recipe for complete confusion... and I've seen 179 messages in which several people who have been active in the WG 180 appear to be confused. I accept Alissa's judgment that it is too 181 late to change this, or at least the association of the "Executive 182 Director" title with that LLC function, but suggest we need to be 183 _very_ careful -- much more careful than we have apparently been so 184 far -- about good-quality explanations and absolute consistency about 185 terminology. ]] 187 This document applies that change to the following: 189 o RFC 2028, The Organizations Involved in the IETF Standards Process 190 [RFC2028], Section 3.3. 191 [[CREF4: Editorial note (JcK 20181115) Jason suggested somewhat 192 different text, specifically "This means that the administrative 193 functions necessary to support the activities of the IETF are 194 performed by a Secretariat, led by the Managing Director, IETF 195 Secretariat, and consisting of his or her staff in the IETF 196 Secretariat." I don't think "This" (the change) means any such 197 thing because 2028 fairly clearly establishes the administrative 198 function role of the Secretariat and its staff. All this change 199 does is what is described in the first paragraph of this section, 200 i.e., switch titles, so the additional attempted explanation is 201 unnecessary and likely to be confusing. A similar change was 202 proposed for the description of the RFC 2418 change below. The WG 203 should decide what it wants.]] 205 o RFC 2418, IETF Working Group Guidelines and Procedures [RFC2418] 207 o RFC 3710, An IESG Charter, Section 2[RFC3710]. 209 o RFC 6702, Promoting Compliance with Intellectual Property Rights 210 (IPR) Disclosure Rules, Section 5 [RFC6702]. 212 [[CREF5: Note in Draft: Bob Hinden's note of November 10, 2018 11:37 213 +0900 indicates that RFC4844 should continue to reference the IETF 214 Executive Director.]] 216 5. Remove the IETF Executive Director as an Option 218 In a few cases, it is no longer appropriate for either the Managing 219 Director, IETF Secretariat (former IETF Executive Director position) 220 or the new IETF Executive Director (for the LLC) to perform a 221 particular historical function. The relevant documents are updated 222 to remove the IETF Executive Director from the list of people with 223 specific responsibilities or authority. Those documents will not be 224 updated to use "Managing Director, IETF Secretariat" but, instead, 225 the mention of the position will simply be dropped. 227 This document applies that change to the following: 229 o RFC 3005, IETF Discussion List Charter [RFC3005], section titled 230 "Charter for the IETF Discussion List". This document is modified 231 to remove the authorization for the IETF Executive Director to 232 restrict people from posting, etc. 234 6. Deprecated Documents 236 The IASA2 Working Group has also identified several RFCs that no 237 longer apply as a result of the change to the new IASA 2.0 structure. 238 The result is that several informational, experimental, or other RFCs 239 can be deprecated. 241 This document deprecates the following: 243 o RFC 3929 [RFC3929], which touches on aspects of the administration 244 of the IETF, such as mentioning the IETF Executive Director. It 245 dates to 2004 and is experimental. 247 o RFC 3979 [RFC3979], that is updated by [RFC8179], which corrects 248 mentions of the IETF Executive Director to the IETF Secretariat. 250 o RFC 4633 [RFC4633], which is an experimental document that refers 251 to IETF Executive Director. It describes a 2006 experiment that 252 ran for 18 months. 254 o RFC 4879 [RFC4879], that is updated by [RFC8179], which corrects 255 mentions of the IETF Executive Director to the IETF Secretariat. 257 It is also recommended that the above documents be reclassified to 258 Historic to further reduce the risk of any confusion. 260 7. Acknowledgements 262 ..to be supplied after version 00 264 8. Contributors 266 Jason Livingood did the hard work of identifying the documents that 267 required updating and supplied considerable text used in this 268 document. 270 9. IANA Considerations 272 [[CREF6: RFC Editor: Please remove this section before publication.]] 274 This memo includes no requests to or actions for IANA. 276 10. Security Considerations 278 The changes specified in this document are matters of terminology and 279 organizational structure derived from documents it references. It 280 should have no effect on Internet security. 282 11. References 284 11.1. Normative References 286 [LLC-Agreement] 287 IETF Administration LLC, "Limited Liability Company 288 Agreement of IETF Administration LLC", August 2018, 289 . 292 [RFC-7437bis] 293 Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood, 294 Ed., "IAB, IESG, and IETF LLC Selection, Confirmation, and 295 Recall Process: Operation of the IETF Nominating and 296 Recall Committees", 2018, 297 . 300 [RFC-Struct] 301 Haberman, B., Hall, J., and J. Livingood, Ed., "Record of 302 Proposed Structure of the IETF Administrative Support 303 Activity (IASA), Version 2.0", 2018, 304 . 307 [RFC-StructS3] 308 Haberman, B., Hall, J., and J. Livingood, Ed., "Record of 309 Proposed Structure of the IETF Administrative Support 310 Activity (IASA), Version 2.0, Sectiion 3", 2018, 311 . 314 [RFC-trust-rationale] 315 Arkko, J., "Discussion of the IASA 2.0 Changes as They 316 Relate to the IETF Trust", 2018, 317 . 320 [RFC-trust-update] 321 Arkko, J. and T. Hardie, "Update to the Process for 322 Selection of Trustees for the IETF Trust", 2018, 323 . 326 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 327 the IETF Standards Process", BCP 11, RFC 2028, 328 DOI 10.17487/RFC2028, October 1996, 329 . 331 [RFC2418] Bradner, S., "IETF Working Group Guidelines and 332 Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418, 333 September 1998, . 335 [RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, 336 RFC 3005, DOI 10.17487/RFC3005, November 2000, 337 . 339 [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, 340 DOI 10.17487/RFC3710, February 2004, 341 . 343 [RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC 344 Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844, 345 July 2007, . 347 [RFC5377] Halpern, J., Ed., "Advice to the Trustees of the IETF 348 Trust on Rights to Be Granted in IETF Documents", 349 RFC 5377, DOI 10.17487/RFC5377, November 2008, 350 . 352 [RFC6702] Polk, T. and P. Saint-Andre, "Promoting Compliance with 353 Intellectual Property Rights (IPR) Disclosure Rules", 354 RFC 6702, DOI 10.17487/RFC6702, August 2012, 355 . 357 [RFC7500] Housley, R., Ed. and O. Kolkman, Ed., "Principles for 358 Operation of Internet Assigned Numbers Authority (IANA) 359 Registries", RFC 7500, DOI 10.17487/RFC7500, April 2015, 360 . 362 11.2. Informative References 364 [RFC3716] IAB Advisory Committee, "The IETF in the Large: 365 Administration and Execution", RFC 3716, 366 DOI 10.17487/RFC3716, March 2004, 367 . 369 [RFC3929] Hardie, T., "Alternative Decision Making Processes for 370 Consensus-Blocked Decisions in the IETF", RFC 3929, 371 DOI 10.17487/RFC3929, October 2004, 372 . 374 [RFC3979] Bradner, S., Ed., "Intellectual Property Rights in IETF 375 Technology", RFC 3979, DOI 10.17487/RFC3979, March 2005, 376 . 378 [RFC4633] Hartman, S., "Experiment in Long-Term Suspensions From 379 Internet Engineering Task Force (IETF) Mailing Lists", 380 RFC 4633, DOI 10.17487/RFC4633, August 2006, 381 . 383 [RFC4879] Narten, T., "Clarification of the Third Party Disclosure 384 Procedure in RFC 3979", RFC 4879, DOI 10.17487/RFC4879, 385 April 2007, . 387 [RFC8179] Bradner, S. and J. Contreras, "Intellectual Property 388 Rights in IETF Technology", BCP 79, RFC 8179, 389 DOI 10.17487/RFC8179, May 2017, 390 . 392 Author's Address 394 John C Klensin (editor) 395 1770 Massachusetts Ave, Ste 322 396 Cambridge, MA 02140 397 USA 399 Phone: +1 617 245 1457 400 Email: john-ietf@jck.com