Internet-Draft

Industrydraft

Description

Work-in-progress documents being developed within IETF Working Groups (or by individual submitters). Internet-Drafts are NOT RFCs and are NOT official specifications — they exist for review and revision. Draft names follow the form 'draft-<author>-<workgroup>-<topic>-<version>' where the version is a two-digit suffix. Drafts automatically expire after 6 months unless renewed. A draft's name is unique for the document's lifetime; only the version suffix changes between revisions.

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

draft-giuliano-treedn-02

draft-giuliano-treedn

draft-ietf-httpbis-cache-digest-04

Components Used

IETF Internet-Draft 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-Draft 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]