Re: [ietf-smtp] Public Key Look Up

Alessandro Vesely <vesely@tana.it> Tue, 11 May 2021 11:48 UTC

Original-From: Alessandro Vesely <vesely@tana.it>
To: ietf-smtp@ietf.org
References: <20210508172602.CC09D72BE50@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <69c31dc0-f9b4-d983-e3e5-345773f27211@tana.it>
Date: Tue, 11 May 2021 13:48:20 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <20210508172602.CC09D72BE50@ary.qy>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/_4eR7MLnzmhAWvJ9IuYIw1FkO60>
Subject: Re: [ietf-smtp] Public Key Look Up
Precedence: list

On Sat 08/May/2021 19:26:02 +0200 John Levine wrote:
> It appears that John C Klensin  <john-ietf@jck.com> said:
>> FWIW, also note that ideas of putting user or mailbox names (not
>> just host names) into the DNS to support a variety of things has
>> been around since the early design of the DNS.
> 
> I'd forgotten about RFC 7929 which purports to put PGP keys
> in the DNS.  [...]
> 
>> I want to stress that I don't think this is a terrible idea,
>> especially if it were used to retrieve keys for S/MIME or PGP
>> use rather than inventing yet another mechanism.
> 
> I think it's a terrible idea both because it puts the keys in the wrong
> place and the reasons you gave, extensions are optional which means
> not implemented.


I'm not clear why a domain's MX would be the wrong place.  A similar idea is to 
store the keys at a domain's well-known place, so as to get them via https. 
The draft also includes a mail-based protocol to update the web key directory.

https://datatracker.ietf.org/doc/html/draft-koch-openpgp-webkey-service


Best
Ale
--

Re: [ietf-smtp] Public Key Look Up Jeremy Harris
[ietf-smtp] Public Key Look Up patrick.peisker
Re: [ietf-smtp] Public Key Look Up John Levine
Re: [ietf-smtp] Public Key Look Up John C Klensin
Re: [ietf-smtp] Public Key Look Up John C Klensin
Re: [ietf-smtp] Public Key Look Up John Levine
Re: [ietf-smtp] Public Key Look Up Dave Crocker
Re: [ietf-smtp] Public Key Look Up Alessandro Vesely
Re: [ietf-smtp] Public Key Look Up John Levine
Re: [ietf-smtp] Public Key Look Up John C Klensin
Re: [ietf-smtp] Public Key Look Up Alessandro Vesely
Re: [ietf-smtp] Public Key Look Up Dave Crocker
Re: [ietf-smtp] Public Key Look Up John R Levine
Re: [ietf-smtp] Public Key Look Up Valdis Kl ē tnieks
Re: [ietf-smtp] Public Key Look Up Alessandro Vesely
Re: [ietf-smtp] Public Key Look Up Alessandro Vesely
Re: [ietf-smtp] Public Key Look Up John C Klensin
Re: [ietf-smtp] Public Key Look Up John C Klensin
Re: [ietf-smtp] Public Key Look Up Dave Crocker
Re: [ietf-smtp] Public Key Look Up Dave Crocker
Re: [ietf-smtp] Public Key Look Up Ned Freed
Re: [ietf-smtp] Public Key Look Up John C Klensin
Re: [ietf-smtp] Public Key Look Up Alessandro Vesely
Re: [ietf-smtp] Public Key Look Up Alessandro Vesely
Re: [ietf-smtp] Public Key Look Up Richard Clayton
Re: [ietf-smtp] Public Key Look Up Matthias Leisi
Re: [ietf-smtp] Public Key Look Up John C Klensin
Re: [ietf-smtp] Public Key Look Up John R Levine
Re: [ietf-smtp] Public Key Look Up John Levine
Re: [ietf-smtp] Public Key Look Up Gene Hightower
Re: [ietf-smtp] Public Key Look Up Gene Hightower
Re: [ietf-smtp] Public Key Look Up John Levine
Re: [ietf-smtp] Public Key Look Up Gene Hightower
Re: [ietf-smtp] Public Key Look Up John C Klensin
Re: [ietf-smtp] Public Key Look Up Matthias Leisi
Re: [ietf-smtp] Public Key Look Up John Levine
Re: [ietf-smtp] Public Key Look Up patrick.peisker