ION The IETF Process: an Informal Guide Status: Approved Name: ion-procdocs Title: Informal Guide to IETF Process Documents Date: 2007-07-19 Approved by: IESG Document editor: Brian Carpenter Discussion forum: ietf@ietf.org Abstract This document is an informal guide to various IETF process documents, intended mainly to assist IETF participants in navigating the labyrinth. , et al. [Page 1] IETF Process: Informal Guide July 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The guide . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. General description of workflow in the IETF . . . . . . . . 3 2.2. Definition of standards track and related document types . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.3. Intellectual Property . . . . . . . . . . . . . . . . . . . 4 2.4. Review and approval process . . . . . . . . . . . . . . . . 4 2.5. Bodies involved in the process . . . . . . . . . . . . . . 4 2.6. Conduct of participants . . . . . . . . . . . . . . . . . . 4 2.7. Publication process . . . . . . . . . . . . . . . . . . . . 5 2.8. Parameter registration process . . . . . . . . . . . . . . 5 2.9. Administration . . . . . . . . . . . . . . . . . . . . . . 5 2.10. Modifying the process . . . . . . . . . . . . . . . . . . . 5 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 4. Change log . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.1. Normative References (Rules) . . . . . . . . . . . . . . . 6 5.2. Informative References . . . . . . . . . . . . . . . . . . 8 , et al. [Page 2] IETF Process: Informal Guide July 2007 1. Introduction BCP 9 [RFC2026] has been the basis for the IETF standards process for many years. However, many other process documents exist, some of which are partial updates to BCP 9. This situation is confusing and would ideally be resolved by a clear set of interlocking documents. The present document suggests a structured way of looking at the existing documents. It is difficult to linearise a complicated and interlocked process. This document presents a guide in one particular order, but that is not intended to imply priority or importance, and it cannot capture all interactions between components. Formally, IETF processes are described in Best Current Practices (BCPs) published as RFCs. Most of the cited RFCs are BCPs. RFC numbers have been used rather than BCP numbers, for convenient lookup. To avoid any accidental ambiguity, this guide does not attempt to paraphrase or summarize their contents; the reader should consult the original RFCs. 2. The guide 2.1. General description of workflow in the IETF Such a document does not exist, although the Tao [RFC4677] offers most of it informally: How ideas for new work enter the IETF, reach a BOF (also see [I-D.narten-successful-bof]), enter IAB or IRTF discussion, and possibly become material for a new or existing WG. How WGs are chartered - the Area Director's role. How specific proposals become drafts and flow through the development, review and approval process. 2.2. Definition of standards track and related document types This material is currently embedded in [RFC2026]. Additional requirements for routing protocols were previously defined in [RFC1264], but this is now obsolete [RFC4794]. It should be noted that practice and interpretation have grown around the documented rules; the Tao [RFC4677] is helpful in this respect. o Technical Specifications This material is currently embedded in [RFC2026], covering standards track, BCP and Experimental documents. The STD (standard) designation is documented in [RFC1311]. Variance procedures for down-level normative references are in [RFC3967] and [RFC4897]. A specific process for advancing MIB documents is in [RFC2438]. , et al. [Page 3] IETF Process: Informal Guide July 2007 o Informational Material This material is currently embedded in [RFC2026], covering Informational and Historic documents. A distinction between obsolete and deprecated documents is not currently made in the IETF. 2.3. Intellectual Property o Rights in Contributions [RFC3978], [RFC4748]. For MIBs, also see [RFC4181], [RFC4841]. o Rights in Technology [RFC3979], [RFC4879] (Guidelines, [RFC3669]) o Trademarks [RFC3978] o IETF Trust [RFC4371] 2.4. Review and approval process This material is currently embedded in [RFC2026]. o Criteria for review Various review teams exist in different IETF Areas, with their own technical criteria. For the General Area, see o Criteria for approval Material on current IESG practice can be found in [I-D.iesg-discuss-criteria] (to become an ION itself) * Appeal process This material is currently embedded in [RFC2026]. 2.5. Bodies involved in the process Bodies involved [RFC2028]; Defining the IETF [RFC3233]; Mission Statement [RFC3935]. o WG procedures [RFC2418], [RFC4858] o IESG [RFC3710] o IAB [RFC2850] * Liaison management [RFC4052], [RFC4053], (guidance in [RFC4691]) o Nomcom [RFC3777] o Relationship to ISOC [RFC2031], [RFC3677] 2.6. Conduct of participants See [RFC3005], [RFC3184], [RFC3683], [RFC3934], [RFC4633]; also discussed in [RFC2418] and in the Tao[RFC4677]. o Appeal process This material is currently embedded in [RFC2026]. , et al. [Page 4] IETF Process: Informal Guide July 2007 2.7. Publication process o Requirements [RFC4714] o Format and mechanics for drafts o Format and mechanics for archival publications [RFC2223] is the published version today. The RFC Editor currently refers to [I-D.rfc-editor-rfc2223bis]. Those writing standards will find the following especially useful: [RFC2360], [RFC2434], [RFC3552]. o Direct submissions to RFC Editor [RFC3932] 2.8. Parameter registration process o Requirements [RFC2860] o Guidelines [RFC2434] o Format and mechanics Case by case at IANA web site. 2.9. Administration See [RFC4071], [RFC4371], [RFC4333]. 2.10. Modifying the process [RFC2026] defines how process BCPs are discussed and approved. A general description of how the IETF modifies its own processes does not exist, but probably should. An experimental procedure is described in [RFC3933] (also see ). 3. Acknowledgements Useful comments on this document were made by: Harald Alvestrand, Scott Bradner, Spencer Dawkins, Leslie Daigle, John Klensin, Paul Hoffman, and others. This document was produced using the xml2rfc tool [RFC2629]. 4. Change log DRAFT ion-procdocs 2007-06-27: cited RFC 4897, 4879, 4181, 4841, 4858. DRAFT ion-procdocs 2007-02-14: public comments incorporated , et al. [Page 5] IETF Process: Informal Guide July 2007 DRAFT ion-procdocs 2007-01-29: converted to ION format draft-carpenter-procdoc-roadmap-05: Earlier drafts of this document included references to drafts proposing changes to the standards process. These have been removed to make this document a more stable reference. It has been renamed from "roadmap" to "guide." Some editorial rearrangements have been made. 2006-08-02 draft-carpenter-procdoc-roadmap-04: minor additions, tuned Abstract and Introduction, 2006-02-20 draft-carpenter-procdoc-roadmap-03: minor additions, 2005-12-20 draft-carpenter-procdoc-roadmap-02: minor additions, 2005-10-11 draft-carpenter-procdoc-roadmap-01: minor additions, 2005-09-20 draft-carpenter-procdoc-roadmap-00: original version, 2005-08-22 5. References 5.1. Normative References (Rules) [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996. [RFC2360] Scott, G., "Guide for Internet Standards Writers", BCP 22, RFC 2360, June 1998. [RFC2418] Bradner, S., "IETF Working Group Guidelines and Procedures", BCP 25, RFC 2418, September 1998. [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [RFC2438] O'Dell, M., Alvestrand, H., Wijnen, B., and S. Bradner, "Advancement of MIB specifications on the IETF Standards Track", BCP 27, RFC 2438, October 1998. [RFC2850] Internet Architecture Board and B. Carpenter, "Charter of the Internet Architecture Board (IAB)", BCP 39, RFC 2850, May 2000. , et al. [Page 6] IETF Process: Informal Guide July 2007 [RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, RFC 3005, November 2000. [RFC3184] Harris, S., "IETF Guidelines for Conduct", BCP 54, RFC 3184, October 2001. [RFC3233] Hoffman, P. and S. Bradner, "Defining the IETF", BCP 58, RFC 3233, February 2002. [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, July 2003. [RFC3677] Daigle, L. and Internet Architecture Board, "IETF ISOC Board of Trustee Appointment Procedures", BCP 77, RFC 3677, December 2003. [RFC3683] Rose, M., "A Practice for Revoking Posting Rights to IETF mailing lists", BCP 83, RFC 3683, February 2004. [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees", BCP 10, RFC 3777, June 2004. [RFC3932] Alvestrand, H., "The IESG and RFC Editor Documents: Procedures", BCP 92, RFC 3932, October 2004. [RFC3933] Klensin, J. and S. Dawkins, "A Model for IETF Process Experiments", BCP 93, RFC 3933, November 2004. [RFC3934] Wasserman, M., "Updates to RFC 2418 Regarding the Management of IETF Mailing Lists", BCP 94, RFC 3934, October 2004. [RFC3935] Alvestrand, H., "A Mission Statement for the IETF", BCP 95, RFC 3935, October 2004. [RFC3967] Bush, R. and T. Narten, "Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level", BCP 97, RFC 3967, December 2004. [RFC3978] Bradner, S., "IETF Rights in Contributions", BCP 78, RFC 3978, March 2005. [RFC3979] Bradner, S., "Intellectual Property Rights in IETF Technology", BCP 79, RFC 3979, March 2005. [RFC4052] Daigle, L. and Internet Architecture Board, "IAB Processes , et al. [Page 7] IETF Process: Informal Guide July 2007 for Management of IETF Liaison Relationships", BCP 102, RFC 4052, April 2005. [RFC4053] Trowbridge, S., Bradner, S., and F. Baker, "Procedures for Handling Liaison Statements to and from the IETF", BCP 103, RFC 4053, April 2005. [RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF Administrative Support Activity (IASA)", BCP 101, RFC 4071, April 2005. [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB Documents", BCP 111, RFC 4181, September 2005. [RFC4333] Huston, G. and B. Wijnen, "The IETF Administrative Oversight Committee (IAOC) Member Selection Guidelines and Process", BCP 113, RFC 4333, December 2005. [RFC4371] Carpenter, B. and L. Lynch, "BCP 101 Update for IPR Trust", BCP 101, RFC 4371, January 2006. [RFC4748] Bradner, S., "RFC 3978 Update to Recognize the IETF Trust", BCP 78, RFC 4748, October 2006. [RFC4841] Heard, C., "RFC 4181 Update to Recognize the IETF Trust", BCP 111, RFC 4841, March 2007. [RFC4879] Narten, T., "Clarification of the Third Party Disclosure Procedure in RFC 3979", BCP 79, RFC 4879, April 2007. [RFC4897] Klensin, J. and S. Hartman, "Handling Normative References to Standards-Track Documents", BCP 97, RFC 4897, June 2007. 5.2. Informative References [I-D.iesg-discuss-criteria] Peterson, J., "DISCUSS Criteria in IESG Review", draft-iesg-discuss-criteria-02 (work in progress), February 2006. [I-D.narten-successful-bof] Narten, T., "Considerations for Having a Successful BOF", draft-narten-successful-bof-03 (work in progress), October 2007. [I-D.rfc-editor-rfc2223bis] Reynolds, J. and R. Braden, "Instructions to Request for , et al. [Page 8] IETF Process: Informal Guide July 2007 Comments (RFC) Authors", draft-rfc-editor-rfc2223bis-08 (work in progress), July 2004. [RFC1264] Hinden, R., "Internet Engineering Task Force Internet Routing Protocol Standardization Criteria", RFC 1264, October 1991. [RFC1311] Postel, J., "Introduction to the STD Notes", RFC 1311, March 1992. [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, October 1996. [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors", RFC 2223, October 1997. [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, June 1999. [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority", RFC 2860, June 2000. [RFC3669] Brim, S., "Guidelines for Working Groups on Intellectual Property Issues", RFC 3669, February 2004. [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, February 2004. [RFC4633] Hartman, S., "Experiment in Long-Term Suspensions From Internet Engineering Task Force (IETF) Mailing Lists", RFC 4633, August 2006. [RFC4677] Hoffman, P. and S. Harris, "The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force", RFC 4677, September 2006. [RFC4691] Andersson, L., "Guidelines for Acting as an IETF Liaison to Another Organization", RFC 4691, October 2006. [RFC4714] Mankin, A. and S. Hayes, "Requirements for IETF Technical Publication Service", RFC 4714, October 2006. [RFC4794] Fenner, B., "RFC 1264 Is Obsolete", RFC 4794, December 2006. [RFC4858] Levkowetz, H., Meyer, D., Eggert, L., and A. Mankin, "Document Shepherding from Working Group Last Call to , et al. [Page 9] IETF Process: Informal Guide July 2007 Publication", RFC 4858, May 2007. , et al. [Page 10]