In computer network engineering, an Internet Standard (abbreviated as "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 a special Request for Comments (RFC) or 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 a RFC and labeled a Proposed Standard. Later, an RFC can be labeled Internet Standard. 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.1
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 Standard. RFC 6410 reduced this to two maturity levels.
A Proposed Standard (PS) is generally stable, has resolved known design choices, is believed to be well-understood, has received significant community review, and appears to enjoy enough community interest to be considered valuable. However, further experience might result in a change or even retraction of the specification before it advances. Usually, neither implementation nor operational experience is required.
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.
All Internet Standards are given a number in the STD series - The first document in this series, STD 1, describes the remaining documents in the series, and has a list of Proposed Standards.
Each RFC is static; if the document is changed, it is submitted again and assigned a new RFC number. If 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 stays the same and it simply refers to a different RFC or set of RFCs. A given Internet Standard, STD n, may be RFCs x and y at a given time, but later the same standard may be updated to be RFC z instead. For example, in 2007 RFC 3700 was an Internet Standard—STD 1—and in May 2008 it was replaced with RFC 5000, so RFC 3700 changed to Historic status, and now[update] STD 1 is RFC 5000. When STD 1 is updated again, it will simply refer to a newer RFC, but it will still be STD 1. Note that not all RFCs are standards-track documents, but all Internet Standards and other standards-track documents are RFCs.</ref>
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.2
|Standard Type||Associated Protocols|
|IMAP, POP, X.400, SMTP, CMC, MIME, binhex, uuencode|
|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|
Content from Wikipedia, the Free Encyclopedia
What Is This Site? The Ultimate Study Guide is a mirror of English Wikipedia. It exists in order to provide Wikipedia content to those who are unable to access the main Wikipedia site due to draconian government, employer, or school restrictions. The site displays all the text content from Wikipedia. Our sponsors generously cover part of the cost of hosting this site, and their ads are shown as part of this agreement. We regret that we are unable to display certain controversial images on some pages the site at the request of the sponsors. If you need to see images which we are unable to show, we encourage you to view Wikipedia directly if possible, and apologize for this inconvenience.
A product of XPR Content Systems. 47 Union St #9K, Grand Falls-Windsor NL A2A 2C9 CANADA