Skip to main content

JMAP for Migration and Data Portability

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Joris Baum , Hans-Jörg Happel
Last updated 2023-10-08 (Latest revision 2023-04-06)
Replaced by draft-baum-jmap-portability-guide
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Associated None milestone
Dec 2023
Adopt a draft for a basic migration simplified endpoint
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-baum-jmap-portability-guide
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


JMAP (RFC8620) is a generic, efficient, mobile friendly and scalable protocol that can be used for data of any type. This makes it a good fit for migrations or data portability use cases. However, due to its large set of features, it is also quite complex, which makes it difficult to explore new application domains in practice. The goal of this document is to provide guidelines on implementing essential parts of JMAP for a much lower entry barrier and more efficient implementation of the protocol.


Joris Baum
Hans-Jörg Happel

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)