References from draft-ietf-lemonade-imap-channel
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 | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust
References Referenced by |
Best Current Practice | normatively references | |
| draft-nerenberg-imap-channel |
IMAP4 Channel Transport Mechanism
References Referenced by |
normatively references | ||
| RFC 2234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Proposed Standard | normatively references | |
| RFC 2396 |
Uniform Resource Identifiers (URI): Generic Syntax
References Referenced by |
Draft Standard | normatively references | |
| RFC 3501 |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3668 |
Intellectual Property Rights in IETF Technology
References Referenced by |
Best Current Practice | Possible Reference |