Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

The JSON Meta Application Protocol (JMAP) for Mail
RFC 8621

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2019-08-26	Gunter Van de Velde	Closed request for Telechat review by OPSDIR with state 'Overtaken by Events'
2019-08-26	Gunter Van de Velde	Assignment of request for Telechat review by OPSDIR to Ron Bonica was marked no-response
2019-08-12	(System)	IANA registries were updated to include RFC8621
2019-08-08	(System)	Received changes through RFC Editor sync (created alias RFC 8621, changed title to 'The JSON Meta Application Protocol (JMAP) for Mail', changed abstract to … Received changes through RFC Editor sync (created alias RFC 8621, changed title to 'The JSON Meta Application Protocol (JMAP) for Mail', changed abstract to 'This document specifies a data model for synchronising email data with a server using the JSON Meta Application Protocol (JMAP). Clients can use this to efficiently search, access, organise, and send messages, and to get push notifications for fast resynchronisation when new messages are delivered or a change is made in another client.', changed pages to 108, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-08-08, changed IESG state to RFC Published, created updates relation between draft-ietf-jmap-mail and RFC 5788)
2019-08-08	(System)	RFC published