Protocol Action: 'JMAP Blob management extension' to Proposed Standard (draft-ietf-jmap-blob-18.txt)

The IESG <iesg-secretary@ietf.org> Wed, 18 January 2023 02:58 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'JMAP Blob management extension' to Proposed Standard (draft-ietf-jmap-blob-18.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, draft-ietf-jmap-blob@ietf.org, fenton@bluepopcorn.net, jmap-chairs@ietf.org, jmap@ietf.org, rfc-editor@rfc-editor.org, superuser@gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <167401073378.6093.8675515965867046717@ietfa.amsl.com>
Date: Tue, 17 Jan 2023 18:58:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/zVmm7EwKavDCN1gbhXABx9B22eo>

The IESG has approved the following document:
- 'JMAP Blob management extension'
  (draft-ietf-jmap-blob-18.txt) as Proposed Standard

This document is the product of the JSON Mail Access Protocol Working Group.

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-jmap-blob/





Technical Summary

   The JMAP base protocol (RFC8620) provides the ability to upload and
   download arbitrary binary data via HTTP POST 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 data types.

Working Group Summary

This document represents the consensus of the jmap working group. While the
working group is small, this document did attract comment from several
individuals associated with different organizations.

One known implementation exists for Cyrus. Other implementers, notably
Fastmail, are expected to implement soon. Existing JMAP implementations are
listed at the community site jmap.io, but since this is an extension to
existing "blob" functions, the features in this particular draft are not
mentioned there.

There are no necessary yet outstanding reviews.

Personnel

Jim Fenton is the document shepherd.
Murray Kucherawy is the responsible Area Director.

Protocol Action: 'JMAP Blob management extension'… The IESG