References from BCP 190
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 |
References Referenced by |
normatively references | ||
BCP 35 |
References Referenced by |
informatively references | ||
RFC 1034 |
Domain names - concepts and facilities
References Referenced by |
Internet Standard | informatively 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 6570 |
URI Template
References Referenced by |
Proposed Standard | informatively references | |
RFC 6901 |
JavaScript Object Notation (JSON) Pointer
References Referenced by |
Proposed Standard | informatively references | |
RFC 6943 |
Issues in Identifier Comparison for Security Purposes
References Referenced by |
Informational | informatively references | |
RFC 7320 |
URI Design and Ownership
References Referenced by |
Best Current Practice | informatively references | |
RFC 7595 |
Guidelines and Registration Procedures for URI Schemes
References Referenced by |
Best Current Practice | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8288 |
Web Linking
References Referenced by |
Proposed Standard | informatively references | |
RFC 8615 |
Well-Known Uniform Resource Identifiers (URIs)
References Referenced by |
Proposed Standard | informatively references | |
STD 13 |
References Referenced by |
informatively references | ||
STD 66 |
References Referenced by |
normatively references |