Re: [Jmap] Integrity checking of blobs

Bron Gondwana <brong@fastmailteam.com> Mon, 30 May 2022 00:48 UTC

Return-Path: <brong@fastmailteam.com>
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 5DF74C14F6EC for <jmap@ietfa.amsl.com>; Sun, 29 May 2022 17:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, 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=fastmailteam.com header.b=D5dJqS5G; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=rMXDfMhc
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 djg0bPfXBwPd for <jmap@ietfa.amsl.com>; Sun, 29 May 2022 17:48:47 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (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 28FD6C14F613 for <jmap@ietf.org>; Sun, 29 May 2022 17:48:46 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 69C5D32008FC for <jmap@ietf.org>; Sun, 29 May 2022 20:48:44 -0400 (EDT)
Received: from imap43 ([10.202.2.93]) by compute4.internal (MEProxy); Sun, 29 May 2022 20:48:44 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; 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=fm2; t=1653871723; x= 1653958123; bh=P+TbZPZGlfOC2DjfPw21susPp227UqesmdL23vr9eqo=; b=D 5dJqS5GLmMBdRx6yAXDQ9zrcxLzqBRIAKChegicp/E+KIlZt2zMDK9ISHXt+pLjj nFtds4eKpsnZr7lSOGoYORcLnvhImE9hkDwrblpswQ0eKdBLQwnK7J1EurCkMmSE 2EMuFsMORRk7EVT/SHnE3UFYsLgEdaKl2HXRWCg7w9ZMSr5yhoZhwEHlKxW8qx9Y 6RNCYnv6oHrGxvO2xlopUPSIPXXXdLokBeyKwn+vv63i6BG+dgGX8iAQwFBTAr+Q ff4+r4PKLb+THi2JA7sSgM8N3cWKXIb2RvrWKl9VyfCbA4UA7n9s9MkO2puP/7pw Gcc+DiHve4vQnIxySyLjA==
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=1653871723; x=1653958123; bh=P+TbZPZGlfOC2DjfPw21susPp227 UqesmdL23vr9eqo=; b=rMXDfMhcKa6vTwqfjXZ6k8dNR+2CxN186+3fLYAka+QJ narGFhsjL5JTQ1whaKImZGZ6ZRC3PFB/TQxoGvG5mU/kbdT37g4nQ5TRBG4XVyVU 0tZsXXe1eFhGVzU9jsCCaEDhh7ukbJqoKtT/VQaWtJJrpblwg7hrsk8/n2T6WV2+ 2E/GDodZjXMvgoTx6vz7gDDL+czM6RmcI/1cAbQR/Dzyj2V+pf1e6XsrM8scU9y1 4MzSfO1ecqOBM6kldk2+IIZp/rwi4iyXCfMjCrl9cWkybOSAiPUzXPRsY1BCsHMI LmkfQTmt2oVJL64fYiP3ZleYwCTBKP2HNKskrOUMrQ==
X-ME-Sender: <xms:axSUYgb0h557EpyRh9Z9t25LHHFhfWhZh4ImksM6Dzqd77ymhM2CJg> <xme:axSUYrZmnhZJ3BMP_4AgxwkpG7AYCzJrFcON5V263pM8Af1qxIXXR6snYaILUUZs0 BcM3EnM5BU>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrkeehgdefkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnhepffevfeeigfejve etheehleegteelteevgeeutdfhhefghfdtjefhvdehhfdtkefgnecuffhomhgrihhnpehi vghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:axSUYq-X4WzekciVLt7DSFaQnSAaazrcpVIExGn2Xe1mmMLT3cbbaw> <xmx:axSUYqo7jOZRmpvBHvfK4COg6vxj28f31JDBmdCdm6_VLGxFbZx37g> <xmx:axSUYrrnS9AZpyeBSWy8jttPDGBfFHZ9h5W1SSuaqg6qV_S-8gqD6w> <xmx:axSUYo2ZRGtIxnPdS2GKndE9r59TZqu_jh2oa_xZo9YtKRrttkgbXg>
Feedback-ID: i2d7042ce:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id A02092D4006D; Sun, 29 May 2022 20:48:43 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.7.0-alpha0-592-g9e92c28807-fm-20220523.001-g9e92c288
Mime-Version: 1.0
Message-Id: <eb0e0c4e-b217-47e4-aec6-da30a1395632@dogfood.fastmail.com>
In-Reply-To: <87sfoubmmr.fsf@eliza.sh>
References: <87sfoubmmr.fsf@eliza.sh>
Date: Mon, 30 May 2022 10:48:25 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: jmap@ietf.org
Content-Type: multipart/alternative; boundary="3397bc7b29324fabb41d020e01a4c859"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/MWU9rrObycwzs8sc1ncL2GvcLKM>
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 00:48:51 -0000

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