WG Action: Rechartered JSON Mail Access Protocol (jmap)
The IESG <email@example.com> Fri, 20 December 2019 17:48 UTC
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 18379120856; Fri, 20 Dec 2019 09:48:37 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
From: The IESG <firstname.lastname@example.org>
To: "IETF-Announce" <email@example.com>
Subject: WG Action: Rechartered JSON Mail Access Protocol (jmap)
Cc: firstname.lastname@example.org, email@example.com, The IESG <firstname.lastname@example.org>
Content-Type: text/plain; charset="utf-8"
Date: Fri, 20 Dec 2019 09:48:37 -0800
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Dec 2019 17:48:37 -0000
The JSON Mail Access Protocol (jmap) WG in the Applications and Real-Time Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the WG Chairs. JSON Mail Access Protocol (jmap) ----------------------------------------------------------------------- Current status: Active WG Chairs: Bron Gondwana <email@example.com> Jim Fenton <firstname.lastname@example.org> Assigned Area Director: Alexey Melnikov <email@example.com> Applications and Real-Time Area Directors: Adam Roach <firstname.lastname@example.org> Alexey Melnikov <email@example.com> Barry Leiba <firstname.lastname@example.org> Mailing list: Address: email@example.com To subscribe: https://www.ietf.org/mailman/listinfo/jmap Archive: https://mailarchive.ietf.org/arch/search/?email_list=jmap Group page: https://datatracker.ietf.org/group/jmap/ Charter: https://datatracker.ietf.org/doc/charter-ietf-jmap/ The JMAP protocol defined in draft-ietf-jmap-core is designed to be extensible to multiple datatypes which are useful for personal information management related to email stores. Now that draft-ietf-jmap-mail is completed, the working group will produce specifications for related data types, beginning with calendars and contacts. The calendar work will be based on draft-ietf-calext-jscalandar as the data format. This working group will consult with the CALEXT working group to ensure that calendar access via JMAP remains compatible with existing calendar standards. The contact work will begin with a JSON format for contact data based upon the work begun in draft-stepanek-jscontact, and in consultation with other users of contact data within the IETF and outside to build an extensible format. Where possible, this format will retain the ability to convert backwards and forwards to RFC6350 vCard format. This format will then be used as the basis of JMAP object types for contacts. Extensions to the existing core and mail JMAP specifications are also within scope for this working group, for example any additional parts of SIEVE, IMAP, SMTP submission, as well as transport of JMAP over WSS (WebSocket over TLS, RFC 6455). Work on JMAP extensions will be bound by the following constraints: 1) The work of this group is limited to developing protocols for a client synchronising data with a server. Any server-to-server issues are out of scope for this working group. 2) Object models will use existing IETF work where possible. 3) JMAP Extensions will be built following the core principles: 3.1) The server will not be required to perform work not explicitly requested by the client, and the default should always be the mode which requires the least server work. 3.2) The client can discover limits enforced by the server on resources or request complexity. 3.3) Where side effects generated by the server are optional, the protocol will default to no side effects, and the client must explicitly request that those side effects happen (for example: sending a calendar invitation or reply when updating an event) The working group will deliver documents for the following: - JMAP access to calendars using the JSCalendar format - JSON formats for representing contacts and groups of contacts (JSContact) - JMAP access to addressbooks using the JSContact format - Accessing JMAP over Websockets - Handling of S/MIME email messages (e.g. signature verification) over JMAP - Message Disposition Notifications (RFC 8098) via JMAP - Other extensions which the working group considers related to email and compatible with the constraints listed above Also within scope for this working group are informational documents for converting between JMAP data representation and other formats already in wide use which can be used to specify the same underlying data. Milestones: Dec 2019 - Submit Message Disposition Notification document to the IESG Jan 2020 - Adopt a document for a JSON Contact format (after recharter) Feb 2020 - Submit JMAP Quotas document to the IESG Feb 2020 - Submit JMAP S/MIME signature validation document to the IESG Feb 2020 - Adopt a document for S/MIME key management and server side signing/encryption Jul 2020 - Adopt a document defining JMAP access to addressbooks Nov 2020 - Submit JMAP Calendars document to the IESG Dec 2020 - Submit document with guidance for implementation of IMAP servers and proxies (Informational) Dec 2020 - Submit JSON Contact document to IESG