Internet-Draft

Internet-Draft An Internet-Draft is a working document used within the Internet engineering and standards communities to propose, discuss, and refine technical specifications, protocols, and informational material. It functions as a temporary, public record of work in progress among standards bodies and engineering groups prior to formalization, and it intersects with many organizations, individuals, and events in the history of networking and standards. The document ties into a broad ecosystem that includes major institutions, standards processes, historic projects, and notable figures.

Overview

An Internet-Draft serves as a preliminary technical manuscript circulated among entities such as the Internet Engineering Task Force, Internet Architecture Board, Internet Society, World Wide Web Consortium, Institute of Electrical and Electronics Engineers, and European Telecommunications Standards Institute. It often references or draws on prior work from groups like ARPA, DARPA, Bell Labs, MIT, Stanford University, University of California, Berkeley, Xerox PARC, CERN, and Lawrence Berkeley National Laboratory. Authors commonly include engineers affiliated with companies and institutions such as Cisco Systems, Juniper Networks, Google, Microsoft, Apple Inc., Amazon (company), Facebook, Nokia, Ericsson, Huawei, Intel, IBM, HP Inc., Oracle Corporation, Red Hat, Cloudflare, Qualcomm, SAP SE, VMware, Siemens, NEC Corporation, Fujitsu, Samsung Electronics, Broadcom Inc., BlackBerry Limited, ZTE Corporation, T-Mobile, Verizon Communications, AT&T, Deutsche Telekom, Orange S.A., and NTT (Nippon Telegraph and Telephone).

Purpose and Role in Standards Development

Internet-Drafts enable collaborative iteration similar to processes used in landmark projects like TCP/IP, IPv4, IPv6, HTTP, SMTP, DNS, BGP, OSPF, MPLS, Ethernet, Wi‑Fi (802.11), and VoIP. They support coordination among working groups such as IETF Working Group on Routing, IETF Security Area, IETF Transport Area, IETF Applications and Real-Time (ART) Area, IETF Operations and Management Area, and influence formal outputs comparable to RFC 791, RFC 793, RFC 2616, RFC 1034, and RFC draft lineage. Contributing authors often cite foundational research and standards by figures and projects like Vint Cerf, Bob Kahn, Tim Berners-Lee, Jon Postel, David Clark, Paul Mockapetris, Steve Crocker, Van Jacobson, Radia Perlman, Leslie Lamport, Claude Shannon, and Donald Knuth as context.

Submission and Publication Process

Draft submission interacts with registration and archival systems maintained by organizations including the Internet Engineering Task Force Secretariat, Internet Assigned Numbers Authority, IETF Datatracker, and repositories used historically by RFC Editor. Authors submit material following templates and procedures influenced by editorial practices at Oxford University Press, ACM, IEEE, Springer, and institutional repositories at MIT Press or Cambridge University Press style guides. The review cycle often involves public discussion on mailing lists associated with groups like IETF Mail List, IETF Dispatch, IETF Meeting, IETF Plenary, and is presented at venues such as IETF Meeting, ICANN Public Meeting, RIPE Meeting, APNIC Conference, ARIN Public Policy Meeting, ISOC Summit, SIGCOMM, USENIX, ICSE, HotNets, NDSS, Black Hat USA, DEF CON, RSA Conference, and FCC Open Commission hearings when policy overlaps occur.

Lifespan, Revision, and Obsolescence

An Internet-Draft has a defined transient lifecycle and may be updated, replaced, or withdrawn in a sequence similar to versioned artifacts in projects like Git, Subversion, Mercurial, and CVS. It can be superseded by more mature documents through iterations akin to software release practices at Linux Kernel, FreeBSD, OpenBSD, NetBSD, Kubernetes, Docker, Apache HTTP Server, NGINX, PostgreSQL, MySQL, SQLite, Redis, MongoDB, and Hadoop. Timelines and deprecation patterns echo procedures from bodies like W3C TAG, IAB, IANA, ITU-T, 3GPP, GSMA, ETSI, and corporate standards processes at Intel Corporation and ARM Holdings. Historical obsolescence examples parallel transitions from technologies such as Telnet to SSH, FTP to SFTP, and legacy signaling like SS7 to modern IP signaling in SIP deployments.

Relationship to RFCs and IETF Working Groups

Internet-Drafts frequently act as precursors to formal publications such as Request for Comments, including historic milestones like RFC 791, RFC 793, RFC 2616, and contemporary standards overseen by the RFC Editor. They are often produced within IETF Working Groups, which are analogous to committees seen in organizations such as IEEE 802, IETF Applications Area Directors, IETF Transport Area Directors, IETF Routing Area Directors, IETF Security Area Directors, and coordinate with regional bodies like RIPE NCC, APNIC, LACNIC, and AfriNIC. Many drafts integrate contributions from collaborative efforts tied to projects and consortia such as OpenSSL, Let's Encrypt, OAuth, OpenID Foundation, W3C WebAssembly Working Group, Khronos Group, OpenStack Foundation, Cloud Native Computing Foundation, Linux Foundation, Apache Software Foundation, and Eclipse Foundation.

Legal and Copyright Considerations

Legal and copyright considerations surrounding drafts involve policies and agreements comparable to those at Creative Commons, WIPO, World Intellectual Property Organization, Berne Convention, United States Copyright Office, European Patent Office, US Patent and Trademark Office, General Data Protection Regulation, Digital Millennium Copyright Act, Anticybersquatting Consumer Protection Act, Communications Assistance for Law Enforcement Act, Export Administration Regulations, and institutional IP offices at Harvard University, Stanford University, MIT, UC Berkeley, Cambridge University, University of Oxford, Columbia University, and Yale University. Contributors must be mindful of employment-related policies from employers such as Google LLC, Microsoft Corporation, IBM Corporation, Facebook, Inc., Amazon.com, Inc., Apple Inc. and the negotiation patterns seen in standard-essential patent discussions involving entities like Nokia, Qualcomm, Ericsson, Samsung, Huawei, NEC, InterDigital, Siemens, Philips, Sony Corporation, and LG Electronics. Drafts also intersect with compliance regimes and licensing models exemplified by BSD license, MIT License, GNU General Public License, Apache License, Creative Commons Attribution, and proprietary agreements used by corporations and consortia.

Category:Internet standards documents