IETF Internet Drafts

IETF Internet Drafts
Name	IETF Internet Drafts
Type	Technical specification drafts
Owner	Internet Engineering Task Force
Started	1990s

IETF Internet Drafts IETF Internet Drafts are working documents produced within the Internet Engineering Task Force and related bodies to propose, document, and refine technical specifications for Internet protocols and practices. They serve as transient artifacts that inform discussion among participants from organizations such as the Internet Society, the World Wide Web Consortium, and regional registries, while interacting with standards processes overseen by bodies like the Internet Architecture Board and national institutions. Drafts influence formalization into RFCs and engage communities represented by working groups, vendors, and academic institutions.

Overview

Internet Drafts originate in venues such as IETF working groups, the Internet Research Task Force, and individual contributors tied to companies like Cisco Systems, Juniper Networks, and Google. The lifecycle of a draft intersects with governance and oversight by entities including the Internet Society, the Internet Architecture Board, the Federal Networking Council, and the US National Institute of Standards and Technology when security or interoperability concerns arise. Draft texts often reference prior work from standards-setting organizations like the World Wide Web Consortium and liaise with operational bodies such as the American Registry for Internet Numbers and regional Internet registries. Notable participants include engineers affiliated with institutions such as MIT, Stanford University, and University College London.

Purpose and Role in Standards Development

Internet Drafts function as provisional proposals that feed into the standards track culminating in RFC publication under the stewardship of the RFC Editor and the Internet Engineering Steering Group. They enable iterative refinement by contributors from companies like Microsoft, Apple, and Amazon and by researchers from organizations including the European Telecommunications Standards Institute and the Institute of Electrical and Electronics Engineers. Drafts provide a mechanism for interoperability testing among vendors such as Nokia and Ericsson and for harmonization with policies shaped by bodies like the Internet Corporation for Assigned Names and Numbers and the IANA. Through community review at meetings such as the IETF plenary and IETF hackathons, drafts help shape documents that may later be advanced to Proposed Standard, Draft Standard, and Internet Standard levels.

Draft Lifecycle and Publication Process

A draft typically begins as an individual submission or a working group document, moves through revisions, and is published in the IETF datatracker and archive managed alongside RFC Editor processes. The procedural path involves chairs, area directors, and the IESG, with interactions involving the IAB and occasionally external review by organizations such as the National Institute of Standards and Technology or the European Commission. Meetings at venues like IETF London, IETF Berlin, and IETF Prague provide forums for adoption decisions, while mailing list debates hosted on platforms maintained by institutions such as the Internet Society inform versioning. The datatracker and archive preserve identifiers and metadata until a draft expires or is superseded.

Authorship, Sponsorship, and IETF Stream Types

Authorship can be individual or organizational, with sponsorship by working groups, the IESG, or external organizations. Contributors often hail from entities like Oracle, IBM, Facebook, and academic centers such as Carnegie Mellon University and the University of California, Berkeley. The IETF recognizes multiple submission streams—working group, individual, and IRTF—that reflect provenance and editorial context, and documents may also emerge from liaison relationships with ETSI, 3GPP, or the ITU. Editor roles and authorship declarations document affiliations with corporations, consortia, and research institutes, and conflicts of interest are managed through processes involving the IETF Secretariat and the Internet Society.

Document Formats, Identifiers, and Versioning

Drafts are published in text and XML formats compatible with tools used by the RFC Editor and the IETF datatracker; metadata follows conventions paralleling those in RFCs and is indexed for search by archives such as the IETF Mail Archive. Each draft carries a structured name and version identifier that signals authorship and revision history, enabling tracking across repositories and interactions with registries like IANA. Versioning practices reflect contributions from software firms such as Red Hat and Canonical when implementations are developed, and test vectors and interoperability reports often accompany drafts from testbed projects at institutions like the National Institute of Standards and Technology or university laboratories.

Obsolescence, Replacement, and RFC Transition

Drafts expire after a defined interval unless updated, and they may be obsoleted by newer drafts or advanced into RFCs through editorial processes overseen by the IESG and the RFC Editor. Transition to RFC status may follow review cycles that include security assessments by groups linked to NIST or coordination with the Internet Architecture Board; once published as RFCs, documents are cited by standards-track references and by operational documents maintained by organizations such as the Internet Assigned Numbers Authority. Vendors and service providers including Akamai and Cloudflare track obsolescence to maintain interoperability, and historical threads link drafts to legacy RFCs and earlier standards work performed at institutions like Bell Labs.

Criticisms, Limitations, and Practical Use

Critiques of the draft system address transient discoverability, varying editorial quality, and potential for fragmentation when multiple competing drafts exist, concerns echoed in exchanges involving corporate participants such as Huawei and academic critics from institutions like Yale University. Practical use often depends on implementation experience from vendors like VMware and testing in environments coordinated by research networks such as Internet2 and GÉANT. Remedies have involved process refinements by the IETF community, input from oversight bodies like the Internet Architecture Board, and tooling improvements contributed by open source projects maintained by communities on platforms associated with the Apache Software Foundation and the Linux Foundation.

Category:Internet standards