什么是RFC？

In several blog posts I mention “this technology is defined in RFC xxxx”, or “see RFC yyyy for the nitty gritty details”.

在几篇博客文章中，我提到“此技术是在RFC xxxx中定义的”，或“请参阅RFC yyyy以获取详细的详细信息”。

What is an RFC?

什么是RFC？

RFC stands for Request for Comments. You might have RFC in various environments now, but traditionally what we mean with RFC on the Internet is a publication that’s written by engineers and computer scientists, aimed at other professionals that work in the Internet sphere.

RFC代表“ 征求意见” 。 您现在可能已经在各种环境中使用了RFC，但是传统上，在Internet上使用RFC的意思是由工程师和计算机科学家编写的出版物，主要针对在Internet领域工作的其他专业人员。

RFCs have a long history, starting back in 1969 in ARPANET times. The Internet was created in this way, with RFCs being starting point of discussion, or protocol implementation details that people used to implement the actual software.

RFC的悠久历史可以追溯到1969年的ARPANET时代。 互联网是以这种方式创建的，以RFC为讨论的起点，或者人们用来实现实际软件的协议实现细节。

The name, Request for Comments, encouraged a community discussion around those papers, that originally circulated in printed form.

“征求意见”这个名称鼓励社区围绕最初以印刷形式分发的这些文件进行讨论。

RFCs today, before being added as official RFCs, go through various steps, that might take many months or years of discussions. This is because an RFC today, once published, cannot be changed any more. The entire process is managed by IETF, the Internet Engineering Task Force.

今天的RFC，在被添加为正式RFC之前，经历了许多步骤，可能需要花费数月或数年的讨论。 这是因为今天的RFC一旦发布，就无法再更改。 整个过程由IETF( 互联网工程任务组)进行管理 。

Revisions to RFC documents need to be published as independent RFCs, and older RFCs are marked as superseded by those newer revisions. Other RFC supplement what older RFC specify.

RFC文档的修订需要作为独立的RFC发布，而较旧的RFC则被这些较新的修订所标记。 其他RFC补充了旧RFC所指定的内容。

For example, RFC 1349 from 1992, titled “Type of Service in the Internet Protocol Suite”, was obsoleted by RFC 2474 in 1998, titled “Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers”.

例如，1992年的RFC 1349(标题为“ Internet协议套件中的服务类型 ”)被RFC 2474(1998年，标题为“ IPv4和IPv6标头中的区分服务字段(DS字段)的定义 ”)淘汰了。

Here are some very famous RFC documents that are very well worth the read. Those are things that will be relevant for a long time (I myself printed some of them back in high school like 20 years ago, and I still have those), and are the foundation of the Internet:

这里有一些非常著名的RFC文档，非常值得阅读。 这些是很长一段时间都有意义的东西(我自己像20年前一样在高中时就印了其中一些，现在我仍然有)，它们是Internet的基础：

• RFC 791: IP

  RFC 791：IP

• RFC 793: TCP

  RFC 793：TCP

• RFC 1034: DNS

  RFC 1034：DNS

• RFC 4291: IPv6

  RFC 4291：IPv6

• RFC 6749: OAuth 2.0

  RFC 6749：OAuth 2.0

Some other RFCs are less technical, like RFC 1855 Netiquette Guidelines, and some others are just funny jokes by engineers for engineers, like RFC 2324, the Hyper Text Coffee Pot Control Protocol.

其他一些RFC的技术性较差，例如RFC 1855网络礼仪指南 ，而其他一些只是工程师的工程师的笑话，例如RFC 2324 ( 超文本咖啡壶控制协议) 。

So, in conclusion: RFCs are technical documents that, after going through a rigorous process of discussion and technical verification are added to the list of official protocols recognized by the IETF, and being a standard they can then be implemented by software vendors.

因此，总而言之：RFC是技术文档，经过严格的讨论和技术验证之后，这些文档被添加到IETF认可的官方协议列表中，并且作为标准，可以由软件供应商实施。

翻译自: https://flaviocopes.com/rfc/