References from rfc7320
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 References Referenced by |
Best Current Practice | normatively references | |
BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax References Referenced by |
Internet Standard | normatively references | |
RFC 4395 |
Guidelines and Registration Procedures for New URI Schemes References Referenced by |
Best Current Practice | informatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 5785 |
Defining Well-Known Uniform Resource Identifiers (URIs) References Referenced by |
Proposed Standard | informatively references | |
RFC 5988 |
Web Linking References Referenced by |
Proposed Standard | informatively references | |
RFC 6570 |
URI Template References Referenced by |
Proposed Standard | informatively references | |
RFC 6838 |
Media Type Specifications and Registration Procedures References Referenced by |
Best Current Practice | normatively references | |
RFC 6943 |
Issues in Identifier Comparison for Security Purposes References Referenced by |
Informational | informatively references | |
STD 66 |
Uniform Resource Identifier (URI): Generic Syntax References Referenced by |
Internet Standard | normatively references |