idnits 2.17.1 draft-rsalz-2028bis-02.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (4 October 2021) is 934 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) ** Obsolete normative reference: RFC 2028 (Obsoleted by RFC 9281) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ??? R. Salz 3 Internet-Draft Akamai Technologies 4 Obsoletes: 2028 (if approved) 4 October 2021 5 Intended status: Best Current Practice 6 Expires: 7 April 2022 8 Entitities Involved in the IETF Standards Process 9 draft-rsalz-2028bis-02 11 Abstract 13 This document describes the individuals and organizations involved in 14 the IETF standards process as described in IETF BCP 9. It includes 15 brief descriptions of the entities involved, and the role they play 16 in the standards process. This document obsoletes RFC 2028. 18 Discussion Venues 20 This note is to be removed before publishing as an RFC. 22 Discussion of this document takes place on the GENDISPATCH mailing 23 list (gendispatch@ietf.org)], which is archived at 24 https://mailarchive.ietf.org/arch/browse/gendispatch/. 26 Source for this draft and an issue tracker can be found at 27 https://github.com/richsalz/draft-ietf-rfc2028bis. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at https://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on 7 April 2022. 46 Copyright Notice 48 Copyright (c) 2021 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 53 license-info) in effect on the date of publication of this document. 54 Please review these documents carefully, as they describe your rights 55 and restrictions with respect to this document. Code Components 56 extracted from this document must include Simplified BSD License text 57 as described in Section 4.e of the Trust Legal Provisions and are 58 provided without warranty as described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 3. Key Individuals in the Process . . . . . . . . . . . . . . . 3 65 3.1. The Document Editor or Author . . . . . . . . . . . . . . 3 66 3.2. The Working Group Chair . . . . . . . . . . . . . . . . . 4 67 3.3. The Area Director . . . . . . . . . . . . . . . . . . . . 4 68 3.4. The Request for Comments Editor . . . . . . . . . . . . . 4 69 4. Key Organizations in the Process . . . . . . . . . . . . . . 4 70 4.1. Internet Engineering Task Force (IETF) . . . . . . . . . 4 71 4.2. Working Groups . . . . . . . . . . . . . . . . . . . . . 4 72 4.3. Internet Engineering Steering Group (IESG) . . . . . . . 6 73 4.4. Internet Architecture Board (IAB) . . . . . . . . . . . . 6 74 4.5. Internet Assigned Numbers Authority (IANA) . . . . . . . 6 75 4.6. Internet Research Task Force (IRTF) . . . . . . . . . . . 7 76 4.7. The IETF Trust . . . . . . . . . . . . . . . . . . . . . 7 77 4.8. IETF Administration LLC (IETF LLC) . . . . . . . . . . . 8 78 4.9. IETF Secretariat . . . . . . . . . . . . . . . . . . . . 8 79 4.10. Internet Society . . . . . . . . . . . . . . . . . . . . 8 80 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 81 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 82 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 83 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 84 8.1. Normative References . . . . . . . . . . . . . . . . . . 9 85 8.2. Informative References . . . . . . . . . . . . . . . . . 11 86 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12 88 1. Introduction 90 The process used by the IETF community for the standardization of 91 protocols and procedures is described in [IETFPROCS]. That document 92 defines the stages in the standardization process, the requirements 93 for moving a document between stages, and the types of documents used 94 during this process. This document identifies some of the key 95 individual and organizations and the roles they play in that process. 97 2. Terminology 99 In general, this document refers to individual roles as individuals, 100 such as "a Document Editor." In reality, many roles are filled by 101 more than one person at the same time. For clarity, this document 102 does not use phrases like "Chair (or co-chair)," unless strictly 103 necessary to do so. 105 3. Key Individuals in the Process 107 This section describes the individual roles involved in the process. 108 It attempts to list the roles in the order in which they are involved 109 in the process, but no meaning is otherwise attached. 111 3.1. The Document Editor or Author 113 Most Working Groups focus their efforts on one or more documents that 114 capture the results of the group's work. A Working Group generally 115 designates a person to serve as the Editor for a particular document. 116 The Document Editor is responsible for ensuring that the contents of 117 the document accurately reflect the decisions that have been made by 118 the Working Group. 120 When a document is composed and edited mainly by an individual, they 121 may be referred to as the Document Author. The distinction is not 122 significant. This document will use the term Document Editor. 124 When a Document Editor is a Chair of the same Working Group, a co- 125 chair should manage the process around the document. If a co-chair 126 is not available, the process must be monitored carefully to ensure 127 that the resulting documents accurately reflect the consensus of the 128 Working Group and that all processes are followed. This can be the 129 collective obligation of all parties involved in the document. 131 3.2. The Working Group Chair 133 Each Working Group is headed by a chair with the responsibility for 134 directing the group's activities, presiding over the group's 135 meetings, and ensuring that the commitments of the group with respect 136 to its role in the Internet standards process are met. In 137 particular, the WG chair is the formal point of contact between the 138 WG and the IESG, via the Area Director of the area to which the WG is 139 assigned. 141 The details on the selection and responsibilites of a Working Group 142 chair can be found in [WGPROCS]. 144 3.3. The Area Director 146 The Area Director assigned as the "Reponsible Area Director" for the 147 Working Group will review the document after the Working Group has 148 approved its last call, and when satisfied will request it to be put 149 on the IESG agenda. 151 3.4. The Request for Comments Editor 153 The RFC publication series [IETFPROCS] is managed by an Editor 154 responsible both for the mechanics of RFC publication and for 155 upholding the technical and editorial standards of the RFC series. 157 4. Key Organizations in the Process 159 The following organizations and organizational roles are involved in 160 the Internet standards process. 162 4.1. Internet Engineering Task Force (IETF) 164 The IETF is an open international community of network designers, 165 operators, vendors, researchers, and other interested parties who are 166 concerned with the evolution of the Internet architecture and the 167 smooth operation of the Internet. It is the principal body engaged 168 in the development of new Internet Standard specifications. 170 4.2. Working Groups 172 The technical work of the IETF is done in its Working Groups, which 173 are organized by topics into several Areas 174 (https://www.ietf.org/topics/areas/), each one under the coordination 175 of the Area Director. Working Groups typically have a narrow focus 176 and a lifetime bounded by completion of specific tasks as defined in 177 their charter and milestones. 179 For all purposes relevant to the Internet Standards development 180 process, membership in the IETF and its Working Groups is defined to 181 be established solely and entirely by individuals who participate in 182 IETF and Working Group activities. These individuals do not formally 183 represent their organizations, if any, although affiliations are 184 often used for identification. 186 Anyone with the time and interest to do so is entitled and urged to 187 participate actively in one or more Working Groups and to attend IETF 188 meetings which are usually held three times a year [MEETINGS]. 189 Active Working Group participation is possible without attending any 190 in-person meeting. 192 Participants in the IETF and its Working Groups must disclose any 193 relevant current or pending intellectual property rights that are 194 reasonably and personally known to the participant if they 195 participate in discussions about a specific technology. The full 196 intellectual property policy is defined in [IPRRIGHTS1] and 197 [IPRRIGHTS2]. 199 New Working Groups are established by the IESG and almost always have 200 a specific and explicit charter. The charter can be modified as the 201 Working Group progresses. The guidelines and procedures for the 202 formation and operation of Working Groups are described in detail in 203 [WGPROCS]. 205 A Working Group is managed by a Working Group chair, as described at 206 Section 3.2. Documents produced by the group will have an Editor, as 207 described at Section 3.1. Further details of Working Group operation 208 can also be found in [WGPROCS]. 210 Working Groups ideally display a spirit of cooperation as well as a 211 high degree of technical maturity; IETF participants recognize that 212 the greatest benefit for all members of the Internet community 213 results from cooperative development of technically superior 214 protocols and services. 216 4.3. Internet Engineering Steering Group (IESG) 218 The IESG is responsible for the management of the IETF technical 219 activities. It administers the Internet Standards process according 220 to the rules and procedures defined in [IETFPROCS]. The IESG is 221 responsible for the actions associated with the progression of 222 technical specification along the "standards track" including the 223 initial approval of new Working Groups and the final approval of 224 specifications as Internet Standards. The IESG is composed of the 225 IETF Area Directors and the IETF Chair, who also chairs the IESG and 226 is the Area Director for the General Area. The IAB Chair is an ex- 227 officio member of the IESG. 229 All members of the IESG are nominated by a nominations committee 230 (colloquially, NomCom), and are confirmed by the IAB. See [NOMCOM] 231 for a detailed description of the NomCom procedures. Other matters 232 concerning its organization and operation, are described in the IESG 233 charter [IESG]. 235 4.4. Internet Architecture Board (IAB) 237 The IAB provides oversight of the architecture of the Internet and 238 its protocols. The IAB must approve all IESG candidates put forward 239 by the NomCom. 241 The IAB provides oversight of the process used to create Internet 242 Standards and serves as an appeal board for complaints of improper 243 execution of the standards process [IETFPROCS]. In general, it acts 244 as source of advice to the IETF and other entities mentioned here 245 about technical, architectural, procedural, and policy matters 246 pertaining to the Internet and its enabling technologies. 248 The members of the IAB are nominated by NomCom, and are confirmed by 249 the Internet Society Board. The IETF Chair is also a member of the 250 IAB, and the IRTF Chair is an ex-officio member. See [NOMCOM] for a 251 detailed description of the NomCom procedures. Other matters 252 concerning its organization and operation, are described in the IAB 253 charter [IAB]. 255 4.5. Internet Assigned Numbers Authority (IANA) 257 Many protocol specifications include parameters that must be uniquely 258 assigned. Examples of this include port numbers, option identifiers 259 within a protocol, and so on. The Internet Assigned Numbers 260 Authority (IANA) is responsible for assigning the values of these 261 protocol parameters for the Internet. These registries used to be 262 published as RFCs entitled "Assigned Numbers," but are now maintained 263 online (https://www.iana.org/protocols). Assignments are coordinated 264 by writing an "IANA Considerations" section in a draft, as documented 265 in [IANADOCS]. The IETF's relationship with IANA is defined by 266 formal agreements, including [IANAMOU]. 268 IANA also is responsible for operating and maintaining several 269 aspects of DNS (https://www.iana.org/domains) and coordination of IP 270 address assignment (https://www.iana.org/numbers). 272 4.6. Internet Research Task Force (IRTF) 274 The IRTF focuses on longer-term research issues related to the 275 Internet while the parallel organization, the Internet Engineering 276 Task Force (IETF), focuses on the shorter term issues of engineering 277 and standards making. 279 The products of IRTF research groups are typically research results 280 that are published in scholarly conferences and journals. Research 281 groups also sometimes develop experimental protocols or technologies, 282 some of which may be suitable for possible standardisation in IETF. 283 Similarly, IETF working groups sometimes ask research groups for 284 advice or other input. Contributions from research groups, however, 285 carry no more weight than other community input, and go through the 286 same standards setting process as any other proposal. 288 The IRTF is managed by the IRTF Chair in consultation with the 289 Internet Research Steering Group (IRSG). The IRSG membership 290 includes the IRTF Chair, the chairs of the various Research Group and 291 possibly other individuals ("members at large") from the community. 292 Details of the organization and operation of the IRTF, the ISRG, and 293 its Research Groups may be found in [IRTF], [IABIRTF], [IRTFPRIMER], 294 and [IRTFCHAIR]. 296 4.7. The IETF Trust 298 The IETF Trust is the legal owner of a number of intellectual 299 properties for the IETF and others (such as IANA). This includes the 300 IETF trademarks, the copyright licenses for IETF contributions 301 including Internet Drafts. The principles for the copyright licenses 302 are described in [IPRRIGHTS1] and [COPYRIGHT], and the licenses 303 themselves are online in the Trust Legal Provisions 304 (https://trustee.ietf.org/documents/trust-legal-provisions/). 306 The trustees that govern the Trust are selected from the IETF 307 community as described in [TRUSTEES]. 309 4.8. IETF Administration LLC (IETF LLC) 311 The IETF Administration Limited Liability Corporation (colloquially, 312 the LLC) provides the corporate legal home for the IETF, the IAB, and 313 the IRTF. 315 The IETF LLC is responsible for supporting the ongoing operations of 316 the IETF, managing its finances and budget, and raising money. It 317 regularly reports to the community. The LLC is the legal entity who 318 signs contracts, including the Secretariat, meeting hotels, tools 319 development contractors, and so on. The LLC also responds to legal 320 requests; these are often subpoenas in patent suits. 322 Selection of the LLC Board of Directors is defined in [NOMCOM]. 324 The IETF Executive Director handles the daily tasks and management, 325 and is overseen by the LLC Board of Directors. 327 [ISOCIETF], Section 6 describes the legal relationship between the 328 LLC and the Internet Society. 330 4.9. IETF Secretariat 332 The administrative functions necessary to support the activities of 333 the IETF are performed by a Secretariat hired by the IETF LLC. The 334 Secretariat handles much of the logistics of running the in-person 335 meetings, and is responsible for maintaining the formal public record 336 of the Internet standards process [IETFPROCS]. 338 4.10. Internet Society 340 Internet standardization is an organized activity of the Internet 341 Society, with the Board of Trustees being responsible for ratifying 342 the procedures and rules of the Internet standards process 343 [ISOCIETF]. 345 The Internet Society also plays an important role in the standards 346 process. It appoints the NomCom Chair, confirms IAB candidates, and 347 acts as the last resort in the appeals process. 349 The way in which the members of the Internet Society Board of 350 Trustees are selected, and other matters concerning the operation of 351 the Internet Society, are described in their By-Laws [ISOC]. 353 5. Security Considerations 355 This document introduces no new security considerations. 357 6. IANA Considerations 359 This document has no IANA actions. 361 7. Acknowledgements 363 The author of this document would like to thank the IETF participants 364 at the time [RFC2028] was written; in particular, those involved with 365 the POISED effort and the authors of that document, Richard Hovey and 366 Scott Bradner. 368 8. References 370 8.1. Normative References 372 [IAB] Internet Architecture Board and B. Carpenter, Ed., 373 "Charter of the Internet Architecture Board (IAB)", 374 BCP 39, RFC 2850, May 2000. 376 378 [IANADOCS] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 379 Writing an IANA Considerations Section in RFCs", BCP 26, 380 RFC 8126, June 2017. 382 384 [IETFPROCS] 385 Bradner, S., "The Internet Standards Process -- Revision 386 3", BCP 9, RFC 2026, October 1996. 388 Dusseault, L. and R. Sparks, "Guidance on Interoperation 389 and Implementation Reports for Advancement to Draft 390 Standard", BCP 9, RFC 5657, September 2009. 392 Housley, R., Crocker, D., and E. Burger, "Reducing the 393 Standards Track to Two Maturity Levels", BCP 9, RFC 6410, 394 October 2011. 396 Resnick, P., "Retirement of the "Internet Official 397 Protocol Standards" Summary Document", BCP 9, RFC 7100, 398 December 2013. 400 Kolkman, O., Bradner, S., and S. Turner, "Characterization 401 of Proposed Standards", BCP 9, RFC 7127, January 2014. 403 Dawkins, S., "Increasing the Number of Area Directors in 404 an IETF Area", BCP 9, RFC 7475, March 2015. 406 Halpern, J., Ed. and E. Rescorla, Ed., "IETF Stream 407 Documents Require IETF Rough Consensus", BCP 9, RFC 8789, 408 June 2020. 410 412 [IPRRIGHTS1] 413 Bradner, S., Ed. and J. Contreras, Ed., "Rights 414 Contributors Provide to the IETF Trust", BCP 78, RFC 5378, 415 November 2008. 417 419 [IPRRIGHTS2] 420 Bradner, S. and J. Contreras, "Intellectual Property 421 Rights in IETF Technology", BCP 79, RFC 8179, May 2017. 423 425 [IRTF] Weinrib, A. and J. Postel, "IRTF Research Group Guidelines 426 and Procedures", BCP 8, RFC 2014, DOI 10.17487/RFC2014, 427 October 1996, . 429 [MEETINGS] Krishnan, S., "High-Level Guidance for the Meeting Policy 430 of the IETF", BCP 226, RFC 8719, DOI 10.17487/RFC8719, 431 February 2020, . 433 [NOMCOM] Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood, 434 Ed., "IAB, IESG, IETF Trust, and IETF LLC Selection, 435 Confirmation, and Recall Process: Operation of the IETF 436 Nominating and Recall Committees", BCP 10, RFC 8713, 437 February 2020. 439 Leiba, B., "Eligibility for the 2020-2021 Nominating 440 Committee", BCP 10, RFC 8788, May 2020. 442 444 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 445 the IETF Standards Process", BCP 11, RFC 2028, 446 DOI 10.17487/RFC2028, October 1996, 447 . 449 [WGPROCS] Bradner, S., "IETF Working Group Guidelines and 450 Procedures", BCP 25, RFC 2418, September 1998. 452 Wasserman, M., "Updates to RFC 2418 Regarding the 453 Management of IETF Mailing Lists", BCP 25, RFC 3934, 454 October 2004. 456 Resnick, P. and A. Farrel, "IETF Anti-Harassment 457 Procedures", BCP 25, RFC 7776, March 2016. 459 Resnick, P. and A. Farrel, "Update to the IETF Anti- 460 Harassment Procedures for the Replacement of the IETF 461 Administrative Oversight Committee (IAOC) with the IETF 462 Administration LLC", BCP 25, RFC 8716, February 2020. 464 466 8.2. Informative References 468 [COPYRIGHT] 469 Halpern, J., Ed., "Advice to the Trustees of the IETF 470 Trust on Rights to Be Granted in IETF Documents", 471 RFC 8721, DOI 10.17487/RFC8721, February 2020, 472 . 474 [IABIRTF] Floyd, S., Ed., Paxson, V., Ed., Falk, A., Ed., and IAB, 475 "IAB Thoughts on the Role of the Internet Research Task 476 Force (IRTF)", RFC 4440, DOI 10.17487/RFC4440, March 2006, 477 . 479 [IANAMOU] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of 480 Understanding Concerning the Technical Work of the 481 Internet Assigned Numbers Authority", RFC 2860, 482 DOI 10.17487/RFC2860, June 2000, 483 . 485 [IESG] Alvestrand, H., "An IESG charter", RFC 3710, 486 DOI 10.17487/RFC3710, February 2004, 487 . 489 [IRTFCHAIR] 490 Eggert, L., "The Role of the IRTF Chair", RFC 7827, 491 DOI 10.17487/RFC7827, March 2016, 492 . 494 [IRTFPRIMER] 495 Dawkins, S., Ed., "An IRTF Primer for IETF Participants", 496 RFC 7418, DOI 10.17487/RFC7418, December 2014, 497 . 499 [ISOC] "Amended and restated By-Laws of the Internet Society", 500 March 2021, . 503 [ISOCIETF] Camarillo, G. and J. Livingood, "The IETF-ISOC 504 Relationship", RFC 8712, DOI 10.17487/RFC8712, February 505 2020, . 507 [TRUSTEES] Arkko, J., "IETF Administrative Support Activity 2.0: 508 Update to the Process for Selection of Trustees for the 509 IETF Trust", RFC 8715, DOI 10.17487/RFC8715, February 510 2020, . 512 Author's Address 514 Rich Salz 515 Akamai Technologies 517 Email: rsalz@akamai.com