[Home]   [TOC]

Request For Comment
IETF, Organization, RFC
Updated Feb 25, 2015 by jht5...@gmail.com

Request For Comment

RFC文件格式最初作为ARPA网计划的基础起源于1969年。如今,它已经成为IETF、Internet Architecture Board (IAB)还有其他一些主要的公共网络研究社区的正式出版物发布途径。
第一份RFC文档由洛杉矶加利福尼亚大学(UCLA)的Steve Crocker撰写,在1969年4月7日公开发表的RFC 1。当初Crocker为了避免打扰他的室友,是在浴室里完成这篇文档的。


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.








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