RFC

RFC
Name	RFC
Caption	Request for Comments cover style
Developer	Internet Engineering Task Force; Internet Research Task Force; Internet Architecture Board
Released	1969
Latest release	ongoing
Platform	cross-platform

RFC is a long-standing series of technical and organizational documents that record the specifications, protocols, procedures, and policies associated with the development of the ARPANET, Internet, and related networking technologies. Originating in 1969, the series has served as a primary vehicle for disseminating engineering proposals among researchers, practitioners, and standards bodies such as the Internet Engineering Task Force and the Internet Architecture Board. The corpus includes both informal memos and formal standards, and its documents have influenced a wide range of protocols, from TCP/IP to SMTP.

History

The RFC series began as informal memos circulated among participants of the ARPANET project at the Stanford Research Institute and the U.S. Department of Defense research community. Early contributors included members of the Network Working Group led by figures associated with DARPA and the University of California, Los Angeles (UCLA) and Bolt Beranek and Newman (BBN). As the Internet expanded, stewardship shifted to the Internet Engineering Task Force and the Internet Society, with editorial oversight linked to the Internet Architecture Board. Historical milestones in the series reflect major events such as the formalization of TCP/IP and the transition from ARPANET to the modern Internet. Over decades the RFC series has preserved the evolution of technologies developed at institutions like MIT, Cornell University, and Berkeley.

Purpose and types

RFCs serve multiple purposes: proposing new protocols for internetworking, documenting operational experiences from organizations like CERN and National Aeronautics and Space Administration, specifying standards adopted by bodies such as the International Organization for Standardization and the European Telecommunications Standards Institute, and recording informational or experimental work from researchers at Bell Labs and Xerox PARC. The series includes categories such as Standards Track (including Proposed, Draft, and Internet Standards), Informational, Experimental, and Historic, with documents authored by individuals affiliated with institutions like Google, Microsoft, IBM, and Cisco Systems. Some RFCs function as Requests for Comments in the literal sense, inviting discussion from communities that include participants in IETF working groups, IAB panels, and academic conferences like the ACM SIGCOMM. Others have the status of formal standards recognized by governance entities such as the Internet Society.

Publication and editorial process

Publication begins when an author submits a draft to an IETF working group or an independent stream associated with organizations like the IAB or the IETF leadership. The document is reviewed through mechanisms involving working group chairs, area directors, and the IETF Administrative Support Activity, with editorial processing performed by the RFC Editor. Community review occurs via mailing lists tied to entities such as IETF working groups and venues like IETF Hackathons, and sometimes through public comment at conferences including IETF meetings and ICANN events. After technical consensus is reached, the document may advance through the Standards Track with oversight from bodies like the Internet Engineering Steering Group and final approval routes that have historically involved the Internet Architecture Board. The RFC Editor archives and assigns numbers, ensuring preservation and citation for institutions like Libraries and Archives Canada and university repositories.

Notable RFCs and impact

Several RFCs have become foundational to modern networking. The documents that specified TCP and IP underpinned the successful deployment of the Internet and influenced protocol development at organizations like Cisco Systems and Juniper Networks. Other RFCs established application-layer protocols such as HTTP and SMTP, enabling the growth of services offered by entities including Netscape, Microsoft, and Google. Security-related RFCs addressing TLS and IPsec have shaped practices at vendors like Intel and AMD and guided standards adopted by regulators such as the Federal Communications Commission. Informational RFCs recording operational incidents, authored by practitioners from institutions like ARIN and RIPE NCC, have affected best practices in network operations and resilience.

Adoption and standardization

Adoption pathways for RFCs vary: some become mandatory implementations within products developed by companies like Cisco Systems or required configurations in infrastructure operated by entities such as Amazon Web Services and Cloudflare. Other RFCs remain experimental or informational, influencing academic research at institutions like Stanford University and University of Cambridge or guiding hobbyist implementations by communities around projects like OpenBSD and Linux. Formal standardization for Standards Track RFCs often intersects with national and international standards organizations including the ISO and the ITU, and procurement policies in governments such as the United States or the European Union sometimes reference RFCs in technical requirements.

Criticism and controversies

The RFC process has faced critiques related to transparency, representation, and pace. Critics from activist groups and academic voices at places like Harvard University and University of Oxford have argued that influence skews toward large corporate actors such as Google and Microsoft, raising concerns echoed in debates at ICANN and IETF plenaries. Controversies have arisen when proposals touching on privacy, surveillance, or security intersect with policy agendas pursued by institutions like the National Security Agency or when contentious technical choices affected interoperability for vendors including Huawei and ZTE. Debates over mandatory standards, the treatment of experimental work, and archival practices have involved stakeholders ranging from IETF working group participants to lawmakers in bodies such as the U.S. Congress.

Category:Internet standards