Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 2088

Author:

A. Melnikov, Ed.

Stream:

IETF

Source:

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 listimapext@ietf.org

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

Abstract

The Internet Message Access Protocol (RFC 3501) contains the"literal" syntactic construct for communicating strings. Whensending a literal from client to server, IMAP requires the client towait for the server to send a command continuation request betweensending the octet count and the string data. This document specifiesan alternate form of literal that does not require this network roundtrip.

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 formof literals unless they are 4096 bytes or less.

This document obsoletes RFC 2088.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.