References from rfc3915
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
References Referenced by |
Best Current Practice | normatively references | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust
References Referenced by |
Best Current Practice | informatively references | |
| BCP 81 |
The IETF XML Registry
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2781 |
UTF-16, an encoding of ISO 10646
References Referenced by |
Informational | informatively references | |
| RFC 3339 |
Date and Time on the Internet: Timestamps
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3629 |
UTF-8, a transformation format of ISO 10646
References Referenced by |
Internet Standard | informatively references | |
| RFC 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 3730 |
Extensible Provisioning Protocol (EPP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3731 |
Extensible Provisioning Protocol (EPP) Domain Name Mapping
References Referenced by |
Proposed Standard | normatively references | |
| RFC 954 |
NICNAME/WHOIS
References Referenced by |
Draft Standard | informatively references | |
| STD 63 |
UTF-8, a transformation format of ISO 10646
References Referenced by |
Internet Standard | informatively references |