[DNSOP] Re: [art] Re: DNS-designated Public Key Authorities (DKA)
John R Levine <johnl@ietf.email> Fri, 26 June 2026 21:49 UTC
Return-Path: <johnl@ietf.email>
X-Original-To: dnsop@mail2.ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id DD7181086ECD9 for <dnsop@mail2.ietf.org>; Fri, 26 Jun 2026 14:49:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782510572; bh=NJMAKE83mLP+hMyMEpdczDGErWbWKhggSUSViI5WEh8=; h=Date:From:To:Cc:Subject; b=zBGKBdRPZv9QTGBNtpGnjh3R4yHEv2tCHkgA7+JA7EzxwHg5rP98/69oHV4aFg4is pB08ROyIs0/awiDXWU4I5SFLm1E99VdSXtb+z1eccF6b7MJlvrt0bu/PmUVGKR6ofH ms2jbekiw/pzYxh/XXG08qGJ3lCgXJ+mHKEP6Ylg=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.401
X-Spam-Level:
X-Spam-Status: No, score=-4.401 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, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="gQSoU47r"; dkim=pass (2048-bit key) header.d=ietf.email header.b="YIeJcVKN"
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vet4WF9NDt3W for <dnsop@mail2.ietf.org>; Fri, 26 Jun 2026 14:49:30 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A3B4910863B84 for <dnsop@ietf.org>; Fri, 26 Jun 2026 14:35:33 -0700 (PDT)
Received: (qmail 37952 invoked from network); 26 Jun 2026 21:35:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:mime-version:content-type:content-transfer-encoding; s=943c6a3ef0a4.k2606; t=1782509722; x=1782855322; bh=NJMAKE83mLP+hMyMEpdczDGErWbWKhggSUSViI5WEh8=; b=gQSoU47rED+pXn6xXAitXN2Kl+L7+8RWNp/b3LHHwfP7VzrYnAUdJUfcOudkUAOGT5rP7akrl0v6D4TjofCaMiRnCBamgIlS0pQLsJ8lGAysz0c5NwN1n0EsV/EplMqci1gW9yLCpnvGH142vJFqea6RzODa73a99VWyJEqSsB3FwG2wq2TUuQg8VHV+qwFELu+KwNFuLECgJd4hPACAvx2HH15zxgo1Y4tYsF7tIPBkq9yz/bNyYLnps5kQjerSauQ/vu8t/NSg//VviB5TLV3+R0BrgySb2s5xRbb8NTqMgicJZhQD3IzkHcTonSo4ThMee/ilAHqyB7NL6kK27Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=ietf.email; h=date:message-id:from:to:cc:subject:mime-version:content-type:content-transfer-encoding; s=943c6a3ef0a4.k2606; bh=NJMAKE83mLP+hMyMEpdczDGErWbWKhggSUSViI5WEh8=; b=YIeJcVKNM0wI5lYeIluk10YVjIbPc2FLC2VfYao51m2ekNfQ/az6jNLiBIuQ+5OaiDOA7OTL44Aqdp1sVo4YAh6w0cd1YJIRb456ZXLlvUgguIs9tKUVNzlA6UWkpBrFwubcw92d1ZAmKuLMLrrV/6zBaCnTHAdFO+eqVp0nVYDgMNEVfdTmnYCjQ9xIcuIlDwcuGXfB4gAeiNxCuu+udMpRciKLOT5FC787LotMDnS01gwqpKnOPlSzY3RAj21UdpYyzFM0hwL/yrUJ1tYJ2eW81EcMWtGwBB2Xsy3aLc578Gkm6Zrepn0Tc6Jc2zRyEOjWBVslbpXy6ARqXkt2CA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 26 Jun 2026 21:35:32 -0000
Received: by ary.qy (Postfix, from userid 501) id 3E47911227E7C; Fri, 26 Jun 2026 17:35:31 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 7E14611227E5E; Fri, 26 Jun 2026 17:35:31 -0400 (EDT)
Date: Fri, 26 Jun 2026 17:35:31 -0400
Message-ID: <13955a81-ae6c-c803-b666-85e7aeb02691@ietf.email>
From: John R Levine <johnl@ietf.email>
To: Bob Traverz <bob.traverz@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: A4HOLDNTYWF3VZEWBCWLDNIUOJBQ2NGV
X-Message-ID-Hash: A4HOLDNTYWF3VZEWBCWLDNIUOJBQ2NGV
X-MailFrom: johnl@ietf.email
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Ben Schwartz <bemasc@meta.com>, art@ietf.org, dnsop@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: [art] Re: DNS-designated Public Key Authorities (DKA)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0EKubhj-yN-8PsNSucccjirO5n0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>
On Fri, 26 Jun 2026, Bob Traverz wrote: >> Indeed. MTA-STS is basically an end run around DNSSEC TLSA, because at >> least one large mail provider doesn't sign its DNS. > > I can see that. Did that email provider implement MTA-STS? $ curl https://mta-sts.gmail.com/.well-known/mta-sts.txt version: STSv1 mode: enforce mx: smtp.google.com mx: gmail-smtp-in.l.google.com mx: *.gmail-smtp-in.l.google.com max_age: 86400 % curl https://mta-sts.outlook.com/.well-known/mta-sts.txt version: STSv1 mode: enforce mx: *.olc.protection.outlook.com max_age: 604800 $ curl https://mta-sts.yahoo.com/.well-known/mta-sts.txt version: STSv1 mode: testing mx: *.am0.yahoodns.net mx: *.mail.gm0.yahoodns.net mx: *.mail.am0.yahoodns.net max_age: 86400 $ curl https://mta-sts.comcast.net/.well-known/mta-sts.txt version: STSv1 mode: enforce mx: mx2c1.comcast.net mx: mx2h1.comcast.net mx: mx1a1.comcast.net mx: mx1h1.comcast.net mx: mx1c1.comcast.net mx: mx2a1.comcast.net mx: mx1.ge.comcast.net mx: mx2.ge.comcast.net mx: mx1.mxge.comcast.net mx: mx2.mxge.comcast.net > > Regards, > > Bob Traverz > > > On Fri, Jun 26, 2026 at 12:51 PM John R Levine <johnl@ietf.email> wrote: > >> On Fri, 26 Jun 2026, Bob Traverz wrote: >>> With respect to the DKA discussion, I’d run the “edge-case” test to test >> if >>> a proposed architecture makes sense. Does a domain, to have a DKA, >>> necessarily require a website or other HTTPS assets? If not, there is no >>> inherent dependency between a website and a DKA. Forcing a domain to have >>> an “A” record designating a Https resource just to run a .well-known URL >>> that delivers another endpoint is simply an end-run around the DNS. Feels >>> like a hack rather than a well-designed architecture. >> >> Indeed. MTA-STS is basically an end run around DNSSEC TLSA, because at >> least one large mail provider doesn't sign its DNS. >> >> You know, all you really need to do is pick a name like dka-server and say >> that the server for example.com is at https://dka-server.example.com. >> All >> done. If you want to outsource your key server to a shared service, you >> know what CNAMEs are. >> >> R's, >> John >> > Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Bob Traverz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… S Kishore
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… John C Klensin
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Bob Traverz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Jim Mozley
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… S Kishore
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… John R Levine
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… John C Klensin
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Paul Kyzivat
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Ben Schwartz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Ben Schwartz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Ondřej Surý
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Ben Schwartz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… S Moonesamy
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… S Moonesamy
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Ondřej Surý
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… S Kishore
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Ben Schwartz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… John Levine
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… John R Levine
- [DNSOP] DNS-designated Public Key Authorities (DK… S Kishore
- [DNSOP] Re: DNS-designated Public Key Authorities… Ben Schwartz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… John Levine
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Paul Kyzivat
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… John R Levine
- [DNSOP] dnssec (Was: Re: [art] DNS-designated Pub… Steffen Nurpmeso
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… S Kishore
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… S Kishore
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Salz, Rich
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… S Kishore
- [DNSOP] Re: [art] Re: Re: DNS-designated Public K… Bob Traverz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Bob Traverz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Ben Schwartz
- [DNSOP] Re: DNS-designated Public Key Authorities… Patrik.Graser@jordbruksverket.se
- [DNSOP] Re: DNS-designated Public Key Authorities… John R Levine
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… John R Levine
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Bob Traverz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… John R Levine
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Bob Traverz
- [DNSOP] Re: [art] Re: DNS-designated Public Key A… Bob Traverz