IETF Logo Mail Archive

Re: [DNSOP] [Ext] About key tags

Peter Thomassen <peter@desec.io> Tue, 27 February 2024 18:51 UTC

Return-Path: <peter@desec.io>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E559EC14F60A for <dnsop@ietfa.amsl.com>; Tue, 27 Feb 2024 10:51:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=a4a.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OhoB2T6JnjBo for <dnsop@ietfa.amsl.com>; Tue, 27 Feb 2024 10:51:11 -0800 (PST)
Received: from mail.a4a.de (mail.a4a.de [IPv6:2a01:4f8:10a:1d5c:8000::8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA610C14F714 for <dnsop@ietf.org>; Tue, 27 Feb 2024 10:51:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=a4a.de; s=20170825; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=LyufgoKOL5dxWNCwZHW9UoxEHu8tAuwd6Ydm45iTabQ=; b=aI60Fvn+mGCqlfPPaokTiO07ny aIBNFyJp5e2ZaId0fO4HqKSWx9sGaZHkIo0EE0Fb/gM4B+VxDeTC8QYcYsg4ES2nH1+DoZo1V8vTS pMijmzIl4pC6TbYOhenU/qP7QBna+pgfi8SOsuuYxv994XP7bEe5VZkx/ctEcrOrDC3Dtf/LRxocw vH2eWJ5or3WTi95bhIkU2NuL0o60azR2bdjt8YgK3UOPGVzuD8Ls5lqrK//LnrKnvvE5zc2KOasT9 V4YRNGuXw1s81cPGFlKnwES3CM8g6PdYk1ud5+Pg2VliO2wKlcpDSoB1fGr0aP133NhuAZlWpt0pf PRQ9TXQg==;
Received: from [2a00:20:d005:71ab:560c:c764:9d46:3f82] by mail.a4a.de with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from <peter@desec.io>) id 1rf2XX-003ek4-28; Tue, 27 Feb 2024 19:50:55 +0100
Message-ID: <f8033eb5-2a26-421a-a40b-826c2eaecbbb@desec.io>
Date: Tue, 27 Feb 2024 13:50:48 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Mark Andrews <marka@isc.org>, Bob Harold <rharolde@umich.edu>
Cc: Ralf Weber <dns@fl1ger.de>, Paul Hoffman <paul.hoffman@icann.org>, IETF DNSOP WG <dnsop@ietf.org>
References: <149c1bd9-6494-429c-8e87-e6a35c5e51de@isc.org> <E1E4C8E8-6D48-430E-9467-DEA2D37640D1@nohats.ca> <1C718716-6F4D-4002-86F7-98EF4DF1D636@akamai.com> <B6EADAB1-AE76-43CD-A127-32ECE3A65324@icann.org> <14F59E40-A2EF-4ACE-9AC3-6AE4D8C59A88@fl1ger.de> <7AA5AD7C-5A9B-4144-B7EB-DC2F2E9EF2B2@icann.org> <7137A5D8-276E-4D60-A8E2-F8446641DFDA@fl1ger.de> <CA+nkc8ARnBctoah5EkY9vpXzJ_TH6wX1dO=bZTKh5Lu1cw=XEg@mail.gmail.com> <06B7D221-FF3C-41EF-8B0C-DE66F5091087@isc.org>
Content-Language: en-US
From: Peter Thomassen <peter@desec.io>
In-Reply-To: <06B7D221-FF3C-41EF-8B0C-DE66F5091087@isc.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/LXGBcYcYROlOXfS8O8VSo25DJAs>
Subject: Re: [DNSOP] [Ext] About key tags
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Feb 2024 18:51:16 -0000


On 2/15/24 22:53, Mark Andrews wrote:
> But we can state that they should be avoided when generating new DNSKEYs. BIND has been avoiding key tag collisions for 2 decades now when generating new keys. Multi-signers all have to have the current published DNSKEY RRset which includes *all* DNSKEYs as part of their publication process.
Multi-signer peers do not need to publish each other's KSKs. A DNSKEY response only needs to contain the KSK suitable for validating the response RRset itself (i.e., the responding peer's KSK), and any ZSKs/CSKs that may be needed for validation of other responses.

Multi-signers thus aren't necessarily aware of keytag collisions across KSKs.

When using DS provisioning automation via CDS/CDNKSEY, they'll have to exchange each other's KSKs for publishing a joint C* RRset (as in draft-thomassen-dnsop-mske). The collision could be detected then, but using C* automation is not required.

Best,
Peter

v2.23.0 | Report a Bug | By Email