References from RFC 9167
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 |
|---|---|---|---|---|
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3339 |
Date and Time on the Internet: Timestamps
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | informatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 5646 |
Tags for Identifying Languages
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5730 |
Extensible Provisioning Protocol (EPP)
References Referenced by |
Internet Standard | normatively references | |
| RFC 5891 |
Internationalized Domain Names in Applications (IDNA): Protocol
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7451 |
Extension Registry for the Extensible Provisioning Protocol
References Referenced by |
Informational | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 9038 |
Extensible Provisioning Protocol (EPP) Unhandled Namespaces
References Referenced by |
Proposed Standard | normatively references |