IMAP4 non-synchronizing literals
draft-melnikov-rfc2088bis-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | John G. Myers , Alexey Melnikov | ||
| Last updated | 2013-11-04 (Latest revision 2013-04-23) | ||
| Replaced by | draft-ietf-imapapnd-rfc2088bis, RFC 7888 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)