Sign in Subscribe

RFC Request For Comment

Last updated on 

RFC stands for Request for Comments. It is a publication series used for developing and discussing Internet standards and protocols. The RFC process was initially established by Steve Crocker in 1969 to document the development of ARPANET, the precursor to the modern Internet.

The primary purpose of RFCs is to foster open discussions and allow input from the wider Internet community, including researchers, engineers, and developers, to refine and improve the standards and protocols that govern the functioning of the Internet.

Here's a detailed explanation of the RFC process:

  1. RFC Creation: The process begins when an individual or a group drafts a document that proposes a new standard, describes a protocol, or discusses an issue related to the Internet. This document is referred to as an "RFC draft."
  2. Submission: The RFC draft is submitted to the RFC Editor, who acts as the central point of contact for the RFC process. The RFC Editor assigns a unique number to the draft and performs an initial review to ensure it meets the basic formatting and editorial requirements.
  3. Initial Review: Once the draft passes the basic requirements, it undergoes a technical review by experts in the specific field or working group related to the subject matter. These experts provide feedback, suggestions, and improvements to the draft. The review process is usually conducted on a voluntary basis by members of the Internet Engineering Task Force (IETF), the organization responsible for developing and promoting Internet standards.
  4. Iterative Development: The draft author(s) incorporate the feedback received during the review process and revise the document accordingly. The revised draft is then resubmitted to the RFC Editor for further processing.
  5. Publication and Distribution: Once the draft reaches a stable and mature state, it is published as an RFC. The RFC Editor assigns an official RFC number to the document, and it is made available to the public. RFCs are freely accessible on the Internet and can be downloaded from various repositories, such as the RFC Editor's website or the IETF website.
  6. Community Review: After publication, the RFC enters a stage of wider community review. Engineers, researchers, and anyone interested can provide feedback, comments, or suggestions on the RFC. This feedback is essential for identifying potential issues, clarifying ambiguities, and improving the proposed standard or protocol.
  7. Implementation and Adoption: RFCs serve as a basis for implementing and deploying Internet protocols and standards. Vendors, developers, and organizations reference RFCs when creating software, networking equipment, and other Internet-related technologies. The wider adoption of an RFC indicates its acceptance as an industry standard.
  8. Iterative Updates: As technology evolves, new requirements emerge, or flaws are discovered, existing RFCs may need to be updated or replaced. The RFC process allows for iterative updates, revisions, or the creation of new RFCs to address these changes. This ensures that Internet standards remain relevant, efficient, and secure over time.

It's important to note that not all RFCs become Internet standards. Some RFCs document experimental protocols, informational documents, or best practices. The RFC process itself is an open and collaborative mechanism that encourages community involvement and fosters the evolution of the Internet.