]> Organization of IETF Process Documents The University of Auckland
School of Computer Science The University of Auckland PB 92019 Auckland 1142 New Zealand brian.e.carpenter@gmail.com
General GenDispatch Internet-Draft This document suggests that the IETF's many documents related to process and procedures need to be better organized, and suggests a possible framework for this. About This Document Status information for this document may be found at . Discussion of this document takes place on the GenDispatch Working Group mailing list (), which is archived at . Subscribe at .
Introduction The IETF has a large number of documents (mainly RFCs) devoted to its standard process, its rules and procedures in general, and how it does its work. Some of these are BCPs, some of them are Informational RFCs, with occasional Experimental RFCs. In addition there are IESG Statements for specific topics, summaries of processes and procedures on the IETF web site, presentations made at IETF meetings or in educational material, snippets in email archives, unwritten rules, and external information such as this. At a rough estimate, to have a complete understanding of IETF processes and procedures, a person would need to consult about 65 BCPs and RFCs -- there is an out of date list. There are also at least 30 relevant IESG statements. This situation is clearly problematic: obviously it is a stumbling block for newcomers, and even for people with years of IETF participation it can be a source of confusion, mistakes, and wasted time. This draft suggests that at the very least, the IETF needs an organizing principle for its process and procedural documents. Beyond that it seems desirable to start a project, which would take many years to complete, of consolidating documents (where that is feasible) and ensuring that they fit together into a common framework that will help newcomers and experienced participants alike. and are good examples of such consolidation. This document suggests an outline of a framework within which such consolidated documents could exist. It is not expected that this draft will become an RFC.
Framework The following list of topics is only a suggestion. The idea is that process documents would be organized to fit into one of these topics, with as little overlap as possible.
  • Workflow in the IETF
  • Bodies involved in the process
  • Document types
  • Standards track documents
  • Review and approval process
  • Intellectual Property Rights
  • Conduct of participants
  • Publication process (RFC Editor)
  • Parameter registration process (IANA)
  • Meetings
  • Administration and support
  • Process for modifying process and procedures
IANA Considerations No IANA actions are needed.
Security Considerations This document does not directly affect the security of the Internet.
Acknowledgements Useful comments were received from ...
Informative References The Internet Standards Process Akamai Technologies SOBCO This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. It also addresses the intellectual property rights and copyright issues associated with the standards process. This document obsoletes RFC2026, RFC5657, RFC6410, RFC7100, RFC7127, RFC7475, RFC8179, RFC8789, and RFC9282. It updates RFC5378, RFC5657. It also updated RFC7475, and with [bis2418], obsoletes it. IETF Working Group Guidelines and Procedures Akamai Technologies SOBCO The Internet Engineering Task Force (IETF) has responsibility for developing and reviewing specifications intended as Internet Standards. IETF activities are organized into working groups (WGs). This document describes the guidelines and procedures for formation and operation of IETF working groups. It also describes the formal relationship between IETF participants WG and the Internet Engineering Steering Group (IESG) and the basic duties of IETF participants, including WG Chairs, WG participants, and IETF Area Directors. This document obsoletes RFC2418, and RFC3934. It also includes the changes from RFC7475, and with [bis2026], obsoletes it. It also includes a summary of the changes implied in RFC7776 and incorporates the changes from RFC8717 and RFC9141.
Change Log [RFC Editor: please remove]
Draft-00
  • Original version