IETF Logo Mail Archive

Re: [dispatch] Work for IETF114

Bron Gondwana <brong@fastmailteam.com> Thu, 16 June 2022 09:17 UTC

Return-Path: <brong@fastmailteam.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85F37C13C2D2 for <dispatch@ietfa.amsl.com>; Thu, 16 Jun 2022 02:17:18 -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=dkx0crEk; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=r9zBlSZE
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 EsC_QUjQIGys for <dispatch@ietfa.amsl.com>; Thu, 16 Jun 2022 02:17:13 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 1FC14C15D894 for <dispatch@ietf.org>; Thu, 16 Jun 2022 02:16:53 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 5C0225C08C1 for <dispatch@ietf.org>; Thu, 16 Jun 2022 05:16:52 -0400 (EDT)
Received: from imap43 ([10.202.2.93]) by compute4.internal (MEProxy); Thu, 16 Jun 2022 05:16:52 -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=fm3; t=1655371012; x= 1655457412; bh=pQkMupom/Qi77WxxQ5caEnQa6GHXjhlqlMlEKQuTSf0=; b=d kx0crEkqUuZT61Bn+Tbc0MEw+0JVlcKF4OnsyvonMf7boMpxLtfgz3S+HwhMwbfr i+J7YrLYM6O1EtzK0ayLXAe8v32G45HCiYuzPlS3BqfK2aW7myaZWR1U3/w0Cgq5 sQOPSM7eUtcc4d/SEB1bgFwoiDHn75ue/ut9qWsC/WZrYRIFabRRDMs6u5IzSgKD arj171dy+Lo+3J/0O+YJNOI2Q4Zq7uPvoQDzYzzT2fPqB4HKGq9MLMxvCLg5kgDi JumlkI9vZgnZn2qCPPnv3q3yroUK05jFllhr9OMFtMgdWEtKo7xwltrq9C78GjEm poIGNMcGH+W5XIvg3LOUQ==
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= fm2; t=1655371012; x=1655457412; bh=pQkMupom/Qi77WxxQ5caEnQa6GHX jhlqlMlEKQuTSf0=; b=r9zBlSZEQpbaAWCT8pW19uiAYTfHhYVTk/8h3WPVMEs7 Z35lKzy2qJ+UKm5iUOjMqn2+FNc+2cI45zOblZTLjnWklKbMkjr8qg7Mg51O36b+ fc3vdEDhg2jBeSdFmpAMo5taRg6F8BGZxhZHJumj0XQ9aDmSphea0rcudUVSbyVv mb+eiwPr5UARG0c0Mll9knCyCP2A9I7OblkXJ5GP8aOpkWOLuEfaGkzpGraS2d4P CaphbgWZdxcdMhkyDXcFyaAvuLy1oFk5DY/nE6z8aKrEuGluEgpBmh8eEgMy64aj v8GDJTBRYifQ51Rfx359iZv9Yg7uTwbX6bJ2Fh4NDw==
X-ME-Sender: <xms:BPWqYnFoCzUyi2gBa3esAfDPBeji7fjlgSixKCQZ_ps9ZOL2j6FiAg> <xme:BPWqYkUa02Mfol7FaVigG3St5k2Qafrs2tZB3lsE01W8rCLw_a9e2NaJuUc8LhAB5 YSXh8wvviM>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedruddvfedgtdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerreejnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpedtheetgeefve etudffveetheffgfehhfdvveekuefhheeuteduhefggeeikeejteenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhhonhhgsehfrghsthhmrg hilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:BPWqYpKFeC-qKfBNaE2xUPm549PCglh-8kKRoQJ3E68ll3V4fsgjrw> <xmx:BPWqYlF3zYFmZQniaUs24jNAsrkyVEM9aJkazOLobP886zyEnHSQEg> <xmx:BPWqYtVXnlaRKUDLlxNL5t5d87Zg6iBCY7NYFjwy9PYW2Uon3bL-2Q> <xmx:BPWqYlgQ_L8X6KBdSblmDnuV_uXoEpMv3mq22w3Ygik_HW1fUKVlww>
Feedback-ID: i2d7042ce:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 042662D40071; Thu, 16 Jun 2022 05:16:52 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.7.0-alpha0-712-gb9e94258b0-fm-20220610.001-gb9e94258
Mime-Version: 1.0
Message-Id: <eb1a696c-b0b8-4ca4-bf47-93e6d3a824e0@www.fastmail.com>
In-Reply-To: <CAHBU6isW95meqLdM5DNj0T12oG8j=E4tufuxC-vxJKL1DtyraQ@mail.gmail.com>
References: <ec38343d-6c89-4c8a-82c0-484375bd89b1@www.fastmail.com> <CAHBU6iuKpV-GTyOTHaytg9_MxDtrNNuSF88WWsTp3wfLmpfsQQ@mail.gmail.com> <5639B870-AC11-4111-B58A-BC02E7172D7C@mnot.net> <CAHBU6ivOnYghs8OVnuSM2_qt5ypTyXjG3E2ZEG3Zb4Qd1CCx4Q@mail.gmail.com> <b8720cce-5312-4320-874d-afad8db3721c@beta.fastmail.com> <CAHBU6isW95meqLdM5DNj0T12oG8j=E4tufuxC-vxJKL1DtyraQ@mail.gmail.com>
Date: Thu, 16 Jun 2022 19:16:31 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="f0aac83eb8d9491a9de441097c0f3828"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/2NoIms42dYS1gS9ByTxE1BrQiKw>
Subject: Re: [dispatch] Work for IETF114
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2022 09:17:18 -0000

On Thu, Jun 16, 2022, at 12:48, Tim Bray wrote:
> On Wed, Jun 15, 2022 at 7:19 PM Martin Thomson <mt@lowentropy.net> wrote:
> 
>>  I am not sure about use of key identifiers vs. keys.
> 
> D'oh, if you're going to send the URI over a secure channel you could just put the key right there in the fragment (*cough* ed25519 *cough*). And arguably you shouldn’t be doing this kind of thing without a secure channel. After all, in Bron's scenario you're emulating the semantic of a (presumably unencrypted) attached file.

Yes - so the protection is at the same level as the content of the email, which is hopefully begin transferred over secure channels - but we should allow that to be a policy decision for the lower layer rather than adding more complexity than necessary to the URI format.

Bron.
--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com

v2.46.0 | Report a Bug | By Email | System Status