A document that has been formally adopted as an Internet Standard. These are technical specifications that describe stable, well-understood, and widely implemented protocols essential for the internet’s functioning. An STD is essentially the highest level of maturity in the IETF standards process.
The path to becoming an STD is rigorous. Protocols typically begin as Internet-Drafts and then progress to publication as a Request for Comments (RFC). From there, an RFC may be elevated through maturity levels:
- Proposed Standard: The entry-level maturity stage for a specification. At this point, the protocol is considered stable and is believed to provide significant technical value; however, it may not have been widely implemented yet.
- Draft Standard: A more mature stage that requires multiple independent, interoperable implementations of the protocol. This ensures the specification works consistently across different systems and environments.
- Internet Standard: The highest level of maturity. A protocol at this stage is thoroughly tested, widely adopted, and considered essential for the reliable and interoperable operation of the internet. It is then assigned an STD number in addition to its RFC reference.
A well-known example is the Transmission Control Protocol (TCP), which is documented in RFC 793 but also assigned the identifier STD 7. This dual reference helps distinguish between the archival RFC series and the formal set of standards that define the core Internet.
The purpose of the STD series is to provide implementers, network operators, and developers with a clear, authoritative list of protocols that must be supported for consistent, interoperable internet communication. Unlike Best Current Practices (BCPs), which offer guidance and policies, STDs represent fixed, technical rules that ensure global compatibility.
Related Martech Zone Content
