[imapext] RFC 7888 on IMAP4 Non-synchronizing Literals

rfc-editor@rfc-editor.org Tue, 17 May 2016 22:26 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4648712DDEE; Tue, 17 May 2016 15:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Q8nBeJLbfjlR; Tue, 17 May 2016 15:26:01 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0468A12DAD5; Tue, 17 May 2016 15:25:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1E479180011; Tue, 17 May 2016 15:25:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160517222505.1E479180011@rfc-editor.org>
Date: Tue, 17 May 2016 15:25:04 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/-UMtYpNHPOyvM9-cjoU8eHjBwVw>
Cc: drafts-update-ref@iana.org, imapext@ietf.org, rfc-editor@rfc-editor.org
Subject: [imapext] RFC 7888 on IMAP4 Non-synchronizing Literals
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 22:26:03 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7888

        Title:      IMAP4 Non-synchronizing Literals 
        Author:     A. Melnikov, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2016
        Mailbox:    alexey.melnikov@isode.com
        Pages:      9
        Characters: 17375
        Obsoletes:  RFC 2088

        I-D Tag:    draft-ietf-imapapnd-rfc2088bis-04.txt

        URL:        https://www.rfc-editor.org/info/rfc7888

        DOI:        http://dx.doi.org/10.17487/RFC7888

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

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.

This document is a product of the IMAP APPEND Extensions Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC