RFCs

RFCs, or Request for Comments, are a long-running series of memoranda that document methods, behaviors, research, and innovations relevant to Internet technologies. Originating in the ARPANET era, RFCs cover a wide range of material, from formal Internet standards to experimental proposals and informational notes. The RFC series is the primary publication channel for the Internet Engineering Task Force (IETF) and related organizations.

Historically, the RFCs began in 1969 with RFC 1, authored by Steve Crocker and colleagues. In the early years the line between proposals, notes, and standards was blurred, but over time the IETF formalized a process to develop and publish technical specifications. Today, RFCs are used to document protocol specifications, architectural guidelines, best current practices, and historical records of the Internet’s development.

Publication and content structure follow a defined process. Work on a draft starts as an Internet-Draft within an IETF working group. After review and approval by the IETF’s governing bodies, the document is published as an RFC with a unique number. RFCs carry a status that indicates their role: Informational, Experimental, Best Current Practice (BCP), or Standards Track (which encompasses levels such as Proposed Standard and Internet Standard). The status helps readers understand the document’s normative influence and adoption level.

Access to RFCs is public. They are published by the RFC Editor and archived on the RFC Editor website as plain text and HTML, with copies also available through IETF and other library resources. Notable RFCs include RFC 791 (IPv4) and RFC 2616 (HTTP/1.1), the latter obsoleted by RFC 7230–7235, and RFC 6455 (WebSocket).

Overall, RFCs provide a centralized, enduring record of Internet protocols, practices, and decisions that shape interoperable networking worldwide.