Skip to main content

JMAP Guide for Migration and Data Portability
draft-baum-jmap-portability-guide-00

Document Type Replaced Internet-Draft (candidate for jmap WG)
Expired & archived
Authors Joris Baum , Hans-Jörg Happel
Last updated 2023-11-14 (Latest revision 2023-11-10)
Replaces draft-baum-jmap-portability
Replaced by draft-ietf-jmap-portability-guide, draft-ietf-jmap-essential
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Associated WG milestone
Jun 2024
Submit Portability Guide (Minimal Profile) to IESG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-jmap-essential, draft-ietf-jmap-portability-guide
Consensus boilerplate Unknown
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:

Abstract

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.

Authors

Joris Baum
Hans-Jörg Happel

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