The process of creating a standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience.
The basic formal definition of the IETF standards process is RFC 2026 (BCP 9). However, this document has been amended several times. The intellectual property rules are now separate, in RFC 5378 (BCP 78) (rights in contributions) and RFC 8179 (BCP 79) (rights in technology). Another update is RFC 5742 (BCP 92) (independent submissions to the RFC Editor).
From RFC 2026, section 1.2:
In outline, the process of creating an Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience, is adopted as a Standard by the appropriate body... and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all of the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community.
The goals of the Internet Standards Process are:
- technical excellence;
- prior implementation and testing;
- clear, concise, and easily understood documentation;
- openness and fairness; and
... The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. On the other hand, today's rapid development of networking technology demands timely development of standards. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, thorough testing before adoption of a standard, or openness and fairness. The welcomes the critical evaluation of protocols and has provided guidance on how to report vulnerabilities.
Choosing between Informational and Experimental Status
This document reproduces the rules for classifying documents as Informational and Experimental from RFC 2026, and amplifies those rules with guidelines relevant to ongoing IESG evaluations. It is not intended to change any of the underlying principles.
The Role of the IESG in the Standards Process
The IESG reviews and approves working group documents and candidates for the IETF standards track, and reviews other candidates for publication in the RFC series
This page lists the appeals submitted to the IESG as part of the IETF standards process and any replies by the IESG.
IESG Ballot Procedures
This document describes the IESG ballot procedures. Three cases are described. For the vast majority of documents, the Normal IESG Ballot Procedure is used, and neither of the other procedures comes into play.
The IETF process: an informal guide
This informal guide to the Internet Engineering Task Force (IETF) standards process aims to assist IETF participants by providing an introduction to the variety of documents that describe it, as well as related groups and processes.
Proposing new work
Any IETF participant can propose new work, but in order for new work to be chartered, some preparation is necessary.