A Request for Comments (RFC) is a formally numbered document in a series used to define, describe and discuss internet technologies, protocols, procedures and conventions. Originating with the early ARPANET community and now stewarded primarily through the IETF, RFCs range from formal standards to informational and experimental memos. The series provides a durable, citable record of how core internet infrastructure is specified and evolved.
Overview
- RFCs began as informal memos circulated among ARPANET researchers and became the canonical publication series for internet standards.
- Despite the historical name, many RFCs are settled standards rather than open solicitations for comment.
- Each RFC has a unique, permanent number and a defined status (standards track, informational, experimental, historic).
Key aspects
- Stable numbering and archival so documents remain citable indefinitely.
- Status categories distinguishing normative standards from informational notes.
- An open editorial and review process coordinated through the IETF and RFC Editor.
- Cross-referencing, with newer RFCs updating or obsoleting earlier ones.
Applications
- Defining foundational protocols such as IP, TCP, HTTP and DNS.
- Recording best-practice operational guidance for network operators.
- Providing the normative basis for reference implementations and test suites.
- Documenting experimental ideas before they mature into standards.
Provenance
- This class was materialised to resolve existing inbound references in the knowledge graph.