References from RFC 4466
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 |
normatively references | ||
RFC 2088 |
IMAP4 non-synchronizing literals
References Referenced by |
Proposed Standard | normatively references | |
RFC 2342 |
IMAP4 Namespace
References Referenced by |
Proposed Standard | normatively references | |
RFC 3501 |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
References Referenced by |
Proposed Standard | normatively references | |
RFC 3502 |
Internet Message Access Protocol (IMAP) - MULTIAPPEND Extension
References Referenced by |
Proposed Standard | normatively references | |
RFC 3516 |
IMAP4 Binary Content Extension
References Referenced by |
Proposed Standard | normatively references | |
RFC 4234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Draft Standard | normatively references |