IMAP REPLACE Extension
draft-ietf-extra-imap-replace-00
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (extra WG)
|
|
Last updated |
|
2018-09-30
(latest revision 2018-08-10)
|
|
Replaces |
|
draft-brandt-imap-replace
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Bron Gondwana
|
|
Shepherd write-up |
|
Show
(last changed 2018-09-17)
|
IESG |
IESG state |
|
AD Evaluation
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alexey Melnikov
|
|
Send notices to |
|
Bron Gondwana <brong@fastmailteam.com>
|
Network Working Group S. Brandt
Internet-Draft Verizon
Intended status: Standards Track August 8, 2018
Expires: February 9, 2019
IMAP REPLACE Extension
draft-ietf-extra-imap-replace-00
Abstract
This document defines an IMAP extension which can be used to replace
an existing message in a message store with a new message. Message
replacement is a common operation for clients that automatically save
drafts or notes as a user composes them.
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 February 9, 2019.
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.
Brandt Expires February 9, 2019 [Page 1]
Internet-Draft IMAP REPLACE Extension August 2018
Table of Contents
1. Conventions Used in This Document . . . . . . . . . . . . . . 2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. REPLACE and UID REPLACE . . . . . . . . . . . . . . . . . . . 3
3.1. Advertising Support for REPLACE . . . . . . . . . . . . . 3
3.2. REPLACE Command . . . . . . . . . . . . . . . . . . . . . 3
3.3. UID REPLACE Command . . . . . . . . . . . . . . . . . . . 4
3.4. Semantics of REPLACE and UID REPLACE . . . . . . . . . . 5
3.5. IMAP State Diagram Impacts . . . . . . . . . . . . . . . 6
4. Interaction with other extensions . . . . . . . . . . . . . . 6
4.1. RFC 4314, ACL . . . . . . . . . . . . . . . . . . . . . . 6
4.2. RFC 4469, CATENATE . . . . . . . . . . . . . . . . . . . 6
4.3. RFC 4315, UIDPLUS . . . . . . . . . . . . . . . . . . . . 8
4.4. RFC 6785, IMAP Events in Sieve . . . . . . . . . . . . . 8
4.5. RFC 7162, CONDSTORE/QRESYNC . . . . . . . . . . . . . . . 8
4.6. draft-ietf-extra-imap-objectid, OBJECTID . . . . . . . . 8
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Formal syntax is defined by [RFC5234].
Example lines prefaced by "C:" are sent by the client and ones
prefaced by "S:" by the server.
2. Overview
This document defines an IMAP [RFC3501] extension to facilitate
replacing an existing message with a new one. This is accomplished
by defining a new REPLACE command and extending the UID command to
allow UID REPLACE.
Since there is no replace function in the base IMAP specification,
clients have instead had to use a combination of three separate
commands issued in serial fashion; APPEND, STORE, EXPUNGE.
Pipelining of these three commands is not recommended since failure
Brandt Expires February 9, 2019 [Page 2]
Internet-Draft IMAP REPLACE Extension August 2018
of any individual command should prevent subsequent commands from
Show full document text