References from rfc3502
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 | |
RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies References Referenced by |
Draft Standard | normatively references | |
RFC 2088 |
IMAP4 non-synchronizing literals References Referenced by |
Proposed Standard | informatively references | |
RFC 2234 |
Augmented BNF for Syntax Specifications: ABNF References Referenced by |
Proposed Standard | normatively references | |
RFC 2359 |
IMAP4 UIDPLUS extension References Referenced by |
Proposed Standard | informatively references | |
RFC 2821 |
Simple Mail Transfer Protocol References Referenced by |
Proposed Standard | informatively references | |
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 |