Re: [ietf-smtp] Public Key Look Up

Dave Crocker <dhc@dcrocker.net> Mon, 10 May 2021 19:09 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EA7D3A2796 for <ietf-smtp@ietfa.amsl.com>; Mon, 10 May 2021 12:09:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.754
X-Spam-Level:
X-Spam-Status: No, score=-0.754 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, NICE_REPLY_A=-0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5GVe--UWP3uq for <ietf-smtp@ietfa.amsl.com>; Mon, 10 May 2021 12:09:25 -0700 (PDT)
Received: from beige.elm.relay.mailchannels.net (beige.elm.relay.mailchannels.net [23.83.212.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B01D3A2793 for <ietf-smtp@ietf.org>; Mon, 10 May 2021 12:09:24 -0700 (PDT)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 76F3222E19 for <ietf-smtp@ietf.org>; Mon, 10 May 2021 19:09:23 +0000 (UTC)
Received: from nl-srv-smtpout3.hostinger.io (100-96-133-96.trex.outbound.svc.cluster.local [100.96.133.96]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 7650622C9F for <ietf-smtp@ietf.org>; Mon, 10 May 2021 19:09:22 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout3.hostinger.io ([UNAVAILABLE]. [145.14.159.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256) by 100.96.133.96 (trex/6.2.1); Mon, 10 May 2021 19:09:23 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Tasty-Soft: 3522ff0041fb52fc_1620673762976_3431086675
X-MC-Loop-Signature: 1620673762976:2122649794
X-MC-Ingress-Time: 1620673762976
Received: from [192.168.0.111] (c-24-130-56-204.hsd1.ca.comcast.net [24.130.56.204]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout3.hostinger.io (smtp.hostinger.com) with ESMTPSA id 8689D31F6607 for <ietf-smtp@ietf.org>; Mon, 10 May 2021 19:09:20 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1620673760; bh=qDftPxAoqYYv5DBa1RYmLULRwc115mtmy8E8n+ZeHJY=; h=Reply-To:Subject:To:References:From:Date:In-Reply-To; b=svF9M8ZRptlXy88dMOLBOleeRObUHXRuLuZK+eazDkNH+Bz+w3ME3AU5k/TL5LV1+ JNll7fZ5cPmlK6R4cmJ4ErZKEntoYE//KI/5Z8ufUkP7vB8SO3ZIlGGaIyboBuB01o ayk72qwtVSkV07mpdzrCMHRFDgnKAhz+LFTO23/1JUwvk1JSRQg2EswpIYv3vPQXyt /OwhPVSxqwMFJkndJXzvq9iQn2IjPV0HWIlCFNUGEvzNlOWIHOXIKvhZpRYQKhz/FV +WJ/ZBse81hetS2xOSnYp4oDt76udZB/uRUFwj6B2SBSxmeCGaIp0+O4H6vLE64G5P ibqGodngN2YnA==
Reply-To: dcrocker@bbiw.net
To: ietf-smtp@ietf.org
References: <20210508172602.CC09D72BE50@ary.qy>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <21c6743c-c909-2c6a-6ad7-e61b0fe3bc4f@dcrocker.net>
Date: Mon, 10 May 2021 12:09:18 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <20210508172602.CC09D72BE50@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/Jw2lWTG6Zi_O-XyjZFsNl1ve440>
Subject: Re: [ietf-smtp] Public Key Look Up
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 May 2021 19:09:30 -0000

On 5/8/2021 10:26 AM, John Levine wrote:
> Right.  This idea has failed plenty of times already.


As I recall, at least one perceived problem with the dramatic difference 
in scale between querying for a host versus query for a user.

I recently noted that Shaken/Stir requires a cert per phone number, 
which seems a rather larger scale of real-world use than certs have 
otherwise gotten, to date.  Not sure how many orders of magnitude 
difference, but likely more than one.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net