[DNSOP] Re: Collision Free Key Tags for DNSSEC draft

Philip Homburg <pch-dnsop-6@u-1.phicoh.com> Mon, 14 July 2025 11:21 UTC

Return-Path: <pch-b6CAFA0C7@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 300DE43CA1D8 for <dnsop@mail2.ietf.org>; Mon, 14 Jul 2025 04:21:52 -0700 (PDT)
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_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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 NHN7yMqf98xW for <dnsop@mail2.ietf.org>; Mon, 14 Jul 2025 04:21:51 -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 7D67943CA1CB for <dnsop@ietf.org>; Mon, 14 Jul 2025 04:21:50 -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 m1ubHFk-0000NZC; Mon, 14 Jul 2025 13:21:48 +0200
Message-Id: <m1ubHFk-0000NZC@stereo.hq.phicoh.net>
To: dnsop@ietf.org
From: Philip Homburg <pch-dnsop-6@u-1.phicoh.com>
Sender: pch-b6CAFA0C7@u-1.phicoh.com
References: <d279f933-f00c-0392-80e2-0c6928b50af3@taugh.com> <C1251C46-3646-4885-A465-BFAF2BE23334@isc.org> <79638578-1dfc-d48c-9341-46cbde9e7feb@taugh.com> <CAHw9_iK+6xwATjbRs_9ZMNmbiX_SRxHpzbwG3SCN53BmPdqCMg@mail.gmail.com>
In-reply-to: Your message of "Mon, 14 Jul 2025 03:34:06 -0700 ." <CAHw9_iK+6xwATjbRs_9ZMNmbiX_SRxHpzbwG3SCN53BmPdqCMg@mail.gmail.com>
Date: Mon, 14 Jul 2025 13:21:48 +0200
Message-ID-Hash: NM434HIXG2MEVNXYLAUK7A4SUS5YHUOS
X-Message-ID-Hash: NM434HIXG2MEVNXYLAUK7A4SUS5YHUOS
X-MailFrom: pch-b6CAFA0C7@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: Collision Free Key Tags for DNSSEC draft
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/eN8CEvbhYoaapHv418YdUssesFc>
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>

>We could say that signers MUST NOT create colliding key tags, and that
>verifiers and similar tooling must continue to work as they currently do.
>
>That way, perhaps in (next decade + 1 year) we can discuss updating the
>verifier behavior.
>
>"The best time to plant a tree was 20 years ago. The second best time is
>now" and all that...

I agree with this. For a signer it can be a lot easier to just let 
collisions happen (and testing is also an issue). With an HSM, creating a
key and then deleting it because of a collision is already not pleasant. 
But some operators generate keys a year in advance. Some operators have
a specific procedure for generating ZSKs with an offline KSK.

Some procedures for moving from one signer to another involve creating a
temporary multi-signer setup. What if the two signers have a different
partitioning algorithm?

In these cases a clear MUST NOT can help to justify putting in the effort 
to make sure that all corner cases are handled.

Collisions are extremely rare. Without a clear requirement to handle 
collisions, it is very tempting to ignore them.