PubIDPubID

IETF

Internet Engineering Task Force

The Internet Engineering Task Force (IETF) is the premier body for developing and promoting Internet standards. Organized as a large open international community of network designers, operators, vendors, and researchers, the IETF produces the Request for Comments (RFC) document series — the foundational specifications of the Internet, covering TCP/IP, DNS, TLS, HTTP, BGP, SMTP, and every other core Internet protocol. The IETF also maintains three sub-series overlays on top of RFCs: STD (Internet Standards — RFCs that have reached full standardization), BCP (Best Current Practices — RFCs documenting community-agreed practices), and FYI (For Your Information — RFCs providing introductory and explanatory material, now mostly historical).

IndustrySyntax 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. Website
5
Doc Types
4
Components
5
Relations
0
Stages

Components 4

Structured elements that make up a IETF identifier:

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

PubID Algebra 5

Relationships between IETF identifiers:

RelationDescriptionSyntaxExample
RFCStandard RFC citationRFC <number>RFC 2119
BCPBest Current PracticeBCP <number>BCP 3
STDInternet Standard (sub-series)STD <number>STD 66
FYIFor Your InformationFYI <number>FYI 1
Internet-DraftWork-in-progress draft, optional version suffix<draft-name>[-<version>]draft-giuliano-treedn-02