| RFC
|
Status
|
Reference
|
Notes
|
| 6919
|
Experimental
|
R. Barnes; S. Kent; E. Rescorla (1 April 2013). Further Key Words for Use in RFCs to Indicate Requirement Levels. Independent Submission. doi:10.17487/RFC6919. ISSN 2070-1721. RFC 6919.
|
This is an April Fools' Day Request for Comments.
|
| 6920
|
Proposed Standard
|
S. Farrell; D. Kutscher; C. Dannewitz; B. Ohlman; A. Keranen; P. Hallam-Baker (April 2013). Naming Things with Hashes. Independent Submission. doi:10.17487/RFC6920. ISSN 2070-1721. RFC 6920.
|
|
| 6921
|
Informational
|
R. Hinden (1 April 2013). Design Considerations for Faster-Than-Light (FTL) Communication. Independent Submission. doi:10.17487/RFC6921. ISSN 2070-1721. RFC 6921.
|
This is an April Fools' Day Request for Comments.
|
| 6951
|
Proposed Standard
|
M. Tuexen; R. Stewart (May 2013). UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets for End-Host to End-Host Communication. IETF. doi:10.17487/RFC6951. ISSN 2070-1721. RFC 6951.
|
Updated by RFC 8899.
|
| 6963
|
Best Current Practice
|
P. Saint-Andre (May 2013). A Uniform Resource Name (URN) Namespace for Examples. IETF. doi:10.17487/RFC6963. ISSN 2070-1721. RFC 6963.
|
Updates RFC 1930.
|
| 6980
|
Proposed Standard
|
F. Gont (August 2013). Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery. IETF. doi:10.17487/RFC6980. ISSN 2070-1721. RFC 6980.
|
Updates RFC 3971 and 4861.
|
| 6996
|
Best Current Practice
|
J. Mitchell (July 2013). Autonomous System (AS) Reservation for Private Use. IETF. doi:10.17487/RFC6996. ISSN 2070-1721. BCP 6. RFC 6996.
|
Updates RFC 1930.
|
