IMAP Extension for Conditional STORE Operation or Quick Flag Changes Resynchronization
draft-ietf-qresync-rfc4551bis-03

The information below is for an old version of the document
Document Type Active Internet-Draft (qresync WG)
Last updated 2013-08-21
Replaced by draft-ietf-qresync-rfc5162bis, rfc7162
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        A. Melnikov
Internet-Draft                                                Isode Ltd.
Obsoletes: 4551 (if approved)                            August 21, 2013
Updates: 3501, 2683 (if approved)
Intended status: Standards Track
Expires: February 22, 2014

  IMAP Extension for Conditional STORE Operation or Quick Flag Changes
                           Resynchronization
                  draft-ietf-qresync-rfc4551bis-03.txt

Abstract

   Often, multiple IMAP (RFC 3501) clients need to coordinate changes to
   a common IMAP mailbox.  Examples include different clients working on
   behalf of the same user, and multiple users accessing shared
   mailboxes.  These clients need a mechanism to synchronize state
   changes for messages within the mailbox.  They must be able to
   guarantee that only one client can change message state (e.g.,
   message flags) at any time.  An example of such an application is use
   of an IMAP mailbox as a message queue with multiple dequeueing
   clients.

   The Conditional Store facility provides a protected update mechanism
   for message state information that can detect and resolve conflicts
   between multiple writing mail clients.

   The Conditional Store facility also allows a client to quickly
   resynchronize mailbox flag changes.

   This document defines an extension to IMAP (RFC 3501).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Melnikov                Expires February 22, 2014               [Page 1]
Internet-Draft               IMAP CONDSTORE                  August 2013

   This Internet-Draft will expire on February 22, 2014.

Copyright Notice

   Copyright (c) 2013 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.

Table of Contents

   1.  Introduction and Overview . . . . . . . . . . . . . . . . . .   3
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   5
   3.  IMAP Protocol Changes . . . . . . . . . . . . . . . . . . . .   6
     3.1.  New OK Untagged Responses for SELECT and EXAMINE  . . . .   6
       3.1.1.  HIGHESTMODSEQ Response Code . . . . . . . . . . . . .   6
       3.1.2.  NOMODSEQ Response Code  . . . . . . . . . . . . . . .   7
     3.2.  STORE and UID STORE Commands  . . . . . . . . . . . . . .   8
     3.3.  FETCH and UID FETCH Commands  . . . . . . . . . . . . . .  14
       3.3.1.  CHANGEDSINCE FETCH Modifier . . . . . . . . . . . . .  14
       3.3.2.  MODSEQ Message Data Item in FETCH Command . . . . . .  14
     3.4.  MODSEQ Search Criterion in SEARCH . . . . . . . . . . . .  16
     3.5.  Modified SEARCH Untagged Response . . . . . . . . . . . .  18
     3.6.  HIGHESTMODSEQ Status Data Items . . . . . . . . . . . . .  18
     3.7.  CONDSTORE Parameter to SELECT and EXAMINE . . . . . . . .  18
     3.8.  Interaction with IMAP SORT and THREAD extensions  . . . .  19
     3.9.  Interaction with IMAP ESORT and ESEARCH extensions  . . .  19
     3.10. Additional Quality-of-Implementation Issues . . . . . . .  20
   4.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .  20
   5.  Server Implementation Considerations  . . . . . . . . . . . .  23
   6.  Long Command Lines  . . . . . . . . . . . . . . . . . . . . .  24
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  24
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  24
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  25
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  25
     10.2.  Informative References . . . . . . . . . . . . . . . . .  25
Show full document text