RFC 7888

IMAP4 Non-synchronizing Literals, May 2016

File formats:
icon for text file icon for PDF icon for HTML
RFC 2088
A. Melnikov, Ed.
imapapnd (art)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7888

Discuss this RFC: Send questions or comments to the mailing list imapext@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7888


The Internet Message Access Protocol (RFC 3501) contains the "literal" syntactic construct for communicating strings. When sending a literal from client to server, IMAP requires the client to wait for the server to send a command continuation request between sending the octet count and the string data. This document specifies an alternate form of literal that does not require this network round trip.

This document specifies 2 IMAP extensions: LITERAL+ and LITERAL-. LITERAL+ allows the alternate form of literals in all IMAP commands. LITERAL- is the same as LITERAL+, but it disallows the alternate form of literals unless they are 4096 bytes or less.

This document obsoletes RFC 2088.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search