JMAP for Sieve Scripts
draft-murchison-jmap-sieve-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-03-05
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Independent Submission K. Murchison
Internet-Draft FastMail
Intended status: Standards Track March 5, 2020
Expires: September 6, 2020
JMAP for Sieve Scripts
draft-murchison-jmap-sieve-01
Abstract
This document specifies a data model for managing Sieve scripts on a
server using JMAP.
Open Issues
o How should doing /set{create} with an existing script name be
handled? Should it fail or overwrite the existing script? Should
the /set request include an 'overwrite' boolean argument?
o Should setting isActive==true on a script automatically deactivate
any other existing active script, or should the client have to do
so itself (as is currently documented)?
o Do we want/need a SieveScript/copy method?
o Do we want to leverage draft-ietf-jmap-quotas to query Sieve
script storage quotas?
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 September 6, 2020.
Murchison Expires September 6, 2020 [Page 1]
Internet-Draft JMAP Sieve March 2020
Copyright Notice
Copyright (c) 2020 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Addition to the Capabilities Object . . . . . . . . . . . 3
1.3.1. urn:ietf:params:jmap:sieve . . . . . . . . . . . . . 3
2. Sieve Scripts . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. SieveScript/get . . . . . . . . . . . . . . . . . . . . . 5
2.2. SieveScript/set . . . . . . . . . . . . . . . . . . . . . 5
2.3. SieveScript/validate . . . . . . . . . . . . . . . . . . 5
3. Security Considerations . . . . . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
4.1. JMAP Capability Registration for "sieve" . . . . . . . . 6
4.2. JMAP Error Codes Registry . . . . . . . . . . . . . . . . 7
4.2.1. scriptIsActive . . . . . . . . . . . . . . . . . . . 7
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Normative References . . . . . . . . . . . . . . . . . . 7
6.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Change History (To be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
JMAP ([RFC8620] - JSON Meta Application Protocol) is a generic
protocol for synchronizing data, such as mail, calendars or contacts,
between a client and a server. It is optimized for mobile and web
environments, and aims to provide a consistent interface to different
data types.
Murchison Expires September 6, 2020 [Page 2]
Internet-Draft JMAP Sieve March 2020
This specification defines a data model for managing Sieve [RFC5228]
scripts on a server using JMAP. The data model is designed to allow
a server to provide consistent access to the same scripts via
ManageSieve [RFC5804] as well as JMAP, however the functionality
offered over the two protocols may differ.
1.1. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text