Network Working Group B. Carpenter (ed) Internet-Draft IBM Expires: March 24, 2006 September 20, 2005 The IETF Process: a Roadmap draft-carpenter-procdoc-roadmap-01 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on March 24, 2006. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This document describes a roadmap for various IETF process documents, to support ongoing discussions about process reform. Carpenter (ed) Expires March 24, 2006 [Page 1] Internet-Draft The IETF Process: a Roadmap September 2005 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Outline of roadmap . . . . . . . . . . . . . . . . . . . . . . 3 3. Details of roadmap . . . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 7. Change log [RFC Editor: please remove this section] . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9 Intellectual Property and Copyright Statements . . . . . . . . . . 10 Carpenter (ed) Expires March 24, 2006 [Page 2] Internet-Draft The IETF Process: a Roadmap September 2005 1. Introduction BCP 9 [1] 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 needs to be resolved by a clear set of interlocking documents. The present document suggests a structured way of looking at these documents, and some commentary about what already exists or has been proposed. It is difficult to linearise a complicated and interlocked process. This document presents the roadmap in one particular order, but that is not intended to imply priority or importance, and it cannot capture all interactions between components. 2. Outline of roadmap For readability of what follows, this section simply lists the process document structure. The following section repeats this structure with explanatory text. General description of workflow in the IETF Definition of standards track and related document types Specifications Information Descriptors Intellectual Property Rights in Contributions Rights in Technology Trademarks Review and approval process Criteria for review Criteria for approval Appeal process Bodies involved in the process WG procedures IESG Review panel TBD IAB Liaison management Nomcom Conduct of participants Publication process Requirements Format and mechanics for drafts Format and mechanics for archival publications Carpenter (ed) Expires March 24, 2006 [Page 3] Internet-Draft The IETF Process: a Roadmap September 2005 Direct submissions to RFC Editor Registration process Requirements Guidelines for authors Assignment criteria Format and mechanics Administration 3. Details of roadmap Note 1: RFC numbers have been used rather than BCP numbers, for convenient lookup. Most of the cited RFCs are BCPs. Of course, many of them may need updating. Note 2: Where drafts are cited, it is not implied that they have reached consensus. Internet-Draft citations have not been given in detail; see https://datatracker.ietf.org/public/idindex.cgi?command=search_id. o General description of workflow in the IETF This document does not exist, although the Tao (RFC 3160[20], draft-hoffman-taobis) offers hints, but it is needed. How ideas for new work enter the IETF, reach a BOF, enter IAB or IRTF discussion, and possibly become material for a new or existing WG. How WGs are chartered - the AD role. How specific proposals become drafts and flow through the development, review and approval process. o Definition of standards track and related document types. This material is currently embedded in RFC 2026[1]. The newtrk WG is chartered to revise the standards track - multiple proposals have been floated, most recently draft-carpenter-newtrk-twostep and draft-loughney-newtrk-one-size-fits-all. * Specifications This material is currently embedded in RFC 2026[1], covering standards track, BCP and experimental documents. A variance procedure for down-level normative references is in RFC 3967[2]. * Information This material is currently embedded in RFC 2026[1], covering informational and historic documents. A distinction between obsolete and deprecated documents should probably be added. * Descriptors See draft-ietf-newtrk-repurposing-isd and draft-otis-newtrk-rfc-set. Carpenter (ed) Expires March 24, 2006 [Page 4] Internet-Draft The IETF Process: a Roadmap September 2005 o Intellectual Property * Rights in Contributions RFC 3978[3], draft-bradner-author-contributors, draft-bradner-rfc-extracts * Rights in Technology RFC 3979[4] (Guidelines, RFC 3669[21]) * Trademarks draft-ietf-ipr-trademarks o Review and approval process This material is currently embedded in RFC 2026[1]. * Criteria for review Some material was in draft-carpenter-solution-sirs and a version can be found at http://www.alvestrand.no/ietf/gen/art/review-guidelines.html * Criteria for approval Material on current IESG practice can be found in draft-iesg-discuss-criteria + Appeal process This material is currently embedded in RFC 2026[1]. o Bodies involved in the process Bodies involved, RFC 2028[5]; Defining the IETF, RFC 3233[6]; Mission Statement, RFC 3935[7]. * WG procedures RFC 2418[8] * IESG RFC 3710[22] * Proposed review panel draft-klensin-stds-review-panel * IAB RFC 2850[9] + Liaison management RFC 4052[10], RFC 4053[11], draft-andersson-iab-liaison-guidelines * Nomcom RFC 3777[12] , draft-klensin-nomcom-term * Relationship to ISOC RFC 2031[23], RFC 3677[13] o Conduct of participants RFC 3005[14], RFC 3184[15], RFC 3683[16] , and also discussed in RFC 2418[8] and in the Tao (RFC 3160[20], draft-hoffman-taobis). o Publication process * Requirements This is intended to be the subject of the techspec BOF in Vancouver. Carpenter (ed) Expires March 24, 2006 [Page 5] Internet-Draft The IETF Process: a Roadmap September 2005 * Format and mechanics for drafts http://www.ietf.org/ietf/1id-guidelines.html * Format and mechanics for archival publications See draft-hoffman-rfc-author-guide for a minimalist version, or draft-rfc-editor-rfc2223bis for a version including other topics. RFC 2223[24] is the published version today. * Direct submissions to RFC Editor RFC 3932[17] o Registration process * Requirements RFC 2860[25] * Guidelines for authors RFC 2434[18], draft-narten-iana-considerations-rfc2434bis * Assignment criteria draft-klensin-iana-reg-policy * Format and mechanics Case by case at IANA web site. o Administration RFC 4071[19], draft-carpenter-bcp101-update, draft-iab-iesg-iaoc-selection, draft-alvestrand-subpoena 4. Security Considerations This document has no security implications for the Internet. 5. IANA Considerations This document requires no action by the IANA. However, it does mention how IANA's registration functions should be documented. 6. Acknowledgements Useful comments on this document were made by: Harald Alvestrand, Scott Bradner, Spencer Dawkins, Leslie Daigle, John Klensin,... This document was produced using the xml2rfc tool[26]. 7. Change log [RFC Editor: please remove this section] draft-carpenter-procdoc-roadmap-01: minor additions, 2005-09-20 draft-carpenter-procdoc-roadmap-00: original version, 2005-08-22 Carpenter (ed) Expires March 24, 2006 [Page 6] Internet-Draft The IETF Process: a Roadmap September 2005 8. References 8.1. Normative References [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [2] 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. [3] Bradner, S., "IETF Rights in Contributions", BCP 78, RFC 3978, March 2005. [4] Bradner, S., "Intellectual Property Rights in IETF Technology", BCP 79, RFC 3979, March 2005. [5] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996. [6] Hoffman, P. and S. Bradner, "Defining the IETF", BCP 58, RFC 3233, February 2002. [7] Alvestrand, H., "A Mission Statement for the IETF", BCP 95, RFC 3935, October 2004. [8] Bradner, S., "IETF Working Group Guidelines and Procedures", BCP 25, RFC 2418, September 1998. [9] Internet Architecture Board and B. Carpenter, "Charter of the Internet Architecture Board (IAB)", BCP 39, RFC 2850, May 2000. [10] Daigle, L. and Internet Architecture Board, "IAB Processes for Management of IETF Liaison Relationships", BCP 102, RFC 4052, April 2005. [11] Trowbridge, S., Bradner, S., and F. Baker, "Procedures for Handling Liaison Statements to and from the IETF", BCP 103, RFC 4053, April 2005. [12] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees", BCP 10, RFC 3777, June 2004. [13] Daigle, L. and Internet Architecture Board, "IETF ISOC Board of Trustee Appointment Procedures", BCP 77, RFC 3677, December 2003. Carpenter (ed) Expires March 24, 2006 [Page 7] Internet-Draft The IETF Process: a Roadmap September 2005 [14] Harris, S., "IETF Discussion List Charter", BCP 45, RFC 3005, November 2000. [15] Harris, S., "IETF Guidelines for Conduct", BCP 54, RFC 3184, October 2001. [16] Rose, M., "A Practice for Revoking Posting Rights to IETF mailing lists", BCP 83, RFC 3683, February 2004. [17] Alvestrand, H., "The IESG and RFC Editor Documents: Procedures", BCP 92, RFC 3932, October 2004. [18] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [19] Austein, R. and B. Wijnen, "Structure of the IETF Administrative Support Activity (IASA)", BCP 101, RFC 4071, April 2005. 8.2. Informative References [20] Harris, S., "The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force", RFC 3160, August 2001. [21] Brim, S., "Guidelines for Working Groups on Intellectual Property Issues", RFC 3669, February 2004. [22] Alvestrand, H., "An IESG charter", RFC 3710, February 2004. [23] Huizer, E., "IETF-ISOC relationship", RFC 2031, October 1996. [24] Postel, J. and J. Reynolds, "Instructions to RFC Authors", RFC 2223, October 1997. [25] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority", RFC 2860, June 2000. [26] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, June 1999. Carpenter (ed) Expires March 24, 2006 [Page 8] Internet-Draft The IETF Process: a Roadmap September 2005 Author's Address Brian Carpenter (ed) IBM 48 Avenue Giuseppe Motta 1211 Geneva 2, Switzerland Email: brc@zurich.ibm.com Carpenter (ed) Expires March 24, 2006 [Page 9] Internet-Draft The IETF Process: a Roadmap September 2005 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Carpenter (ed) Expires March 24, 2006 [Page 10]