References from rfc5466
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 18 |
IETF Policy on Character Sets and Languages
References Referenced by |
Best Current Practice | normatively references | |
| BCP 47 |
Tags for Identifying Languages
References Referenced by |
Best Current Practice | normatively 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 | normatively references | |
| RFC 3501 |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4466 |
Collected Extensions to IMAP4 ABNF
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4646 |
Tags for Identifying Languages
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5464 |
The IMAP METADATA Extension
References Referenced by |
Proposed Standard | normatively references | |
| STD 63 |
UTF-8, a transformation format of ISO 10646
References Referenced by |
Internet Standard | normatively references | |
| STD 68 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references |