References from rfc6415
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 14 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1 Refs Ref'd by |
Draft Standard | normatively references | |
RFC 2818 |
HTTP Over TLS Refs Ref'd by |
Informational | normatively references | Downref |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by |
Internet Standard | normatively references | |
RFC 4627 |
The application/json Media Type for JavaScript Object Notation (JSON) Refs Ref'd by |
Informational | normatively references | Downref |
RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF Refs Ref'd by |
Internet Standard | normatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates Refs Ref'd by |
Informational | Possible Reference | Possible Downref |
RFC 5785 |
Defining Well-Known Uniform Resource Identifiers (URIs) Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 5988 |
Web Linking Refs Ref'd by |
Proposed Standard | normatively references | |
STD 66 |
Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by |
Internet Standard | normatively references | |
STD 68 |
Augmented BNF for Syntax Specifications: ABNF Refs Ref'd by |
Internet Standard | normatively references |