阅读原版RFC

RFC文档的形成

在1992年成立的 ISOC 组织（Internet Society, 国际互联网协会）下属的 IAB 团体负责定义整个互联网的架构和长期发展规划，该团体下属的 IESG 小组负责创建 IETF 工作组并为其分配特定的主题。IETF 的工作结果通常会形成 RFC 文档。

大多数 RFC 文档描述的网络协议、服务或者策略可能演变为一种互联网标准。RFC 按顺序依次编号，一个号码一旦被指定后将永远不重复使用。RFC 可能会更新或辅之以较高编号的 RFC。

一、RFC自身

  • [RFC 2119] 在RFC中用于指示需求级别的关键字

二、通用基础

  • [RFC 2822] 互联网消息格式
  • [RFC 3339] 互联网上的日期和时间：时间戳

三、网络协议

IEEE 802 委员会研究的标准只针对 PHY 和 DLL 两层。

1、物理层 - Physical Layer, PHY

FE自协商

Manchester

MLT-3

4A

PAM5

2、数据链路层 - Data Link Layer, DLL

ARP

  • [RFC 826]

RARP

  • [RFC 903]

IEEE802.x

PPP

  • [RFC 1661]

PPP-MP

  • [RFC 1717]

CSMA/CD

3、网络层

IP

  • [RFC 791]
  • [RFC 1918] 专用互联网的地址分配

BOOTP

  • [RFC 951]

DHCP

  • [RFC 1541]

ICMP

RIP

IGMP

IGMPv2

  • [RFC 2236]

4、传输层

OSPFv2

  • [RFC 1583]

SNMP (MIB-II)

  • [RFC 1157]
  • [RFC 1213]

TCP

  • [RFC 793]

UDP

  • [RFC 768]

5、应用层

NetBIOS

  • [RFC 1001]
  • [RFC 1002]

BGPv4

  • [RFC 1771]

Telnet

  • [RFC 854]
  • [RFC 855]

FTP

  • [RFC 959]

TFTP

  • [RFC 1350]

DNS

  • [RFC 1034]
  • [RFC 1035]
  • [RFC 1912] 常见的DNS操作和配置错误

SMTP

  • [RFC 821]

POP3

  • [RFC 1939]

HTTP 1.0

  • [RFC 1945]

HTTP 1.1

  • [RFC 2616]
  • [RFC 2617]
  • [RFC 7231] 超文本传输协议（HTTP/1.1）：语义和内容

HTML 2.0

  • [RFC 1866]

MIME

  • [RFC 1341]

CoAP

Number Title Date More Info Status
RFC 7252 The Constrained Application Protocol (CoAP) Jun-2014 Errata, Updated by RFC 7959, RFC 8613, RFC 8974 Proposed Standard
RFC 7390 Group Communication for the Constrained Application Protocol (CoAP) Oct-2014 Experimental
RFC 7641 Observing Resources in the Constrained Application Protocol (CoAP) Sep-2015 Updated by RFC 8323 Proposed Standard
RFC 7650 A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD) Sep-2015 Proposed Standard
RFC 7959 Block-Wise Transfers in the Constrained Application Protocol (CoAP) Aug-2016 Errata, Updates RFC 7252, Updated by RFC 8323 Proposed Standard
RFC 7967 Constrained Application Protocol (CoAP) Option for No Server Response Aug-2016 Informational
RFC 8075 Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP) Feb-2017 Proposed Standard
RFC 8132 PATCH and FETCH Methods for the Constrained Application Protocol (CoAP) Apr-2017 Proposed Standard
RFC 8152 CBOR Object Signing and Encryption (COSE) Jul-2017 Errata Proposed Standard
RFC 8323 CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets Feb-2018 Updates RFC 7641, RFC 7959, Updated by RFC 8974 Proposed Standard
RFC 8352 Energy-Efficient Features of Internet of Things Protocols Apr-2018 Informational
RFC 8387 Practical Considerations and Implementation Experiences in Securing Smart Object Networks May-2018 Informational
RFC 8516 “Too Many Requests” Response Code for the Constrained Application Protocol Jan-2019 Proposed Standard
RFC 8710 Multipart Content-Format for the Constrained Application Protocol (CoAP) Feb-2020 Proposed Standard
RFC 8768 Constrained Application Protocol (CoAP) Hop-Limit Option Mar-2020 Proposed Standard
RFC 8790 FETCH and PATCH with Sensor Measurement Lists (SenML) Jun-2020 Proposed Standard
RFC 8824 Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP) Jun-2021 Proposed Standard
RFC 8974 Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP) Jan-2021 Updates RFC 7252, RFC 8323 Proposed Standard
RFC 9006 TCP Usage Guidance in the Internet of Things (IoT) Mar-2021 Informational