References from RFC 7888
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 | ||
draft-ietf-imapapnd-appendlimit-extension |
The IMAP APPENDLIMIT Extension
References Referenced by |
Proposed Standard | informatively references | |
RFC 2088 |
IMAP4 non-synchronizing literals
References Referenced by |
Proposed Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | 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 | informatively references | |
RFC 3516 |
IMAP4 Binary Content Extension
References Referenced by |
Proposed Standard | normatively references | |
RFC 4466 |
Collected Extensions to IMAP4 ABNF
References Referenced by |
Proposed Standard | normatively references | |
RFC 4469 |
Internet Message Access Protocol (IMAP) CATENATE Extension
References Referenced by |
Proposed Standard | normatively references | |
STD 68 |
References Referenced by |
normatively references |