IMAP4 Non-synchronizing Literals
RFC 7888, “IMAP4 Non-synchronizing Literals”, is a Proposed Standard document published in May 2016 by A. Melnikov. It obsoletes RFC 2088. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 7888 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7887 Hierarchical Join/Prune Attributes
- RFC 7889 The IMAP APPENDLIMIT Extension
- RFC 7886 Advertising Seamless Bidirectional Forwarding Detection Discriminators in the Layer Two Tunneling Protocol Version 3
- RFC 7890 Concepts and Terminology for Peer-to-Peer SIP
- RFC 7885 Seamless Bidirectional Forwarding Detection for Virtual Circuit Connectivity Verification
- RFC 7891 Explicit Reverse Path Forwarding Vector
- RFC 7884 OSPF Extensions to Advertise Seamless Bidirectional Forwarding Detection Target Discriminators
- RFC 7892 IANA Allocation Procedures for the GMPLS OTN Signal Type Registry