|This article relies too much on references to primary sources. (November 2015) (Learn how and when to remove this template message)|
In computer network engineering, an Internet Standard (STD) is a normative specification of a technology or methodology applicable to the Internet. Internet Standards are created and published by the Internet Engineering Task Force (IETF).
An Internet Standard is characterized by technical maturity and usefulness. The IETF also defines a Proposed Standard as a less mature but stable and well-reviewed specification. A Draft Standard is a third, even less mature classification that was discontinued in 2011.
An Internet Standard is a Request for Comments (RFC) or a set of RFCs. An RFC that is to become a Standard or part of a Standard begins as an Internet Draft, and is later, usually after several revisions, accepted and published by the RFC Editor as an RFC and labeled a Proposed Standard. Later, an RFC is elevated as Internet Standard, with an additional sequence number, when maturity has reached an acceptable level. Collectively, these stages are known as the Standards Track, and are defined in RFC 2026 and RFC 6410. The label Historic is applied to deprecated Standards Track documents or obsolete RFCs that were published before the Standards Track was established.
Only the IETF, represented by the Internet Engineering Steering Group (IESG), can approve Standards Track RFCs. The definitive list of Internet Standards is maintained in Internet Standards document STD 1: Internet Official Protocol Standards.
Becoming a standard is a two-step process within the IETF called Proposed Standards and Internet Standards. If an RFC is part of a proposal that is on the Standard Track, then at the first stage, the standard is proposed and subsequently organizations decide whether to implement this Proposed Standard. After the criteria in RFC 6410 is met (two separate implementations, widespread use, no errata etc.), the RFC can advance to Internet Standard.
The Internet Standards Process is defined in several "Best Current Practice" documents, notably BCP 9 (currently[update] RFC 2026 and RFC 6410). There were previously three standard maturity levels Proposed Standard, Draft Standard and Internet Standard. RFC 6410 reduced this to two maturity levels.
A Proposed Standard specification is stable, has resolved known design choices, has received significant community review, and appears to enjoy enough community interest to be considered valuable. Usually, neither implementation nor operational experience is required for the designation of a specification as a Proposed Standard.
Proposed Standards are of such quality that implementations can be deployed in the Internet. However, as with all technical specifications, Proposed Standards may be revised if problems are found or better solutions are identified, when experiences with deploying implementations of such technologies at scale is gathered.
Many Proposed Standards are actually deployed on the Internet and used extensively, as stable protocols. Actual practice has been that full progression through the sequence of standards levels is typically quite rare, and most popular IETF protocols remain at Proposed Standard.
In October 2011 RFC 6410 in essence merged this second and the third Internet Standard maturity level for future Internet Standards. Existing older Draft Standards retain that classification. The IESG can reclassify an old Draft Standard as Proposed Standard after two years (October 2013).
An Internet Standard is characterized by a high degree of technical maturity and by a generally held belief that the specified protocol or service provides significant benefit to the Internet community. Generally Internet Standards cover interoperability of systems on the Internet through defining protocols, message formats, schemas, and languages. The most fundamental of the Internet Standards are the ones defining the Internet Protocol.
An Internet Standard ensures that hardware and software produced by different vendors can work together. Having a standard makes it much easier to develop software and hardware that link different networks because software and hardware can be developed one layer at a time. Normally, the standards used in data communication are called protocols.
Documents submitted to the IETF editor and accepted as an RFC are not revised; if the document has to be changed, it is submitted again and assigned a new RFC number. When an RFC becomes an Internet Standard (STD), it is assigned an STD number but retains its RFC number. When an Internet Standard is updated, its number is unchanged but refers to a different RFC or set of RFCs. For example, in 2007 RFC 3700 was an Internet Standard (STD 1) and in May 2008 it was replaced with RFC 5000. RFC 3700 received Historic status, and RFC 5000 became STD 1.
The list of Internet standards in RFC 5000 ends with STD 68 (RFC 5234, ABNF) published in 2008. It does not cover STD 69 (a set of five EPP RFCs), STD 70 (RFC 5652, CMS) published in 2009, STD 71 (RFC 6152, 8BITMIME), and STD 72 (RFC 6409, Mail Submission) published in 2011.
|Standard Type||Associated Protocols|
|Web||http, CGI, html/xml/vrml/sgml|
|Internet Directory||X.500, LDAP|
|Application||http, FTP, telnet, gopher, wais|
|Videoconferencing||H.320, H.323, Mpeg-1, Mpeg-2|
- "Internet Official Protocol Standards (STD 1)" (plain text). RFC Editor. May 2008. Retrieved 2008-05-25.
- "Characterization of Specifications". Characterization of Proposed Standards. IETF. January 2014. sec. 3. RFC 7127. https://tools.ietf.org/html/rfc7127#section-3. Retrieved March 11, 2016.
- "IETF Review of Proposed Standards". Characterization of Proposed Standards. IETF. January 2014. sec. 2. RFC 7127. https://tools.ietf.org/html/rfc7127#section-2. Retrieved March 11, 2016.
- "STANDARDS ordered by STD". Official Internet Protocol Standards. RFC editor. Archived July 19, 2011, at the Wayback Machine.