References from RFC 5256
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 19 |
References Referenced by |
normatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
RFC 1733 |
Distributed Electronic Mail Models in IMAP4
References Referenced by |
Informational | informatively references | |
RFC 2047 |
MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
References Referenced by |
Draft Standard | Possible Reference | |
RFC 2822 |
Internet Message Format
References Referenced by |
Proposed Standard | normatively references | |
RFC 3501 |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
References Referenced by |
Proposed Standard | normatively references | |
RFC 5051 |
i;unicode-casemap - Simple Unicode Collation Algorithm
References Referenced by |
Proposed Standard | normatively references | |
RFC 5255 |
Internet Message Access Protocol Internationalization
References Referenced by |
Proposed Standard | normatively references | |
RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | Possible Reference | |
STD 63 |
References Referenced by |
normatively references | ||
STD 68 |
References Referenced by |
normatively references |