[JMAP] Re: Blobext: should it obsolete blob?
Mauro De Gennaro <mauro@stalw.art> Sat, 25 April 2026 08:27 UTC
Return-Path: <mauro@stalw.art>
X-Original-To: jmap@mail2.ietf.org
Delivered-To: jmap@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D1657E2D79E5 for <jmap@mail2.ietf.org>; Sat, 25 Apr 2026 01:27:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777105661; bh=1QLxSGPrMtmPRotaCZ2y9JHwnJd58cI8U6F6pyrby8o=; h=From:Subject:Date:References:To:In-Reply-To; b=WUnE8Cg4ce3jWI0O72HGPPVkciGozVnUZeF2kg9Waj5MLd2eGqNNTbC7gr+t/kmLU mRbpaMdqejbOtzAeKj1BwYGMda8RQAAwWbXAyRPRfDhkAXTT19/Q4xnxD+ep/qmcud hWT/LbWirPUQdACbpnvKQuAMJSTemzjrQN/r/Wf0=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=stalw.art header.b="3lvEmPLv"; dkim=pass (2048-bit key) header.d=stalw.art header.b="yvtFs3WW"
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OfsTVYm9OJP3 for <jmap@mail2.ietf.org>; Sat, 25 Apr 2026 01:27:41 -0700 (PDT)
Received: from mail.stalw.art (mail.stalw.art [135.181.195.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 57033E2D79DE for <jmap@ietf.org>; Sat, 25 Apr 2026 01:27:41 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; s=v1-ed25519-20260418; d=stalw.art; c=relaxed/relaxed; r=y; h=Message-Id:To:Date:Subject:From; t=1777105660; bh=eF8lg7CPqByYBbKHLbtNGlH BY272nPYqM80TNLkobmU=; b=3lvEmPLvKICUktRZ+Op9JVDNfx3w6XLgLHbVnPOyL4H69uRpNF TY+TIcgcIhP8afAcR5c9hlbz9v5LQHMj/jBg==;
DKIM-Signature: v=1; a=rsa-sha256; s=v1-rsa-20260418; d=stalw.art; c=relaxed/relaxed; r=y; h=Message-Id:To:Date:Subject:From; t=1777105660; bh=eF8lg7CPqByYBbKHLbtNGlH BY272nPYqM80TNLkobmU=; b=yvtFs3WWLrwY10T735a9hvCG7Mz11KsTrIP7fMWSx6n/A3iSu4 gvpRFGXG3euyO1tZxy8ol2GdWchChrI60yNziQuagIKLPRmBwiaRQUF1XmBVstJ99fwcRuZXDnx wlUowBoSADjZRXRr2KL9PneT2jr+GTbrkrc3ym70yD1VIlTzAZYjM2vfS7GeSYmUqNSDHPtLpjP ig6SD6gHt58WmQC4fWPcAOgVXPCLwBd71PZX/TGRh90+4Xsch0wwl0o4laRP3CeeHggWa04HKDF pt2PVSgS3FZ3e5kAinJWfbA1c6Y+MfnkAR7T8gg7N5F56xGtP/nGJ2ajEfFaPNjEjuA==;
From: Mauro De Gennaro <mauro@stalw.art>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0218CC0D-B7B8-4473-A6EF-2593D9E6BCB6"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
Date: Sat, 25 Apr 2026 10:27:29 +0200
References: <285f7f35-05ee-4f10-bfbd-2028fcc5bbb1@app.fastmail.com> <8a2a68e9-89cb-4dcf-a6b1-ffb7717e1515@dogfoodapp.fastmail.com>
To: JMAP IETF <jmap@ietf.org>
In-Reply-To: <8a2a68e9-89cb-4dcf-a6b1-ffb7717e1515@dogfoodapp.fastmail.com>
Message-Id: <FB58950D-7427-478C-B2E8-EFE3B7F2E51F@stalw.art>
X-Mailer: Apple Mail (2.3864.400.21)
Message-ID-Hash: RXL55AFBY7R3ABWNPWQUNJ3FIP4ZZI5O
X-Message-ID-Hash: RXL55AFBY7R3ABWNPWQUNJ3FIP4ZZI5O
X-MailFrom: mauro@stalw.art
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-jmap.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [JMAP] Re: Blobext: should it obsolete blob?
List-Id: JSON Meta Access Protocol <jmap.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/hu1lNrG6zEkJc38MOlk8ynHI378>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Owner: <mailto:jmap-owner@ietf.org>
List-Post: <mailto:jmap@ietf.org>
List-Subscribe: <mailto:jmap-join@ietf.org>
List-Unsubscribe: <mailto:jmap-leave@ietf.org>
Hi Bron, I also agree with the proposed changes. Best, Mauro > On 23 Apr 2026, at 07:21, Neil Jenkins <neilj=40fastmailteam.com@dmarc.ietf.org> wrote: > > On Tue, 14 Apr 2026, at 09:06, Bron Gondwana wrote: >> Make this document OBSOLETE the existing RFC9404, so move all the text from there into here. >> Change Blob/upload to be Blob/set - since it now has update and destroy as well. > > Yeah, I think both of these are reasonable. > > Cheers, > Neil. > _______________________________________________ > JMAP mailing list -- jmap@ietf.org > To unsubscribe send an email to jmap-leave@ietf.org
- [JMAP] Blobext: should it obsolete blob? Bron Gondwana
- [JMAP] Re: Blobext: should it obsolete blob? Neil Jenkins
- [JMAP] Re: Blobext: should it obsolete blob? Mauro De Gennaro
- [JMAP] Re: Blobext: should it obsolete blob? Bron Gondwana