Internet standard Page

Internet Standard

Return to Internet standards (IETF standards), Web standards (W3C standards), Networking standards, Programming standards (ISO Programming standards) - Software engineering standards, Computer standards, Open Standards

{{wp>Internet standards}}

Short description - a standard published by the Internet Engineering Task Force

In computer network engineering, an Internet Standard 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).

Engineering contributions to the IETF start as an Internet Draft, may be promoted to a Request for Comments, and may eventually become an Internet Standard.

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 classification that was discontinued in 2011. A Draft Standard was an intermediary step that occurred after a Proposed Standard but prior to an Internet Standard.

As put in RFC>2026 | RFC 2026: "In general, an Internet Standard is a specification that is stable and well-understood, is technically competent, has multiple, independent, and interoperable implementations with substantial operational experience, enjoys significant public support, and is recognizably useful in some or all parts of the Internet."

Overview

An Internet Standard is documented by ((Huitema, C., Postel J., Crocker S., Date: 1995, Title: g>Not All RFCs are Standards, https://www.rfc-editor.org/info/rfc1796, RFC>1796 | RFC 1796, ISSN: 2070-1721)) a Request for Comments (RFC) or a set of RFCs. A specification 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 wp>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 | RFC 2026 and RFC>6410 | 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 Administrative Support Activity|IETF, represented by the Internet Engineering Steering Group (IESG), can approve Standards Track RFCs. The definitive list of Internet Standards is maintained in the [http://www.rfc-editor.org/standards Official Internet Protocol Standards]. Previously, STD 1 used to maintain a snapshot of the list.((RFC>7100 | RFC 7100 Retirement of the "Internet Official Protocol Standards" Summary Document))

Standardization process

Becoming a standard is a two-step process within the Internet Standards Process: Proposed Standard and Internet Standard. These are called maturity levels and the process is called the Standards Track.

If an RFC is part of a proposal that is on the Standards 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 | 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 [http://tools.ietf.org/html/bcp9 BCP 9] ({{As of|2011|alt=currently}} RFC>2026 | RFC 2026 and [[RFC>6410 | RFC 6410). There were previously three standard maturity levels: Proposed Standard, Draft Standard and Internet Standard. RFC 6410 reduced this to two maturity levels.

=Proposed Standard

=
RFC 2026 originally characterized Proposed Standards as immature specifications, but this stance was annulled by RFC>7127 | RFC 7127.{{cite IETF |title=Characterization of Proposed Standards |rfc=7127 |sectionname=Characterization of Specifications |section=3 |date=January 2014 |publisher=Internet Engineering Task Force|IETF |accessdate=March 11, 2016}}

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.{{cite IETF |title=Characterization of Proposed Standards |rfc=7127 |sectionname=IETF Review of Proposed Standards |section=2 |date=January 2014 |publisher=Internet Engineering Task Force|IETF |accessdate=March 11, 2016}}

=Draft Standard

=
In October 2011, RFC>6410 | RFC 6410 merged the second and third maturity levels into one Draft Standard. Existing older Draft Standards retain that classification. The Internet Engineering Steering Group|IESG can reclassify an old Draft Standard as Proposed Standard after two years (October 2013).

=Internet Standard

=
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.

All Internet Standards are given a number in the STD series. The series was summarized in its first document, STD 1 (RFC>5000 | RFC 5000]]), until 2013, but this practice was retired in RFC>7100 | RFC 7100. The definitive list of Internet Standards is now maintained by the RFC Editor.{{cite web |url=http://www.rfc-editor.org/standards |title=Official Internet Protocol Standards}}

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 | RFC 3700 was an Internet Standard (STD 1) and in May 2008 it was replaced with RFC>5000 | RFC 5000. RFC 3700 received Historic status, and RFC 5000 became STD 1.

The list of Internet standards was originally published as STD 1 but this practice has been abandoned in favor of an online list maintained by the RFC Editor.{{IETF RFC|7100}}

External links

* [http://www.rfc-editor.org/ RFC Editor]

Research It More

Research:
* ddg>Internet Standards on DuckDuckGo
* oreilly>Internet Standards on O'Reilly
* github>Internet Standards on GitHub
* reddit>Internet Standards on Reddit
* stackoverflow>Internet Standards on StackOverflow
* youtube>Internet Standards on YouTube

Fair Use Sources

Fair Use Sources:
* ddg>Internet Standards on DuckDuckGo

{{navbar_networking}}

{{navbar_iso}}

{{navbar_footer}}