References from RFC 5137
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 18 | References Referenced by | informatively references | ||
| BCP 78 | References Referenced by | informatively references | ||
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | normatively references | |
| RFC 2277 | IETF Policy on Character Sets and Languages References Referenced by | Best Current Practice | informatively references | |
| RFC 3492 | Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA) References Referenced by | Proposed Standard | informatively references | |
| RFC 3629 | UTF-8, a transformation format of ISO 10646 References Referenced by | Internet Standard | normatively references | |
| RFC 5234 | Augmented BNF for Syntax Specifications: ABNF References Referenced by | Internet Standard | informatively references | |
| STD 63 | References Referenced by | normatively references | ||
| STD 68 | References Referenced by | normatively references |