Internet standard
Encyclopedia
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).
(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.
The Internet Standards Process is defined in several "Best Current Practice" documents, notably BCP 9 ( 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.
can reclassify an old Draft Standard as Proposed Standard after two years (October 2013).
Generally Internet Standards cover interoperability of systems on the Internet through defining protocols, messages formats, schemas, and languages. The most fundamental of the Internet Standards are the ones defining the Internet Protocol
.
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 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.
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.
Computer network
A computer network, often simply referred to as a network, is a collection of hardware components and computers interconnected by communication channels that allow sharing of resources and information....
engineering
Engineering
Engineering is the discipline, art, skill and profession of acquiring and applying scientific, mathematical, economic, social, and practical knowledge, in order to design and build structures, machines, devices, systems, materials and processes that safely realize improvements to the lives of...
, an Internet Standard (STD) is a normative specification of a technology or methodology applicable to the Internet
Internet
The Internet is a global system of interconnected computer networks that use the standard Internet protocol suite to serve billions of users worldwide...
. Internet Standards are created and published by the Internet Engineering Task Force
Internet Engineering Task Force
The Internet Engineering Task Force develops and promotes Internet standards, cooperating closely with the W3C and ISO/IEC standards bodies and dealing in particular with standards of the TCP/IP and Internet protocol suite...
(IETF).
Overview
An Internet Standard is a special Request for CommentsRequest for Comments
In computer network engineering, a Request for Comments is a memorandum published by the Internet Engineering Task Force describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems.Through the Internet Society, engineers and...
(RFC) or set of RFCs. An RFC that is to become a Standard or part of a Standard begins as an Internet Draft
Internet Draft
Internet Drafts is a series of working documents published by the IETF. Typically, they are drafts for RFCs, but may be other works in progress not intended for publication as RFCs. It is considered inappropriate to rely on Internet Drafts for reference purposes...
, 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
Internet Engineering Task Force
The Internet Engineering Task Force develops and promotes Internet standards, cooperating closely with the W3C and ISO/IEC standards bodies and dealing in particular with standards of the TCP/IP and Internet protocol suite...
, represented by the Internet Engineering Steering Group
Internet Engineering Steering Group
The Internet Engineering Steering Group is a body composed of the Internet Engineering Task Force chair and area directors.It provides the final technical review of Internet standards and is responsible for day-to-day management of the IETF...
(IESG), can approve Standards Track RFCs. The definitive list of Internet Standards is maintained in Internet Standards document STD 1: Internet Official Protocol Standards.
Standardization process
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 ( 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.
Proposed Standard
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.Draft 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 IESGInternet Engineering Steering Group
The Internet Engineering Steering Group is a body composed of the Internet Engineering Task Force chair and area directors.It provides the final technical review of Internet standards and is responsible for day-to-day management of the IETF...
can reclassify an old Draft Standard as Proposed Standard after two years (October 2013).
Internet Standard
A specification for which at least two independent and interoperable implementations and successful operational experience has been obtained may be elevated to the Internet Standard level. 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, messages formats, schemas, and languages. The most fundamental of the Internet Standards are the ones defining the Internet Protocol
Internet Protocol
The Internet Protocol is the principal communications protocol used for relaying datagrams across an internetwork using the Internet Protocol Suite...
.
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 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.
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
Mail submission agent
A mail submission agent is a computer program or software agent that receives electronic mail messages from a mail user agent and cooperates with a mail transfer agent for delivery of the mail...
) published in 2011.
External links
- http://www.apps.ietf.org/rfc/stdlist.htmlList of Full Standard RFCRequest for CommentsIn computer network engineering, a Request for Comments is a memorandum published by the Internet Engineering Task Force describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems.Through the Internet Society, engineers and...
s] - Internet Architecture Board
- Internet Engineering Steering Group
- Internet Engineering Task Force
- RFC Editor