Skip to main content

JMAP Backend Information
draft-baum-jmap-backend-info-00

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-extensions
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Associated None milestone
Dec 2023
Adopt a document for Server info and debug
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-baum-jmap-portability-extensions
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

It is likely that any JMAP implementation has either bugs or intentionally deviates from the standard. To cope with such a unique behavior, JMAP clients need to identify the software behind the JMAP endpoint and apply custom logic. This specification defines the ability to provide details about the product, backend and environment for JMAP servers.

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.)