Network Working Group B. Carpenter (ed) Internet-Draft IBM Expires: August 24, 2006 February 20, 2006 The IETF Process: a Roadmap draft-carpenter-procdoc-roadmap-04 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 August 24, 2006. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This document describes a roadmap for various IETF process documents, intended both to assist IETF participants and to support discussions about process reform. Carpenter (ed) Expires August 24, 2006 [Page 1] Internet-Draft The IETF Process: a Roadmap February 2006 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 . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 Intellectual Property and Copyright Statements . . . . . . . . . . 11 Carpenter (ed) Expires August 24, 2006 [Page 2] Internet-Draft The IETF Process: a Roadmap February 2006 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, and mentions some (but not all) drafts covering possible changes and updates. 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. Modifying the process 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 Carpenter (ed) Expires August 24, 2006 [Page 3] Internet-Draft The IETF Process: a Roadmap February 2006 Format and mechanics for drafts Format and mechanics for archival publications 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. Drafts are cited by filename only; the curious may consult http://tools.ietf.org/id/ . o Modifying the process A general description of how the IETF modifies its own processes does not exist, but probably should. An experimental procedure is described in [RFC3933]. Some recent discussion is captured in draft-davies-pesci-initial-considerations. o General description of workflow in the IETF This document does not exist, although the Tao ([RFC3160], draft-hoffman-taobis) offers contains most of it informally. How ideas for new work enter the IETF, reach a BOF (draft-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. o Definition of standards track and related document types. This material is currently embedded in [RFC2026]. Additional requirements for routing protocols are defined in [RFC1264], being updated by draft-fenner-zinin-rtg-standard-reqts. 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 [RFC2026], covering standards track, BCP and experimental documents. The STD (standard) designation is documented in [RFC1311]. A variance procedure for down-level normative references is in [RFC3967]. Carpenter (ed) Expires August 24, 2006 [Page 4] Internet-Draft The IETF Process: a Roadmap February 2006 A specific process for advancing MIB documents is in [RFC2438]. * Information This material is currently embedded in [RFC2026], covering informational and historic documents. A distinction between obsolete and deprecated documents is not currently made. * Descriptors See draft-ietf-newtrk-repurposing-isd and draft-otis-newtrk-rfc-set. o Intellectual Property * Rights in Contributions [RFC3978], draft-ietf-ipr-rules-update * Rights in Technology [RFC3979] (Guidelines, [RFC3669]) * Trademarks draft-ietf-ipr-trademarks * IETF Trust [RFC4371] o Review and approval process This material is currently embedded in [RFC2026]. * 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 [RFC2026]. o Bodies involved in the process Bodies involved [RFC2028]; Defining the IETF [RFC3233]; Mission Statement [RFC3935]. * WG procedures [RFC2418] * IESG [RFC3710] * Proposed review panel draft-klensin-stds-review-panel * IAB [RFC2850] + Liaison management [RFC4052], [RFC4053], draft-iab-liaison-guidelines * Nomcom [RFC3777] , draft-klensin-nomcom-term * Relationship to ISOC [RFC2031], [RFC3677] o Conduct of participants [RFC3005], [RFC3184], [RFC3683], [RFC3934], and also discussed in [RFC2418] and in the Tao ([RFC3160], draft-hoffman-taobis). Carpenter (ed) Expires August 24, 2006 [Page 5] Internet-Draft The IETF Process: a Roadmap February 2006 o Publication process * Requirements This is the subject of the techspec BOFs at IETF 64 and 65. See draft-mankin-pub-req. * 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. [RFC2223] is the published version today. Those writing standards will find the following especially useful: [RFC2360], [RFC2434], [RFC3552]. * Direct submissions to RFC Editor [RFC3932] o Registration process * Requirements [RFC2860] * Guidelines for authors [RFC2434], draft-narten-iana-considerations-rfc2434bis * Assignment criteria draft-klensin-iana-reg-policy * Format and mechanics Case by case at IANA web site. o Administration [RFC4071], [RFC4371], [RFC4333], 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 are 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[RFC2629]. 7. Change log [RFC Editor: please remove this section] Carpenter (ed) Expires August 24, 2006 [Page 6] Internet-Draft The IETF Process: a Roadmap February 2006 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 8. References 8.1. Normative References [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. [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, Carpenter (ed) Expires August 24, 2006 [Page 7] Internet-Draft The IETF Process: a Roadmap February 2006 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 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. Carpenter (ed) Expires August 24, 2006 [Page 8] Internet-Draft The IETF Process: a Roadmap February 2006 [RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF Administrative Support Activity (IASA)", BCP 101, RFC 4071, April 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. 8.2. Informative References [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. [RFC3160] Harris, S., "The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force", RFC 3160, August 2001. [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. Carpenter (ed) Expires August 24, 2006 [Page 9] Internet-Draft The IETF Process: a Roadmap February 2006 Author's Address Brian Carpenter (ed) IBM 8 Chemin de Blandonnet 1214 Vernier, Switzerland Email: brc@zurich.ibm.com Carpenter (ed) Expires August 24, 2006 [Page 10] Internet-Draft The IETF Process: a Roadmap February 2006 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 (2006). 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 August 24, 2006 [Page 11]