[JMAP] Re: New Version Notification for draft-ietf-jmap-blobext-01.txt

[Bron Gondwana <[e-mail]>]

This is reworked with:

"blob2" rather than "blobext"
Replaces blob
Blob/set rather than Blob/upload

Would love to have reviews on this approach - do you think this is better than extending the existing RFC9404?  Have I missed anything major?

Thanks,

Bron.

On Tue, Apr 21, 2026, at 11:29, [e-mail] wrote:
> A new version of Internet-Draft draft-ietf-jmap-blobext-01.txt has been
> successfully submitted by Bron Gondwana and posted to the
> IETF repository.
> 
> Name:     draft-ietf-jmap-blobext
> Revision: 01
> Title:    JMAP Blob Management
> Date:     2026-04-21
> Group:    jmap
> Pages:    41
> URL:      https://www.ietf.org/archive/id/draft-ietf-jmap-blobext-01.txt
> Status:   https://datatracker.ietf.org/doc/draft-ietf-jmap-blobext/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-jmap-blobext
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-ietf-jmap-blobext-01
> 
> Abstract:
> 
>    The JSON Meta Application Protocol (JMAP) base protocol ([JMAP-CORE])
>    provides the ability to upload and download arbitrary binary data via
>    HTTP POST and GET on a 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.  It also
>    adds a reverse lookup mechanism to discover where blobs are
>    referenced within other data types, support for large blobs via
>    chunked construction with server-side optimisation, and server-side
>    blob conversion operations including image format conversion, archive
>    creation and extraction, compression and decompression, and delta/
>    patch operations.
> 
> 
> 
> The IETF Secretariat
> 
> 
> 

--
  Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC
  [e-mail]