Re: [ietf-smtp] Public Key Look Up

John Levine <johnl@taugh.com> Tue, 11 May 2021 18:55 UTC

Date: Tue, 11 May 2021 14:55:42 -0400
Message-Id: <20210511185543.C751179052B@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: vesely@tana.it
In-Reply-To: <69c31dc0-f9b4-d983-e3e5-345773f27211@tana.it>
Organization: Taughannock Networks
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/3Ag2G2Wq4MkE068hjNS-MVwBf8I>
Subject: Re: [ietf-smtp] Public Key Look Up
Precedence: list

It appears that Alessandro Vesely  <vesely@tana.it> said:
>> 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.

Because you can't tell the user's relation to the domain.  Would you
want Google to be the authoritative source of keys for every gmail
user?  Apollo Global Management for every Yahoo and AOL user?

Personally, as a passive-aggressive mail system operator, the only keys
my MX would publish would be proxy ones that let my MTA decode the
mail and do spam and malware filtering.  If my users don't like that,
they can manage their own fripping keys.

R's,
John

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