References from rfc8536
This is an experimental product. These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 13 |
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 175 |
Procedures for Maintaining the Time Zone Database Refs Ref'd by |
Best Current Practice | informatively references | |
| RFC 20 |
ASCII format for network interchange Refs Ref'd by |
Internet Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 5545 |
Internet Calendaring and Scheduling Core Object Specification (iCalendar) Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 6557 |
Procedures for Maintaining the Time Zone Database Refs Ref'd by |
Best Current Practice | informatively references | |
| RFC 6838 |
Media Type Specifications and Registration Procedures Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 7231 |
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 7808 |
Time Zone Data Distribution Service Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 8446 |
The Transport Layer Security (TLS) Protocol Version 1.3 Refs Ref'd by |
Proposed Standard | informatively references |