Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

IMAP4 Non-synchronizing Literals (RFC7888)

IP.com Disclosure Number: IPCOM000246756D
Original Publication Date: 2016-May-01
Included in the Prior Art Database: 2016-Jun-29
Document File: 18 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Melnikov: AUTHOR [+2]

Abstract

The Internet Message Access Protocol [RFC3501] 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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 16% of the total text.

Internet Engineering Task Force (IETF)                  A. Melnikov, Ed. Request for Comments: 7888                                     Isode Ltd Obsoletes: 2088                                                 May 2016 Category: Standards Track ISSN: 2070-1721

                     IMAP4 Non-synchronizing Literals

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7888.

 Melnikov                     Standards Track                    [Page 1]
 RFC 7888            IMAP4 Non-synchronizing Literals            May 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF    Contributions published or made publicly available before November    10, 2008.  The person(s) controlling the copyright in some of this    material may not have...