IETF Logo Mail Archive

[DNSOP] Re: Client authentication for encrypted DNS — interest check

Philip Homburg <pch-dnsop-7@u-1.phicoh.com> Fri, 10 July 2026 15:45 UTC

Return-Path: <pch-b55F8B228@u-1.phicoh.com>
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 569421149BB84 for <dnsop@mail2.ietf.org>; Fri, 10 Jul 2026 08:45:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783698322; bh=jVWzZdrhqprtZ2M24NE6TlHwl4YKJfD8V+6aFjjB4Ic=; h=To:Cc:Subject:From:References:In-reply-to:Date; b=HqzW+zK1kzaj4ITl8eEEWlMLumhcLckRPULFw4P6l0horZ/v5ipQs35bpb1iqPdBE 2NkxSPYWFNYB2S8PKrFJp5KHbTe+Jb3XtXO1/9ooiK7GwM7IwmwQskT2d61Lb0AC8f Ncsf0F6GL0IeSQfKUWQEtrGls4kKQNKk8NCO1ynY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 L32C-lpSmk6V for <dnsop@mail2.ietf.org>; Fri, 10 Jul 2026 08:45:22 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [45.83.6.19]) (using TLSv1.2 with cipher ECDHE-ECDSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 5DFE41149BB6D for <dnsop@ietf.org>; Fri, 10 Jul 2026 08:45:12 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305) (Smail #158) id m1wiDPb-0000O3C; Fri, 10 Jul 2026 17:45:11 +0200
Message-Id: <m1wiDPb-0000O3C@stereo.hq.phicoh.net>
To: dnsop@ietf.org
From: Philip Homburg <pch-dnsop-7@u-1.phicoh.com>
Sender: pch-b55F8B228@u-1.phicoh.com
References: <AM8P189MB122002B1E02C38D8A97B23D9A8FD2@AM8P189MB1220.EURP189.PROD.OUTLOOK.COM> <CA9E8786-787C-49C5-A608-9878CEF6B41D@pch.net> <f9ce82c4-b2ea-47eb-dc13-f1c33b21540a@nohats.ca> <9EA346A1-F188-4912-B4D6-FF7588AB5C80@rfc1035.com>
In-reply-to: Your message of "Fri, 10 Jul 2026 16:01:36 +0100 ." <9EA346A1-F188-4912-B4D6-FF7588AB5C80@rfc1035.com>
Date: Fri, 10 Jul 2026 17:45:11 +0200
Message-ID-Hash: TMLLCSFCBADTE2T6EBSXX7FOVBNI4KCN
X-Message-ID-Hash: TMLLCSFCBADTE2T6EBSXX7FOVBNI4KCN
X-MailFrom: pch-b55F8B228@u-1.phicoh.com
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: Client authentication for encrypted DNS — interest check
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lsL3lctepSfLwe_UHCgNT2Y63UU>
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>

> > When will I get DANE requiring DNSSEC support on my mobile devices?
> 
> Some time after the heat death of the universe is my best guess.

Both of you seem to assume that a phone that authenticates using DANE
would have to do something with DNSSEC. Which is weird because phones are
usually not running any authoritative DNS server. And only the relying
party would have to have DNSSEC validation. Which would be the server
in this case, not the client.

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