References from RFC 5524
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 | ||
RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by |
Draft Standard | normatively references | |
RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by |
Draft Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 3501 |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
References Referenced by |
Proposed Standard | normatively references | |
RFC 3516 |
IMAP4 Binary Content Extension
References Referenced by |
Proposed Standard | normatively references | |
RFC 4467 |
Internet Message Access Protocol (IMAP) - URLAUTH Extension
References Referenced by |
Proposed Standard | normatively references | |
RFC 4468 |
Message Submission BURL Extension
References Referenced by |
Proposed Standard | informatively references | |
RFC 4648 |
The Base16, Base32, and Base64 Data Encodings
References Referenced by |
Proposed Standard | normatively references | |
RFC 5259 |
Internet Message Access Protocol - CONVERT Extension
References Referenced by |
Proposed Standard | normatively references | |
STD 68 |
References Referenced by |
normatively references |