References from draft-weber-iri-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 | ||
draft-abarth-url |
Parsing URLs for Fun and Profit
References Referenced by |
informatively references | ||
draft-hoehrmann-javascript-scheme |
The 'javascript' resource identifier scheme
References Referenced by |
Possible Reference | ||
draft-ietf-iri-3987bis |
Internationalized Resource Identifiers (IRIs)
References Referenced by |
Proposed Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2397 |
The "data" URL scheme
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 3629 |
UTF-8, a transformation format of ISO 10646
References Referenced by |
Internet Standard | normatively references | |
RFC 3896 |
Definitions of Managed Objects for the DS3/E3 Interface Type
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
RFC 3987 |
Internationalized Resource Identifiers (IRIs)
References Referenced by |
Proposed Standard | normatively references | |
RFC 4395 |
Guidelines and Registration Procedures for New URI Schemes
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 5137 |
ASCII Escaping of Unicode Characters
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 6068 |
The 'mailto' URI Scheme
References Referenced by |
Proposed Standard | Possible Reference |