References from rfc5076
This is an experimental product. 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 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust Refs Ref'd by |
Best Current Practice | informatively references | |
| BCP 81 |
The IETF XML Registry Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | Possible Reference | |
| RFC 3688 |
The IETF XML Registry Refs Ref'd by |
Best Current Practice | Possible Reference | |
| RFC 3730 |
Extensible Provisioning Protocol (EPP) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3731 |
Extensible Provisioning Protocol (EPP) Domain Name Mapping Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3761 |
The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 4114 |
E.164 Number Mapping for the Extensible Provisioning Protocol (EPP) Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 4725 |
ENUM Validation Architecture Refs Ref'd by |
Informational | informatively references |