RFC

RFC. A Request for Comments is a formal document from the Internet Engineering Task Force and the broader Internet community that defines the specifications, protocols, procedures, and concepts for the Internet and many computer network systems. Initially conceived as a simple memorandum series during the early development of the ARPANET, the RFC series has evolved into the principal archival publication record for Internet standards, best practices, and experimental ideas. Managed through a structured process by the Internet Society and its affiliated bodies, these documents form the foundational technical and organizational literature of the global networked ecosystem.

Overview

The RFC series originated in 1969, with Steve Crocker authoring the very first document, RFC 1, while working on the Host-to-Host protocol for the ARPANET project funded by the Advanced Research Projects Agency. This informal beginning, characterized by its collaborative "request for comments" style, stood in contrast to the more rigid standards processes of traditional bodies like the International Organization for Standardization. The series is sequentially numbered and freely available, with archival and editorial functions historically managed by the RFC Editor, a role long held by the late Jon Postel at the University of Southern California's Information Sciences Institute. Today, the RFC Editor function is overseen by the RFC Series Approval Board and the Internet Architecture Board, ensuring the integrity and continuity of the publication stream, which encompasses everything from seminal protocol definitions to humorous April Fools' Day documents.

Development process

The development of an RFC follows a well-defined trajectory, typically beginning as an Internet-Draft submitted to the IETF Secretariat. These drafts are developed within specialized IETF working groups, such as those focused on IPv6, Transport Layer Security, or HTTP, where they undergo extensive peer review, testing, and community consensus-building. The process is governed by the principles outlined in RFC 2026, "The Internet Standards Process," and involves review by the responsible Area Director and the Internet Engineering Steering Group. For standards-track documents, the path progresses through proposed, draft, and finally Internet Standard status, as exemplified by protocols like TCP/IP defined in RFC 793 and RFC 791. The final publication decision rests with the RFC Series Editor and the independent RFC Production Center.

Types and categories

RFCs are categorized by their intended status and content, a classification system managed by the IETF Administration LLC. Standards Track RFCs, which include Proposed Standard, Draft Standard, and Internet Standard documents, specify core protocols like the Border Gateway Protocol in RFC 4271 and the Simple Mail Transfer Protocol in RFC 5321. Informational RFCs provide general descriptions or background, such as the Guide for Internet Standards Writers in RFC 2360. Experimental RFCs document research, while Best Current Practice documents, like those for DNS operations in RFC 2182, offer procedural guidance. A unique sub-category includes April Fools' Day RFCs, such as RFC 1149 on transmitting data via carrier pigeon, which are published humorously but still adhere to the series' formal structure.

Notable examples

Several RFCs have achieved landmark status for defining the fundamental architecture of the Internet. The core Internet Protocol suite was established by RFC 791 (IP) and RFC 793 (TCP), authored by pioneers like Vint Cerf and Bob Kahn. The Hypertext Transfer Protocol, foundational to the World Wide Web, was first specified in RFC 1945 by Tim Berners-Lee and others. Other critical documents include RFC 1034 and RFC 1035 for the Domain Name System, RFC 2068 for HTTP/1.1, and RFC 6749 for the OAuth 2.0 authorization framework. The humorous RFC 2324 famously defined the Hyper Text Coffee Pot Control Protocol, satirizing protocol extension efforts.

Impact and adoption

The RFC series has had a profound and global impact, providing the open, vendor-neutral technical specifications that underpin the interoperable Internet infrastructure. Its adoption is universal, with every Internet service provider, cloud computing platform like Amazon Web Services or Microsoft Azure, and operating system implementer relying on its standards. The process has influenced other standards bodies, including the World Wide Web Consortium and the Institute of Electrical and Electronics Engineers, and its model of open development is studied in contexts like open-source software movements. The series' longevity and authority, maintained through organizations like the Internet Society and the stewardship of figures such as Joyce K. Reynolds, cement its role as the definitive technical canon for networked communications.

Category:Internet standards Category:Internet architecture Category:Technical communication