RFC (Request for Comments) is a publication of the technical community
In several blog posts, I mentioned "this technology is defined in RFC xxxx", or "please refer to RFC yyyy for detailed details".
What is RFC?
RFC representativesolicit opinions. You may have used RFCs in various environments now, but traditionally, using RFCs on the Internet means publications written by engineers and computer scientists, aimed at other professionals working in the Internet field.
RFC has a long history, dating back to the ARPANET era in 1969. The Internet was created in this way, with the RFC as the starting point for discussion, or the implementation details of the protocol that people use to implement actual software.
The name "Request for Comments" encourages community discussions around these documents, which were originally distributed in printed form.
Today's RFC has gone through many steps before being added as an official RFC, and it may take months or years of discussion. This is because once today's RFC is published, it cannot be changed. The whole process is managed by IETF,Internet Engineering Task Force.
Revisions to RFC documents need to be published as independent RFCs, and older RFCs are marked as being replaced by these newer revisions. Other RFCs supplement the content specified by earlier RFCs.
For example, RFC 1349 in 1992, titled "Types of services in the Internet protocol suite", was eliminated by RFC 2474 in 1998, with the title "Definition of Differentiated Services Field (DS Field) in IPv4 and IPv6 Headers".
Here are some very famous RFC documents, which are worth reading. These are things that have been meaningful for a long time (I myself printed some of them in high school like 20 years ago, and I still have them), and they are the foundation of the Internet:
Some other RFCs are less technical, such asRFC 1855 Network Etiquette Guide, And there are some funny jokes just made by engineers to engineers, such asRFC 2324, ThisHypertext Coffee Pot Control Protocol.
Therefore, in a nutshell: RFCs are technical documents. After rigorous discussion and technical verification, these documents are added to the list of official protocols recognized by the IETF, and as a standard, they can be implemented by software vendors.
More web tutorials:
- Introduction to WebSockets
- How HTTP requests work
- List of HTTP request headers
- List of HTTP response headers
- HTTP and HTTPS
- What is RFC?
- HTTP protocol
- HTTPS protocol
- The curl guide for HTTP requests
- HTTP cache
- List of HTTP status codes
- What is CDN?
- HTTP/2 protocol
- What is the port
- DNS, Domain Name System
- TCP protocol
- UDP protocol
- Introduction to REST API
- How to install a local SSL certificate in macOS
- How to generate a local SSL certificate
- How to configure Nginx for HTTPS
- A simple Nginx reverse proxy for serving multiple Node.js applications from subfolders
- What is a reverse proxy?