WG Review: IMAP QRESYNC Extension (qresync)
The IESG <iesg-secretary@ietf.org> Tue, 16 April 2013 16:23 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3930A21F96F2 for <ietf-announce@ietfa.amsl.com>; Tue, 16 Apr 2013 09:23:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.491
X-Spam-Level:
X-Spam-Status: No, score=-102.491 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sEC-Wfwz7Kic for <ietf-announce@ietfa.amsl.com>; Tue, 16 Apr 2013 09:23:35 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7163D21F96CA for <ietf-announce@ietf.org>; Tue, 16 Apr 2013 09:23:35 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Review: IMAP QRESYNC Extension (qresync)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.43.p4
Message-ID: <20130416162335.19246.25041.idtracker@ietfa.amsl.com>
Date: Tue, 16 Apr 2013 09:23:35 -0700
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 16:23:37 -0000
A new IETF working group has been proposed in the Applications Area. The IESG has not made any determination yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg at ietf.org) by 2013-04-23. IMAP QRESYNC Extension (qresync) ------------------------------------------------ Current Status: Proposed Working Group Assigned Area Director: Barry Leiba <barryleiba@computer.org> Mailing list Address: imapext@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/imapext Archive: http://www.ietf.org/mail-archive/web/imapext/ Charter of Working Group: The Internet Message Access Protocol (IMAP), defined in RFC 3501, specifies a protocol for accessing email messages on a server that implements a message store from a client. It also includes commands for manipulating the message store -- creating, deleting, and renaming mailboxes, adding a message to a mailbox, and copying messages from one mailbox to another. Base IMAP as described in RFC 3501 requires that in order to discover flag changes and expunged messages in a mailbox, the client has to fetch flags for all messages it knows in the mailbox and compare returned results with its own state. This can generate a significant amount of traffic for big mailboxes. The IMAP CONDSTORE extension (RFC 4551) provides a facility for IMAP clients to quickly resynchronize mailbox flag changes in a mailbox. The IMAP QRESYNC extension (RFC 5162) extends CONDSTORE to also cover expunged messages, and reduces the number of round trips needed to resynchronize by extending the SELECT/EXAMINE command. The CONDSTORE and QRESYNC extensions are deployed in both clients and servers. These deployments have exposed errors and clarity issues in the specifications, and they need correcting. The IMAP QRESYNC Extension working group has the task of updating CONDSTORE and QRESYNC extensions on the Standards Track. The working group might produce one (combined) or two separate documents (as now) updating these extensions. The working group will review errata and update the documents as needed to incorporate those, and will correct significant errors and inconsistencies, but will keep changes at this stage to a minimum and avoid incompatible changes. No other IMAP extension work is in scope for this working group. Milestones: TBD