JMAP Blob management extension
draft-gondwana-jmap-blob-02
| Document | Type |
Replaced Internet-Draft
(jmap WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Bron Gondwana | ||
| Last updated | 2021-07-11 | ||
| Replaced by | draft-ietf-jmap-blob | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Associated WG milestone |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-jmap-blob | |
| 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
The JMAP base protocol (RFC8620) provides the ability to upload and download arbitrary binary data via HTTP PUT and GET on defined endpoint. This binary data is called a "Blob". This extension adds additional ways to create and access Blobs, by making inline method calls within a standard JMAP request. This extension also adds a reverse lookup mechanism to discover where blobs are referenced within other datatypes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)