Internet DRAFT - draft-carpenter-procdoc-roadmap
draft-carpenter-procdoc-roadmap
Network Working Group B. Carpenter (ed)
Internet-Draft IBM
Intended status: Informational August 2, 2006
Expires: February 3, 2007
The IETF Process: an Informal Guide
draft-carpenter-procdoc-roadmap-05
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 February 3, 2007.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document is an informal guide to various IETF process documents,
intended both to assist IETF participants and to support possible
future discussions about process reform.
Carpenter (ed) Expires February 3, 2007 [Page 1]
Internet-Draft IETF Process: Informal Guide August 2006
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. Security Considerations . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
6. Change log [RFC Editor: please remove this section] . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . . . . 10
Carpenter (ed) Expires February 3, 2007 [Page 2]
Internet-Draft IETF Process: Informal Guide August 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.
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
Suach a document does not exist, although the Tao ([RFC3160], to be
replaced by [I-D.hoffman-taobis]) offers most of it informally: 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 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 are currently defined in
[RFC1264]. The newtrk WG was chartered to revise the standards track
- multiple proposals have been floated, but no conclusions have been
reached.
o 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]. A
specific process for advancing MIB documents is in [RFC2438].
Carpenter (ed) Expires February 3, 2007 [Page 3]
Internet-Draft IETF Process: Informal Guide August 2006
o Information
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]
o Rights in Technology [RFC3979] (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
http://www.alvestrand.no/ietf/gen/art/review-guidelines.html
o Criteria for approval
Material on current IESG practice can be found in
[I-D.iesg-discuss-criteria]
* 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]
o IESG [RFC3710]
o IAB [RFC2850]
* Liaison management [RFC4052], [RFC4053], (guidance in
[I-D.iab-liaison-guidelines])
o Nomcom [RFC3777]
o Relationship to ISOC [RFC2031], [RFC3677]
2.6. Conduct of participants
See [RFC3005], [RFC3184], [RFC3683], [RFC3934]; also discussed in
[RFC2418] and in the Tao ([RFC3160], to be replaced by
[I-D.hoffman-taobis]).
o Appeal process
This material is currently embedded in [RFC2026].
Carpenter (ed) Expires February 3, 2007 [Page 4]
Internet-Draft IETF Process: Informal Guide August 2006
2.7. Publication process
o Requirements
[I-D.mankin-pub-req]
o Format and mechanics for drafts
http://www.ietf.org/ietf/1id-guidelines.html
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
http://www.ietf.org/IESG/content/experiments.html).
3. Security Considerations
This document has no security implications for the Internet.
4. IANA Considerations
This document requires no action by the IANA. However, it does
mention how IANA's registration functions are documented.
5. Acknowledgements
Useful comments on this document were made by: Harald Alvestrand,
Scott Bradner, Spencer Dawkins, Leslie Daigle, John Klensin, and
Carpenter (ed) Expires February 3, 2007 [Page 5]
Internet-Draft IETF Process: Informal Guide August 2006
others.
This document was produced using the xml2rfc tool [RFC2629].
6. Change log [RFC Editor: please remove this section]
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
7. References
7.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
Carpenter (ed) Expires February 3, 2007 [Page 6]
Internet-Draft IETF Process: Informal Guide August 2006
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,
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,
Carpenter (ed) Expires February 3, 2007 [Page 7]
Internet-Draft IETF Process: Informal Guide August 2006
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.
[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.
7.2. Informative References
[I-D.hoffman-taobis]
Harris, S. and P. Hoffman, "The Tao of IETF - A Novice's
Guide to the Internet Engineering Task Force",
draft-hoffman-taobis-08 (work in progress), June 2006.
[I-D.iab-liaison-guidelines]
Andersson, L., "Guidelines for Acting as an IETF Liaison
to Another Organization", draft-iab-liaison-guidelines-04
(work in progress), June 2006.
[I-D.iesg-discuss-criteria]
Peterson, J., "DISCUSS Criteria in IESG Review",
draft-iesg-discuss-criteria-02 (work in progress),
February 2006.
[I-D.mankin-pub-req]
Mankin, A. and S. Hayes, "Requirements for IETF Technical
Publication Service", draft-mankin-pub-req-11 (work in
progress), July 2006.
[I-D.rfc-editor-rfc2223bis]
Reynolds, J. and R. Braden, "Instructions to Request for
Carpenter (ed) Expires February 3, 2007 [Page 8]
Internet-Draft IETF Process: Informal Guide August 2006
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.
[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.
Author's Address
Brian Carpenter (ed)
IBM
8 Chemin de Blandonnet
1214 Vernier,
Switzerland
Email: brc@zurich.ibm.com
Carpenter (ed) Expires February 3, 2007 [Page 9]
Internet-Draft IETF Process: Informal Guide August 2006
Full 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.
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.
Intellectual Property
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.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Carpenter (ed) Expires February 3, 2007 [Page 10]
