References from RFC 4617
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 26 |
References Referenced by |
informatively references | ||
BCP 66 |
References Referenced by |
normatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
RFC 2141 |
URN Syntax
References Referenced by |
Proposed Standard | informatively references | |
RFC 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
RFC 3305 |
Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations
References Referenced by |
Informational | informatively references | |
RFC 3406 |
Uniform Resource Names (URN) Namespace Definition Mechanisms
References Referenced by |
Best Current Practice | normatively references | |
RFC 3616 |
A Uniform Resource Name (URN) Namespace for Foundation for Intelligent Physical Agents (FIPA)
References Referenced by |
Informational | informatively references | |
RFC 3622 |
A Uniform Resource Name (URN) Namespace for the Liberty Alliance Project
References Referenced by |
Informational | informatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
RFC 4234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Draft Standard | informatively references | |
STD 66 |
References Referenced by |
normatively references |