RFC 8620: The JSON Meta Application Protocol (JMAP)
In plain English — editorial summary, not part of the RFC
This document specifies a protocol for clients to efficiently query, fetch, and modify JSON-based data objects, with support for push notification of changes and fast resynchronisation and for out-of- band binary data upload/download.
Document record
- Document ID
- RFC8620
- Published
- July 2019
- Authors
- N. Jenkins; C. Newman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 90
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8621The JSON Meta Application Protocol (JMAP) for MailCurrent
August 2019
- RFC 9007Handling Message Disposition Notification with the JSON Meta Application Protocol (JMAP)Current
March 2021
- RFC 9425JSON Meta Application Protocol (JMAP) for QuotasCurrent
June 2023
- RFC 9610JSON Meta Application Protocol (JMAP) for ContactsCurrent
December 2024
- RFC 9661The JSON Meta Application Protocol (JMAP) for Sieve ScriptsCurrent
September 2024
- RFC 8742Concise Binary Object Representation (CBOR) SequencesCurrent
February 2020
- RFC 8746Concise Binary Object Representation (CBOR) Tags for Typed ArraysCurrent
February 2020
- RFC 8949Concise Binary Object Representation (CBOR)Current
December 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?