References from draft-nottingham-uri-get-off-my-lawn
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 |
References Referenced by |
normatively references | ||
BCP 14 |
References Referenced by |
normatively references | ||
BCP 35 |
References Referenced by |
normatively references | ||
BCP 9 |
References Referenced by |
informatively references | ||
RFC 2026 |
The Internet Standards Process -- Revision 3
References Referenced by |
Best Current Practice | 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 4395 |
Guidelines and Registration Procedures for New URI Schemes
References Referenced by |
Best Current Practice | normatively references | |
RFC 4844 |
The RFC Series and RFC Editor
References Referenced by |
Informational | informatively references | |
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 | |
STD 66 |
References Referenced by |
normatively references |