IETF Logo Mail Archive

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

Philip Homburg <pch-dnsop-6@u-1.phicoh.com> Tue, 22 July 2025 16:15 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 5402D489F553 for <dnsop@mail2.ietf.org>; Tue, 22 Jul 2025 09:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_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 zd7XWbkGOElA for <dnsop@mail2.ietf.org>; Tue, 22 Jul 2025 09:15:35 -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 3E604489F4E7 for <dnsop@ietf.org>; Tue, 22 Jul 2025 09:15:32 -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 m1ueFeN-0000OSC; Tue, 22 Jul 2025 18:15:31 +0200
Message-Id: <m1ueFeN-0000OSC@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> <F5F9D9E2-90DD-40B1-824B-57C4380DDA67@icann.org> <m1ubcE5-0000NuC@stereo.hq.phicoh.net> <8c4b4f9c-8c8c-7a2d-f2da-9aff895e40f1@nohats.ca> <90464e4c-e5aa-4ac6-b4ff-a5fdac8c6c14@nic.cz> <20250717100850.D810CD3A7716@ary.local> <1be57a05-8719-424d-95ad-1bf557eff053@isc.org> <20250722134129.AEBFFD42229F@dhcp-81ff.meeting.ietf.org>
In-reply-to: Your message of "22 Jul 2025 15:41:29 +0200 ." <20250722134129.AEBFFD42229F@dhcp-81ff.meeting.ietf.org>
Date: Tue, 22 Jul 2025 18:15:30 +0200
Message-ID-Hash: P4GMRZKCZMOQLRU6SIU52O32ROAH26UR
X-Message-ID-Hash: P4GMRZKCZMOQLRU6SIU52O32ROAH26UR
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
CC: John Levine <johnl@taugh.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: [Ext] 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/EFqiskwRHUM71JixwarcSy3Bkeo>
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>

> Well, OK.   I can live with MUST NOT have colliding key tags if we
> also have MUST NOT have invalid RRSIGs.
> 
> PS: Not that I expect anyone to enforce either of them any time
> soon.

I'm not aware of any part of the DNSSEC standards, key rolls, operational
practice, etc. that leads to invalid RRSIGs.

So from a standards point of view, MUST NOT have invalid RRSIGs seems fine.

Obviously things can break. In that case it is fine if a resolver returns 
SERVFAIL.

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