JMAP for Calendars
draft-ietf-jmap-calendars-00
JMAP N. Jenkins
Internet-Draft FastMail
Intended status: Standards Track M. Douglass
Expires: October 31, 2019 Spherical Cow Group
April 29, 2019
JMAP for Calendars
draft-ietf-jmap-calendars-00
Abstract
This document specifies a data model for synchronising calendar data
with a server using JMAP.
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 October 31, 2019.
Copyright Notice
Copyright (c) 2019 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.
Jenkins & Douglass Expires October 31, 2019 [Page 1]
Internet-Draft JMAP Calendars April 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational conventions . . . . . . . . . . . . . . . . . 2
1.2. The Date datatypes . . . . . . . . . . . . . . . . . . . 3
1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.4. Addition to the capabilities object . . . . . . . . . . . 3
2. Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Calendar/get . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Calendar/changes . . . . . . . . . . . . . . . . . . . . 5
2.3. Calendar/set . . . . . . . . . . . . . . . . . . . . . . 5
3. Calendar events . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. CalendarEvent/get . . . . . . . . . . . . . . . . . . . . 6
3.2. CalendarEvent/changes . . . . . . . . . . . . . . . . . . 6
3.3. CalendarEvent/set . . . . . . . . . . . . . . . . . . . . 6
3.4. CalendarEvent/copy . . . . . . . . . . . . . . . . . . . 6
3.5. CalendarEvent/query . . . . . . . . . . . . . . . . . . . 7
3.5.1. Filtering . . . . . . . . . . . . . . . . . . . . . . 7
3.5.2. Sorting . . . . . . . . . . . . . . . . . . . . . . . 8
3.6. CalendarEvent/queryChanges . . . . . . . . . . . . . . . 8
4. Security considerations . . . . . . . . . . . . . . . . . . . 8
5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 9
5.1. JMAP capability registration for "calendars" . . . . . . 9
6. Normative References . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
JMAP ([I-D.ietf-jmap-core] - JSON Meta Application Protocol) is a
generic protocol for synchronising data, such as mail, calendars or
contacts, between a client and a server. It is optimised for mobile
and web environments, and aims to provide a consistent interface to
different data types.
This specification defines a data model for synchronising calendar
data between a client and a server using JMAP.
1.1. Notational conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Type signatures, examples and property descriptions in this document
follow the conventions established in section 1.1 of
[I-D.ietf-jmap-core].
Jenkins & Douglass Expires October 31, 2019 [Page 2]
Internet-Draft JMAP Calendars April 2019
Object properties may also have a set of attributes defined along
Show full document text