Request For Comment

RFC文件格式最初作为ARPA网计划的基础起源于1969年。如今，它已经成为IETF、Internet Architecture Board (IAB)还有其他一些主要的公共网络研究社区的正式出版物发布途径。
第一份RFC文档由洛杉矶加利福尼亚大学（UCLA）的Steve Crocker撰写，在1969年4月7日公开发表的RFC 1。当初Crocker为了避免打扰他的室友，是在浴室里完成这篇文档的。
RFC文件只有新增，不會有取消或中途停止發行的情形。但是對於同一主題而言，新的RFC文件可以聲明取代舊的RFC文件。RFC文件是純ASCII文字檔格式，可由電腦程式自動轉檔成其他檔案格式。RFC文件有封面、目錄及頁首頁尾和頁碼。RFC的章節是數字標示，但數字的小數點後不補零，例如4.9的順序就在4.10前面，但9的前面並不補零。RFC1000這份文件就是RFC的指南。

子类型

BCP	Best Current Practice; mandatory IETF RFCs not on standards track.
FYI	For Your Information; informational RFCs promoted by the IETF as specified in RFC 1150 (FYI 1). In 2011 RFC 6360 obsoleted FYI 1 and concluded this sub-series.
STD	Standard; this used to be the third and highest maturity level of the IETF standards track specified in RFC 2026 (BCP 9). In 2011 RFC 6410 (a new part of BCP 9) reduced the standards track to two maturity levels.

状态

INFORMATIONAL	An informational RFC can be nearly anything from April 1 jokes over proprietary protocols up to widely recognized essential RFCs like Domain Name System Structure and Delegation (RFC 1591).
EXPERIMENTAL	An experimental RFC can be an IETF document or an individual submission to the 'RFC Editor'.
BEST CURRENT PRACTICE	The best current practice (BCP) subseries collects administrative documents and other texts which are considered as official rules and not only informational, but which do not affect over the wire data.
HISTORIC	A historic RFC is one that has been made obsolete by a newer version, documents a protocol that is not considered interesting in the current Internet, or has been removed from the standards track for other reasons.
UNKNOWN	Status unknown is used for some very old RFCs, where it is unclear which status the document would get if it were published today.

RFC目录

http://www.ietf.org/download/rfc-index.txt

恶搞RFC

http://zh.wikipedia.org/wiki/%E6%83%A1%E6%90%9ERFC

RFC之道

https://www.ietf.org/tao.html

参考资料

[1]. http://zh.wikipedia.org/wiki/RFC
[2]. http://en.wikipedia.org/wiki/Request_for_Comments