References from draft-hansen-2717bis-2718bis-uri-guidelines
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 26 |
References Referenced by |
normatively references | ||
BCP 66 |
References Referenced by |
informatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
BCP 90 |
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2141 |
URN Syntax
References Referenced by |
Proposed Standard | normatively references | |
RFC 2717 |
Registration Procedures for URL Scheme Names
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2718 |
Guidelines for new URL Schemes
References Referenced by |
Informational | informatively references | |
RFC 3406 |
Uniform Resource Names (URN) Namespace Definition Mechanisms
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 3978 |
IETF Rights in Contributions
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | Possible Reference | |
RFC 3987 |
Internationalized Resource Identifiers (IRIs)
References Referenced by |
Proposed Standard | normatively references | |
STD 66 |
References Referenced by |
normatively references |