References from RFC 5527
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 | ||
RFC 1034 |
Domain names - concepts and facilities
References Referenced by |
Internet Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2672 |
Non-Terminal DNS Name Redirection
References Referenced by |
Proposed Standard | normatively references | |
RFC 3401 |
Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS
References Referenced by |
Informational | normatively references | |
RFC 3761 |
The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
RFC 5067 |
Infrastructure ENUM Requirements
References Referenced by |
Informational | informatively references | |
RFC 5526 |
The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM
References Referenced by |
Informational | informatively references | |
STD 13 |
References Referenced by |
normatively references | ||
STD 66 |
References Referenced by |
normatively references |