Internet Standard (STD)

IndustrySTD

Description

The Internet Standard sub-series — RFCs that have completed the full IETF standardization process and are designated as official Internet Standards. STD numbers are stable across revisions: when an STD RFC is updated, the STD number is retained while the underlying RFC number may change. For example, STD 66 (the URI Generic Syntax) has been revised multiple times across RFC 3986, RFC 6874, etc.

Syntax

IETF identifiers come in 5 shapes: RFC '<number>', BCP '<number>', STD '<number>', FYI '<number>', and Internet-Draft '<draft-name>-<version>'. Internet-Drafts are work-in-progress documents with a name like 'draft-giuliano-treedn' and an optional two-digit version suffix. RFCs/BCPs/STDs/FYIs share the same numbering space conceptually but each has its own sub-series index.

Examples 3

STD 66

STD 1

STD 80

Components Used

IETF Internet Standard (STD) identifiers are composed of these elements:

Series

Series prefix: RFC, BCP, STD, FYI (or nil for Internet-Drafts)

e.g.RFC

:series

Number

Sequence number within the sub-series (RFC, BCP, STD, FYI)

e.g.2119

:number

Draft Name

Internet-Draft name (e.g. 'draft-giuliano-treedn'), without version suffix

:name

Version

Internet-Draft two-digit version suffix (e.g. '02'), nil when absent

:version

Algebraic Relations

Relations that can involve Internet Standard (STD) identifiers:

Relation	Description	Syntax	Example
RFC	Standard RFC citation	`RFC <number>`	`RFC 2119`
BCP	Best Current Practice	`BCP <number>`	`BCP 3`
STD	Internet Standard (sub-series)	`STD <number>`	`STD 66`
FYI	For Your Information	`FYI <number>`	`FYI 1`
Internet-Draft	Work-in-progress draft, optional version suffix	`<draft-name>[-<version>]`	`draft-giuliano-treedn-02`

URN Mapping

Patternurn:ietf:[series]:[number]