JSON Meta Application Protocol (JMAP) for Calendars
draft-ietf-jmap-calendars-22

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-jmap-calendars@ietf.org, jmap-chairs@ietf.org, jmap@ietf.org, joris@audriga.com, rfc-editor@rfc-editor.org, superuser@gmail.com
Subject: Protocol Action: 'JSON Meta Application Protocol (JMAP) for Calendars' to Proposed Standard (draft-ietf-jmap-calendars-22.txt)

The IESG has approved the following document:
- 'JSON Meta Application Protocol (JMAP) for Calendars'
  (draft-ietf-jmap-calendars-22.txt) as Proposed Standard

This document is the product of the JSON Mail Access Protocol Working Group.

The IESG contact persons are Murray Kucherawy and Orie Steele.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-jmap-calendars/

Ballot Text

Technical Summary

   This document specifies a data model for synchronizing calendar data
   with a server using JMAP.

Working Group Summary

There has been controversy about the proposed solution for achieving scheduling
regarding its interoperability with existing calendar scheduling protocols.
This has been resolved since last IETF by introducing a new property called
"calendarUserAddress" to resolve interoperability concerns with legacy calendaring
formats like iCalendar [RFC5545][18]. A related draft is
[draft-ietf-calext-jscalendar-icalendar][19] which defines how to convert between
iCalendar and JSCalendar.

Additionally, Discussion about Calendar role deviating from JMAP Mail was a bit controversial
and consensus a bit rough, but there was consensus.

Document Quality

This is believed to have been implemented in Fastmail, and others have
expressed interest. Audriga also has implemented parts of the JMAP Calendars
specification. Test implementations have been written by other JMAP server
authors.

No specific additional reviews are warranted.

Personnel

   The Document Shepherd for this document is Joris Baum. The Responsible
   Area Director is Murray Kucherawy.

RFC Editor Note