IMAP Extension for object identifiers
draft-ietf-extra-imap-objectid-03

Document Type Active Internet-Draft (extra WG)
Last updated 2018-07-13 (latest revision 2018-05-28)
Replaces draft-ietf-extra-imap-uniqueid
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Jiankang Yao
Shepherd write-up Show (last changed 2018-06-21)
IESG IESG state Waiting for AD Go-Ahead::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to Jiankang Yao <yaojk@cnnic.cn>;aamelnikov@fastmail.fm
IANA IANA review state IANA - Not OK
IANA action state None
EXTRA                                                   B. Gondwana, Ed.
Internet-Draft                                                  FastMail
Updates: 3501 (if approved)                                 May 28, 2018
Intended status: Standards Track
Expires: November 29, 2018

                 IMAP Extension for object identifiers
                   draft-ietf-extra-imap-objectid-03

Abstract

   This document updates RFC3501 (IMAP4rev1) with persistent identifiers
   on mailboxes and messages to allow clients to more efficiently re-use
   cached data when resources have changed location on the server.

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 https://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."

   This Internet-Draft will expire on November 29, 2018.

Copyright Notice

   Copyright (c) 2018 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
   (https://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.

Gondwana                Expires November 29, 2018               [Page 1]
Internet-Draft                IMAP ObjectID                     May 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used In This Document . . . . . . . . . . . . . .   3
   3.  CAPABILITY Identification . . . . . . . . . . . . . . . . . .   3
   4.  MAILBOXID object identifier . . . . . . . . . . . . . . . . .   3
     4.1.  New response code for CREATE  . . . . . . . . . . . . . .   4
     4.2.  New OK Untagged Response for SELECT and EXAMINE . . . . .   4
     4.3.  New attribute for STATUS  . . . . . . . . . . . . . . . .   5
   5.  EMAILID object identifier and THREADID correlator . . . . . .   6
     5.1.  EMAILID identifier for identical messages . . . . . . . .   6
     5.2.  THREADID identifer for related messages . . . . . . . . .   6
     5.3.  New Message Data Items in FETCH and UID FETCH Commands  .   7
   6.  New Filters on SEARCH command . . . . . . . . . . . . . . . .   9
   7.  Formal syntax . . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  Implementation considerations . . . . . . . . . . . . . . . .  10
     8.1.  Assigning object identifiers  . . . . . . . . . . . . . .  10
     8.2.  Interaction with special cases  . . . . . . . . . . . . .  11
     8.3.  Client usage  . . . . . . . . . . . . . . . . . . . . . .  11
   9.  Future considerations . . . . . . . . . . . . . . . . . . . .  11
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  12
   12. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     12.1.  draft-ietf-extra-imap-objectid-03  . . . . . . . . . . .  12
     12.2.  draft-ietf-extra-imap-objectid-02  . . . . . . . . . . .  12
     12.3.  draft-ietf-extra-imap-objectid-01  . . . . . . . . . . .  12
     12.4.  draft-ietf-extra-imap-objectid-00  . . . . . . . . . . .  13
     12.5.  draft-ietf-extra-imap-uniqueid-00  . . . . . . . . . . .  13
     12.6.  draft-gondwana-imap-uniqueid-01  . . . . . . . . . . . .  13
     12.7.  draft-gondwana-imap-uniqueid-00  . . . . . . . . . . . .  14
   13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  14
     13.1.  Appendix 1: ideas for implementing object identifiers  .  14
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     14.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     14.2.  Informative References . . . . . . . . . . . . . . . . .  15
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   IMAP stores are often used by many clients.  Each client may cache
   data from the server so that they don't need to re-download
   information.  [RFC3501] defines that a mailbox can be uniquely
   referenced by its name and UIDVALIDITY, and a message within that
   mailbox can be uniquely referenced by its mailbox (name +
Show full document text