References from RFC 4350
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 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 3406 |
Uniform Resource Names (URN) Namespace Definition Mechanisms
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | Possible Reference | |
STD 63 |
References Referenced by |
Possible Reference | ||
STD 66 |
References Referenced by |
informatively references |