JMAP Migration and Portability Extensions
draft-baum-jmap-portability-extensions-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-debug, draft-baum-jmap-backend-info | ||
| Replaced by | draft-ietf-jmap-portability-extensions | ||
| 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 |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-jmap-portability-extensions | |
| 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. This extension adds additional features useful (but not limited to) those use cases. It adds a feature exposing details about the product, backend and environment of a JMAP server. It also adds a data model for extending the JMAP Response with log messages, particularly helpful for debugging.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)