[DNSOP] Re: Sanity tl;dr for Multi-algorithm DNSSEC Requirements

Philip Homburg <pch-dnsop-7@u-1.phicoh.com> Wed, 05 August 2026 08:52 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 0478A123F5189 for <dnsop@mail2.ietf.org>; Wed, 5 Aug 2026 01:52:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785919927; bh=/E54PcG8mzvIF2mONB7eHY3db0bOajk6uZVua97QcrI=; h=To:Cc:Subject:From:References:In-reply-to:Date; b=cAIS7rT4afmmS8tWASeS6Q1t+OmnxgJgagrjpBbpkd7Dwmvu1Fqym1pxnTBHuAkTx zbSHAVZ/ByD9K48RXL8F3EVdi99YYeg8ySaFNnHJOmJYJb6oonWxwhduD6F6zeEaR2 SdSq7358v3vgw4jf+QrwULAIoz6ySsUQMHmYpTaM=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 BCc9bEVqbYlD for <dnsop@mail2.ietf.org>; Wed, 5 Aug 2026 01:52:06 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [IPv6:2a10:3781:2413:1:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-ECDSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 38D66123F50F6 for <dnsop@ietf.org>; Wed, 5 Aug 2026 01:52:03 -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 m1wrXM2-0000NyC; Wed, 5 Aug 2026 10:52:02 +0200
Message-Id: <m1wrXM2-0000NyC@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: <e6237cf7-01f1-4871-baad-6988985b113c@desec.io> <1f237f00-48ce-4599-b1c6-f3dc5cc6b24a@nic.cz> <5F6D199C-9269-4716-80B6-AEDFA9E5B49A@internetstiftelsen.se> <3FF284CF-FF1C-44F8-9854-9E80B6852710@isc.org> <m1wojaR-0000NeC@stereo.hq.phicoh.net> <6A1CE7C8-87E6-4FC4-ABEC-BF9163824362@isc.org> <m1wp08m-0000NfC@stereo.hq.phicoh.net> <43C3F251-8AF9-4643-BE3C-39CD104CDE20@isc.org>
In-reply-to: Your message of "Thu, 30 Jul 2026 11:03:20 +1000 ." <43C3F251-8AF9-4643-BE3C-39CD104CDE20@isc.org>
Date: Wed, 05 Aug 2026 10:52:01 +0200
Message-ID-Hash: W7MYBUAU4ZVMM3OKEB5VZBBUMVK4AVFK
X-Message-ID-Hash: W7MYBUAU4ZVMM3OKEB5VZBBUMVK4AVFK
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: Sanity tl;dr for Multi-algorithm DNSSEC Requirements
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/cREI1jmdcnisVCS2XlR1HMgNJAQ>
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>

> So what?  While the root will be an issue EVERY other zone goes
> INSECURE as people migrate to new algorithms and lookups DO NOT
> FAIL.  This is how DNSSEC was designed to work.  To have GRACEFUL
> fallback with old validators.
> 
> This attempt to break the bargain we made with the world is WRONG.
> It is bad engineering.

I think it is very bad idea for security protocols if software that it at
least a decade out of date and that has marginal (remaining) deployment
can block useful progress.

Whether and how to sign is a decision of the zone owner.
There is no requirement to sign is a way that is incompatible with those
old validators. It is just that we should allow a zone owner to say:
we don't care about people running obsolete security software. The people
using that software can turn it off if they can't update.