IETF Logo Mail Archive

Re: [Jmap] Integrity checking of blobs

Eliza Velasquez <eliza@eliza.sh> Mon, 30 May 2022 23:05 UTC

Return-Path: <eliza@eliza.sh>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77333C1A7F2E for <jmap@ietfa.amsl.com>; Mon, 30 May 2022 16:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.11
X-Spam-Level:
X-Spam-Status: No, score=-7.11 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=eliza.sh header.b=rz9SFfNE; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ICX3Ztf0
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N4W_XCIOtuJz for <jmap@ietfa.amsl.com>; Mon, 30 May 2022 16:05:03 -0700 (PDT)
Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC44BC1A7F2A for <jmap@ietf.org>; Mon, 30 May 2022 16:05:02 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id 0EA325802D7; Mon, 30 May 2022 19:05:02 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 30 May 2022 19:05:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eliza.sh; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1653951902; x=1653955502; bh=rZ8rBLIMEh hUAziPi3j9Ox4Rw5Ib/s5zDwVsue2qJN8=; b=rz9SFfNETzcgmQcoiWUiNzEtO9 jrMWnsEBZ6/qedB9iVMSEDaI0ppWl5Vn9TCNFJd6P1PbmuWIxqpv4u3TLlFH8jlG JLysNffsPvNjq6mvKil3FRKKNa9Q/QxgKoSGJbSW/aRoEiy9iyDxhu+wG2khQqLH f2rJmAz8qZsQ0OAprNjhiTsWOJ4ilwklzjA8g56Un1XNGD42iUAiHLJmPD+PWrmM Alh5fCo9iixNYOugzaC8XZozdmJ1OiVyR2SK9s1x+XkmK0sKe6C3LjmOmspVltRG HGN8xPCyd29VaqpnFGU2LeIbCDut+YMl2DxPYF37Y2E/dFm7ar35FKV1wd9g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1653951902; x=1653955502; bh=rZ8rBLIMEhhUAziPi3j9Ox4Rw5Ib /s5zDwVsue2qJN8=; b=ICX3Ztf0pwQOI/VrILZN5NYfmx2uRwD3OSgiD1Fk4MLP AwhvjXUoUebbWRNkrv4wKJBQfZYMckc1H8Ns1KCmuwCvm65erxvju0Hf743DTU6t VGYV6sS0J4wHJWDscmLFER7OORVQz9MzDf4ThnSe8VL1Zg8vPnFmn+QUpsdzNh1M tn3znDqmtf/sF2EcEmhWkbi0kg31Rpo1+GvUriNNmBABKp7QfF/ZTRIWJWX9njuU osxwz7FvVeysLFwwwMZu3x0IektwhUT6xfd4Jhl/eL64jCp+wb+0H2F1cYIzdR6X VbeVCVgNgit76di5VxMw6P7Sp9prm55VCNbUoYstxA==
X-ME-Sender: <xms:nU2VYnUj2McnPxeD5o2meqe-0qRVCVf3DMLQc094FvbbpBbWjNwMuQ> <xme:nU2VYvlStLQTV9nnYAhTPqdMDdP7A-j255pWG0jMBUxgcGBEGjhY6VG4hFQRJtG_g Sh_XsOg5CHDB1GAPmc>
X-ME-Received: <xmr:nU2VYjZiP1acBz2814afCBGemoyAU_rsIFKxbFkSEIOAn4hP7lI06UFYC0OckQZfLva_iNoie8a9ClAZGpthz3e9>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrkeejgddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffujghffffkgggtsehttdertddttddtnecuhfhrohhmpefglhhiiigrucgg vghlrghsqhhuvgiiuceovghlihiirgesvghlihiirgdrshhhqeenucggtffrrghtthgvrh hnpedvteekiedvleeukedukeevhfeuhfegueeuhfdukeeliedutdetjeeivdfhvddvheen ucffohhmrghinhepihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomhepvghlihiirgesvghlihiirgdrshhh
X-ME-Proxy: <xmx:nU2VYiXB5E2RdXDy4kWEOw1Aa-0uH8igW_FGdToQ3I5qCb9LFwnXcg> <xmx:nU2VYhk_TRB9L_5AqwQk3ADCMvwNZXfbVnGH0toiHPIV-FpQNAp4Aw> <xmx:nU2VYvfvhrFqOF2ig4M9uCEgpL11AM09T8EFO--CE_LbgLevsqlz6A> <xmx:nU2VYgtQRmBoMu8lyOHqXPQsTMrSFGquC7BqetXVlDJdXg-BYZHSGw>
Feedback-ID: i87c446d8:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 30 May 2022 19:05:01 -0400 (EDT)
From: Eliza Velasquez <eliza@eliza.sh>
To: Bron Gondwana <brong@fastmailteam.com>, jmap@ietf.org
In-Reply-To: <eb0e0c4e-b217-47e4-aec6-da30a1395632@dogfood.fastmail.com>
References: <87sfoubmmr.fsf@eliza.sh> <eb0e0c4e-b217-47e4-aec6-da30a1395632@dogfood.fastmail.com>
Date: Mon, 30 May 2022 16:05:00 -0700
Message-ID: <878rqi7hb7.fsf@eliza.sh>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/IaGJvwARncbOMvrn-mcObVZ_E04>
Subject: Re: [Jmap] Integrity checking of blobs
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2022 23:05:07 -0000

Oh, that's great! Is this something I can contribute to? I'm afraid I
have no experience when it comes to the IETF RFC process.

On Mon, May 30 2022 at 10:48 +10, "Bron Gondwana" <brong@fastmailteam.com> wrote:

> I'm working on a draft for blob extensions right now... I could easily add such a thing!
>
> https://datatracker.ietf.org/doc/draft-ietf-jmap-blob/
>
> It does make sense to add actually - as an additional piece of capability which lists the digests available, and having them as a fetchable property.
>
> Cheers,
>
> Bron.
>
> On Sat, May 28, 2022, at 09:07, Eliza Velasquez wrote:
>> Hello jmap,
>> 
>> While implementing a JMAP client which is designed to download and
>> maintain a cache of every message file on the server, I was somewhat
>> surprised to discover that there appears to be nothing built into the
>> specification to determine a checksum for a given blob ID. I assume JMAP
>> mail servers or reverse proxies they sit behind might implement the HTTP
>> Digest header for a blob GET request, but that would necessitate that a
>> client perform a large number of GET requests for every message in its
>> cache, and the design of JMAP seems built around avoiding this sort of
>> thing.
>> 
>> I was expecting something along the lines of a `Blob/get' method which
>> can return a sha256 sum of a given blob ID. Is this something that I
>> missed while reading the spec, or is this something that would have to
>> be added to a new RFC? Also, is there any interest in the community for
>> such a feature?
>> 
>> -- 
>> Eliza
>> 
>> _______________________________________________
>> Jmap mailing list
>> Jmap@ietf.org
>> https://www.ietf.org/mailman/listinfo/jmap
>> 
>
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com
>
> _______________________________________________
> Jmap mailing list
> Jmap@ietf.org
> https://www.ietf.org/mailman/listinfo/jmap

-- 
Eliza

v2.23.0 | Report a Bug | By Email