References from RFC 8748
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 | ||
| BCP 205 |
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3915 |
Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5730 |
Extensible Provisioning Protocol (EPP)
References Referenced by |
Internet Standard | normatively references | |
| RFC 5731 |
Extensible Provisioning Protocol (EPP) Domain Name Mapping
References Referenced by |
Internet Standard | normatively references | |
| RFC 7451 |
Extension Registry for the Extensible Provisioning Protocol
References Referenced by |
Informational | informatively references | |
| RFC 7942 |
Improving Awareness of Running Code: The Implementation Status Section
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8334 |
Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
References Referenced by |
Proposed Standard | normatively references | |
| STD 69 |
References Referenced by |
normatively references |