[imapext] RFC 7889 on The IMAP APPENDLIMIT Extension

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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4776B12DDE8; Tue, 17 May 2016 15:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rrFLis6NPY66; Tue, 17 May 2016 15:26:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 801DE12DE13; Tue, 17 May 2016 15:25:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A3F8618000C; Tue, 17 May 2016 15:25:29 -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: <20160517222529.A3F8618000C@rfc-editor.org>
Date: Tue, 17 May 2016 15:25:29 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/pkQT3psqQgGKYJwmXrBqek69Y54>
Cc: drafts-update-ref@iana.org, imapext@ietf.org, rfc-editor@rfc-editor.org
Subject: [imapext] RFC 7889 on The IMAP APPENDLIMIT Extension
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:30 -0000

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

        
        RFC 7889

        Title:      The IMAP APPENDLIMIT Extension 
        Author:     J. SrimushnamBoovaraghamoorthy, N. Bisht
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2016
        Mailbox:    jayantheesh.sb@gmail.com, 
                    narendrasingh.bisht@gmail.com
        Pages:      7
        Characters: 13801
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imapapnd-appendlimit-extension-10.txt

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

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

This document defines an extension to the IMAP service whereby a
server can inform the client about maximum message upload sizes,
allowing the client to avoid sending APPEND commands that will fail
because the messages are too large.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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