idnits 2.17.1 draft-carpenter-procdoc-roadmap-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 403. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 414. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 421. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 427. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. 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 RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (August 2, 2006) is 6449 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2028 (Obsoleted by RFC 9281) ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 3005 (Obsoleted by RFC 9245) ** Obsolete normative reference: RFC 3184 (Obsoleted by RFC 7154) ** Obsolete normative reference: RFC 3777 (Obsoleted by RFC 7437) ** Obsolete normative reference: RFC 3932 (Obsoleted by RFC 5742) ** Obsolete normative reference: RFC 3978 (Obsoleted by RFC 5378) ** Obsolete normative reference: RFC 3979 (Obsoleted by RFC 8179) ** Obsolete normative reference: RFC 4071 (Obsoleted by RFC 8711) ** Obsolete normative reference: RFC 4333 (Obsoleted by RFC 8711) ** Obsolete normative reference: RFC 4371 (Obsoleted by RFC 8714) -- Obsolete informational reference (is this intentional?): RFC 1264 (Obsoleted by RFC 4794) -- Obsolete informational reference (is this intentional?): RFC 2031 (Obsoleted by RFC 8712) -- Obsolete informational reference (is this intentional?): RFC 2223 (Obsoleted by RFC 7322) -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) -- Obsolete informational reference (is this intentional?): RFC 3160 (Obsoleted by RFC 4677) Summary: 14 errors (**), 0 flaws (~~), 1 warning (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Carpenter (ed) 3 Internet-Draft IBM 4 Intended status: Informational August 2, 2006 5 Expires: February 3, 2007 7 The IETF Process: an Informal Guide 8 draft-carpenter-procdoc-roadmap-05 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on February 3, 2007. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 39 Abstract 41 This document is an informal guide to various IETF process documents, 42 intended both to assist IETF participants and to support possible 43 future discussions about process reform. 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 2. The guide . . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2.1. General description of workflow in the IETF . . . . . . . 3 50 2.2. Definition of standards track and related document 51 types . . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2.3. Intellectual Property . . . . . . . . . . . . . . . . . . 4 53 2.4. Review and approval process . . . . . . . . . . . . . . . 4 54 2.5. Bodies involved in the process . . . . . . . . . . . . . . 4 55 2.6. Conduct of participants . . . . . . . . . . . . . . . . . 4 56 2.7. Publication process . . . . . . . . . . . . . . . . . . . 5 57 2.8. Parameter registration process . . . . . . . . . . . . . . 5 58 2.9. Administration . . . . . . . . . . . . . . . . . . . . . . 5 59 2.10. Modifying the process . . . . . . . . . . . . . . . . . . 5 60 3. Security Considerations . . . . . . . . . . . . . . . . . . . 5 61 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 62 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 63 6. Change log [RFC Editor: please remove this section] . . . . . 6 64 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 65 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 66 7.2. Informative References . . . . . . . . . . . . . . . . . . 8 67 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9 68 Intellectual Property and Copyright Statements . . . . . . . . . . 10 70 1. Introduction 72 BCP 9 [RFC2026] has been the basis for the IETF standards process for 73 many years. However, many other process documents exist, some of 74 which are partial updates to BCP 9. This situation is confusing and 75 would ideally be resolved by a clear set of interlocking documents. 76 The present document suggests a structured way of looking at the 77 existing documents. 79 It is difficult to linearise a complicated and interlocked process. 80 This document presents a guide in one particular order, but that is 81 not intended to imply priority or importance, and it cannot capture 82 all interactions between components. 84 Formally, IETF processes are described in Best Current Practices 85 (BCPs) published as RFCs. Most of the cited RFCs are BCPs. RFC 86 numbers have been used rather than BCP numbers, for convenient 87 lookup. To avoid any accidental ambiguity, this guide does not 88 attempt to paraphrase or summarize their contents; the reader should 89 consult the original RFCs. 91 2. The guide 93 2.1. General description of workflow in the IETF 95 Suach a document does not exist, although the Tao ([RFC3160], to be 96 replaced by [I-D.hoffman-taobis]) offers most of it informally: How 97 ideas for new work enter the IETF, reach a BOF, enter IAB or IRTF 98 discussion, and possibly become material for a new or existing WG. 99 How WGs are chartered - the Area Director's role. How specific 100 proposals become drafts and flow through the development, review and 101 approval process. 103 2.2. Definition of standards track and related document types 105 This material is currently embedded in [RFC2026]. Additional 106 requirements for routing protocols are currently defined in 107 [RFC1264]. The newtrk WG was chartered to revise the standards track 108 - multiple proposals have been floated, but no conclusions have been 109 reached. 110 o Specifications 111 This material is currently embedded in [RFC2026], covering 112 standards track, BCP and Experimental documents. The STD 113 (standard) designation is documented in [RFC1311]. A variance 114 procedure for down-level normative references is in [RFC3967]. A 115 specific process for advancing MIB documents is in [RFC2438]. 117 o Information 118 This material is currently embedded in [RFC2026], covering 119 Informational and Historic documents. A distinction between 120 obsolete and deprecated documents is not currently made in the 121 IETF. 123 2.3. Intellectual Property 124 o Rights in Contributions [RFC3978] 125 o Rights in Technology [RFC3979] (Guidelines, [RFC3669]) 126 o Trademarks [RFC3978] 127 o IETF Trust [RFC4371] 129 2.4. Review and approval process 131 This material is currently embedded in [RFC2026]. 132 o Criteria for review 133 Various review teams exist in different IETF Areas, with their own 134 technical criteria. For the General Area, see 135 http://www.alvestrand.no/ietf/gen/art/review-guidelines.html 136 o Criteria for approval 137 Material on current IESG practice can be found in 138 [I-D.iesg-discuss-criteria] 139 * Appeal process 140 This material is currently embedded in [RFC2026]. 142 2.5. Bodies involved in the process 144 Bodies involved [RFC2028]; Defining the IETF [RFC3233]; Mission 145 Statement [RFC3935]. 146 o WG procedures [RFC2418] 147 o IESG [RFC3710] 148 o IAB [RFC2850] 149 * Liaison management [RFC4052], [RFC4053], (guidance in 150 [I-D.iab-liaison-guidelines]) 151 o Nomcom [RFC3777] 152 o Relationship to ISOC [RFC2031], [RFC3677] 154 2.6. Conduct of participants 156 See [RFC3005], [RFC3184], [RFC3683], [RFC3934]; also discussed in 157 [RFC2418] and in the Tao ([RFC3160], to be replaced by 158 [I-D.hoffman-taobis]). 159 o Appeal process 160 This material is currently embedded in [RFC2026]. 162 2.7. Publication process 163 o Requirements 164 [I-D.mankin-pub-req] 165 o Format and mechanics for drafts 166 http://www.ietf.org/ietf/1id-guidelines.html 167 o Format and mechanics for archival publications 168 [RFC2223] is the published version today. The RFC Editor 169 currently refers to [I-D.rfc-editor-rfc2223bis]. Those writing 170 standards will find the following especially useful: [RFC2360], 171 [RFC2434], [RFC3552]. 172 o Direct submissions to RFC Editor [RFC3932] 174 2.8. Parameter registration process 175 o Requirements [RFC2860] 176 o Guidelines [RFC2434] 177 o Format and mechanics 178 Case by case at IANA web site. 180 2.9. Administration 182 See [RFC4071], [RFC4371], [RFC4333]. 184 2.10. Modifying the process 186 [RFC2026] defines how process BCPs are discussed and approved. A 187 general description of how the IETF modifies its own processes does 188 not exist, but probably should. An experimental procedure is 189 described in [RFC3933] (also see 190 http://www.ietf.org/IESG/content/experiments.html). 192 3. Security Considerations 194 This document has no security implications for the Internet. 196 4. IANA Considerations 198 This document requires no action by the IANA. However, it does 199 mention how IANA's registration functions are documented. 201 5. Acknowledgements 203 Useful comments on this document were made by: Harald Alvestrand, 204 Scott Bradner, Spencer Dawkins, Leslie Daigle, John Klensin, and 205 others. 207 This document was produced using the xml2rfc tool [RFC2629]. 209 6. Change log [RFC Editor: please remove this section] 211 draft-carpenter-procdoc-roadmap-05: Earlier drafts of this document 212 included references to drafts proposing changes to the standards 213 process. These have been removed to make this document a more stable 214 reference. It has been renamed from "roadmap" to "guide." Some 215 editorial rearrangements have been made. 2006-08-02 217 draft-carpenter-procdoc-roadmap-04: minor additions, tuned Abstract 218 and Introduction, 2006-02-20 220 draft-carpenter-procdoc-roadmap-03: minor additions, 2005-12-20 222 draft-carpenter-procdoc-roadmap-02: minor additions, 2005-10-11 224 draft-carpenter-procdoc-roadmap-01: minor additions, 2005-09-20 226 draft-carpenter-procdoc-roadmap-00: original version, 2005-08-22 228 7. References 230 7.1. Normative References 232 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 233 3", BCP 9, RFC 2026, October 1996. 235 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 236 the IETF Standards Process", BCP 11, RFC 2028, 237 October 1996. 239 [RFC2360] Scott, G., "Guide for Internet Standards Writers", BCP 22, 240 RFC 2360, June 1998. 242 [RFC2418] Bradner, S., "IETF Working Group Guidelines and 243 Procedures", BCP 25, RFC 2418, September 1998. 245 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 246 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 247 October 1998. 249 [RFC2438] O'Dell, M., Alvestrand, H., Wijnen, B., and S. Bradner, 250 "Advancement of MIB specifications on the IETF Standards 251 Track", BCP 27, RFC 2438, October 1998. 253 [RFC2850] Internet Architecture Board and B. Carpenter, "Charter of 254 the Internet Architecture Board (IAB)", BCP 39, RFC 2850, 255 May 2000. 257 [RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, 258 RFC 3005, November 2000. 260 [RFC3184] Harris, S., "IETF Guidelines for Conduct", BCP 54, 261 RFC 3184, October 2001. 263 [RFC3233] Hoffman, P. and S. Bradner, "Defining the IETF", BCP 58, 264 RFC 3233, February 2002. 266 [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC 267 Text on Security Considerations", BCP 72, RFC 3552, 268 July 2003. 270 [RFC3677] Daigle, L. and Internet Architecture Board, "IETF ISOC 271 Board of Trustee Appointment Procedures", BCP 77, 272 RFC 3677, December 2003. 274 [RFC3683] Rose, M., "A Practice for Revoking Posting Rights to IETF 275 mailing lists", BCP 83, RFC 3683, February 2004. 277 [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and 278 Recall Process: Operation of the Nominating and Recall 279 Committees", BCP 10, RFC 3777, June 2004. 281 [RFC3932] Alvestrand, H., "The IESG and RFC Editor Documents: 282 Procedures", BCP 92, RFC 3932, October 2004. 284 [RFC3933] Klensin, J. and S. Dawkins, "A Model for IETF Process 285 Experiments", BCP 93, RFC 3933, November 2004. 287 [RFC3934] Wasserman, M., "Updates to RFC 2418 Regarding the 288 Management of IETF Mailing Lists", BCP 94, RFC 3934, 289 October 2004. 291 [RFC3935] Alvestrand, H., "A Mission Statement for the IETF", 292 BCP 95, RFC 3935, October 2004. 294 [RFC3967] Bush, R. and T. Narten, "Clarifying when Standards Track 295 Documents may Refer Normatively to Documents at a Lower 296 Level", BCP 97, RFC 3967, December 2004. 298 [RFC3978] Bradner, S., "IETF Rights in Contributions", BCP 78, 299 RFC 3978, March 2005. 301 [RFC3979] Bradner, S., "Intellectual Property Rights in IETF 302 Technology", BCP 79, RFC 3979, March 2005. 304 [RFC4052] Daigle, L. and Internet Architecture Board, "IAB Processes 305 for Management of IETF Liaison Relationships", BCP 102, 306 RFC 4052, April 2005. 308 [RFC4053] Trowbridge, S., Bradner, S., and F. Baker, "Procedures for 309 Handling Liaison Statements to and from the IETF", 310 BCP 103, RFC 4053, April 2005. 312 [RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF 313 Administrative Support Activity (IASA)", BCP 101, 314 RFC 4071, April 2005. 316 [RFC4333] Huston, G. and B. Wijnen, "The IETF Administrative 317 Oversight Committee (IAOC) Member Selection Guidelines and 318 Process", BCP 113, RFC 4333, December 2005. 320 [RFC4371] Carpenter, B. and L. Lynch, "BCP 101 Update for IPR 321 Trust", BCP 101, RFC 4371, January 2006. 323 7.2. Informative References 325 [I-D.hoffman-taobis] 326 Harris, S. and P. Hoffman, "The Tao of IETF - A Novice's 327 Guide to the Internet Engineering Task Force", 328 draft-hoffman-taobis-08 (work in progress), June 2006. 330 [I-D.iab-liaison-guidelines] 331 Andersson, L., "Guidelines for Acting as an IETF Liaison 332 to Another Organization", draft-iab-liaison-guidelines-04 333 (work in progress), June 2006. 335 [I-D.iesg-discuss-criteria] 336 Peterson, J., "DISCUSS Criteria in IESG Review", 337 draft-iesg-discuss-criteria-02 (work in progress), 338 February 2006. 340 [I-D.mankin-pub-req] 341 Mankin, A. and S. Hayes, "Requirements for IETF Technical 342 Publication Service", draft-mankin-pub-req-11 (work in 343 progress), July 2006. 345 [I-D.rfc-editor-rfc2223bis] 346 Reynolds, J. and R. Braden, "Instructions to Request for 347 Comments (RFC) Authors", draft-rfc-editor-rfc2223bis-08 348 (work in progress), July 2004. 350 [RFC1264] Hinden, R., "Internet Engineering Task Force Internet 351 Routing Protocol Standardization Criteria", RFC 1264, 352 October 1991. 354 [RFC1311] Postel, J., "Introduction to the STD Notes", RFC 1311, 355 March 1992. 357 [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, 358 October 1996. 360 [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors", 361 RFC 2223, October 1997. 363 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 364 June 1999. 366 [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of 367 Understanding Concerning the Technical Work of the 368 Internet Assigned Numbers Authority", RFC 2860, June 2000. 370 [RFC3160] Harris, S., "The Tao of IETF - A Novice's Guide to the 371 Internet Engineering Task Force", RFC 3160, August 2001. 373 [RFC3669] Brim, S., "Guidelines for Working Groups on Intellectual 374 Property Issues", RFC 3669, February 2004. 376 [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, 377 February 2004. 379 Author's Address 381 Brian Carpenter (ed) 382 IBM 383 8 Chemin de Blandonnet 384 1214 Vernier, 385 Switzerland 387 Email: brc@zurich.ibm.com 389 Full Copyright Statement 391 Copyright (C) The Internet Society (2006). 393 This document is subject to the rights, licenses and restrictions 394 contained in BCP 78, and except as set forth therein, the authors 395 retain all their rights. 397 This document and the information contained herein are provided on an 398 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 399 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 400 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 401 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 402 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 403 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 405 Intellectual Property 407 The IETF takes no position regarding the validity or scope of any 408 Intellectual Property Rights or other rights that might be claimed to 409 pertain to the implementation or use of the technology described in 410 this document or the extent to which any license under such rights 411 might or might not be available; nor does it represent that it has 412 made any independent effort to identify any such rights. Information 413 on the procedures with respect to rights in RFC documents can be 414 found in BCP 78 and BCP 79. 416 Copies of IPR disclosures made to the IETF Secretariat and any 417 assurances of licenses to be made available, or the result of an 418 attempt made to obtain a general license or permission for the use of 419 such proprietary rights by implementers or users of this 420 specification can be obtained from the IETF on-line IPR repository at 421 http://www.ietf.org/ipr. 423 The IETF invites any interested party to bring to its attention any 424 copyrights, patents or patent applications, or other proprietary 425 rights that may cover technology that may be required to implement 426 this standard. Please address the information to the IETF at 427 ietf-ipr@ietf.org. 429 Acknowledgment 431 Funding for the RFC Editor function is provided by the IETF 432 Administrative Support Activity (IASA).