IMAP4 non-synchronizing literals
draft-melnikov-rfc2088bis-04

Document Type Replaced Internet-Draft (individual)
Last updated 2015-03-09
Replaced by draft-ietf-imapapnd-rfc2088bis
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-imapapnd-rfc2088bis
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-melnikov-rfc2088bis-04.txt

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 which does not require this network round trip. This document specifies 2 IMAP extensions: LITERAL+ and LITERAL-. The former allows the alternate form of literals in all IMAP command. The latter is the same as LITERAL+, but disallow the alternate form in IMAP APPEND, unless they are 4096 bytes or less.

Authors

John Myers (jgm+@cmu.edu)
Alexey Melnikov (alexey.melnikov@isode.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)