References from draft-melnikov-imapext-multimailbox-search
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 78 |
References Referenced by |
normatively references | ||
| draft-cridland-imap-context |
Contexts for IMAP4
References Referenced by |
Proposed Standard | Possible Reference | |
| draft-ietf-imapext-list-extensions |
Internet Message Access Protocol version 4 - LIST Command Extensions
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-lemonade-imap-notify |
The IMAP NOTIFY Extension
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2978 |
IANA Charset Registration Procedures
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3501 |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4314 |
IMAP4 Access Control List (ACL) Extension
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4466 |
Collected Extensions to IMAP4 ABNF
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4731 |
IMAP4 Extension to SEARCH Command for Controlling What Kind of Information Is Returned
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references |