Re: [dd] DS-pinning and Alias mode limitation

Roy Arends <roy@dnss.ec> Tue, 13 February 2024 11:54 UTC

Return-Path: <roy@dnss.ec>
X-Original-To: dd@ietfa.amsl.com
Delivered-To: dd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 756E1C15107E for <dd@ietfa.amsl.com>; Tue, 13 Feb 2024 03:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 (1024-bit key) header.d=dnss.ec
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 Yt8bqBM40Db8 for <dd@ietfa.amsl.com>; Tue, 13 Feb 2024 03:53:56 -0800 (PST)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2106AC14F5E7 for <dd@ietf.org>; Tue, 13 Feb 2024 03:53:53 -0800 (PST)
Received: by mail-pf1-x42f.google.com with SMTP id d2e1a72fcca58-6e0d085cf59so1684961b3a.2 for <dd@ietf.org>; Tue, 13 Feb 2024 03:53:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dnss.ec; s=google; t=1707825233; x=1708430033; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=xQnn58RFIQjjecRAqj39TyypVe/djYVXwmufxrDIQPA=; b=JhYWzDNk241o8qFC0UgCMvh11QQlRJJeMjAuCRhRDdbWONPfnWdyq7yIy8PinmFwM6 gXLY1028cUcUuQ06WRi+43IXsgdXdsXBn4Q/M6FjBpkpgPOYzg4UYhhewXuThSfZO90p fINU4NJgTgwe2QFmQ6drpNH1AZt//f85h9wSk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707825233; x=1708430033; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=xQnn58RFIQjjecRAqj39TyypVe/djYVXwmufxrDIQPA=; b=tl0GmGYtBkrefBH6zcBMKuGOGo6ZYj/qKErRGivRrEsfsJVz/RnX5/aaWONmr4cNcv t3/2yC+/xQdyFEJOvzGwK43Ws3n84b0l7fyQX5Y3Q02LIMlfUg3KAhbatBDg0gcrYP7n 0JuNfysKM/pop7jLeio2iAsNcihpSPFBjhzEBE0ffnJgF8AP+chKXwDYcdM3ZhTzYUl+ 2APP+RqgRzyfYbYGWqTZr8q6qdnzHw/nOS8yAgCTJiMBzhaRfHO4+cUe5aa05tKQMz/t SVPY6PPEjwYWfj/nxIBAGaLEyQSLJIJv/Q6mOiO6QHCxH7X0hOoDYMHZiP8IWWnfSvGv eBhg==
X-Gm-Message-State: AOJu0YzrEoL4eOuqG2751rw8NOvaRXxugnLSnwONir3tGFHDcTCZUc8b UH7YGniAEWcn9bxS0c6ks/e7B7uqlhJl0d9Y5V7VticMRJIF4eEbbI+emeXPPEyajxoPf8D0m4D RA98=
X-Google-Smtp-Source: AGHT+IEqM8UfElTBwoCa0k2P4XgFpwLukJjO7T5teglAzvx6ryTXNNtLfN1leCrvbCPk8stGPKYo8g==
X-Received: by 2002:a05:6a20:43ab:b0:19c:5523:eefe with SMTP id i43-20020a056a2043ab00b0019c5523eefemr14036173pzl.3.1707825232919; Tue, 13 Feb 2024 03:53:52 -0800 (PST)
Received: from smtpclient.apple ([78.111.198.85]) by smtp.gmail.com with ESMTPSA id q3-20020a17090a870300b002960e397891sm966677pjn.1.2024.02.13.03.53.51 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2024 03:53:52 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Roy Arends <roy@dnss.ec>
In-Reply-To: <SA1PR15MB43706DF6701A136927AB31F5B3482@SA1PR15MB4370.namprd15.prod.outlook.com>
Date: Tue, 13 Feb 2024 11:53:37 +0000
Cc: "dd@ietf.org" <dd@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF4DF716-F92B-429F-983A-8E13EFC878D4@dnss.ec>
References: <1DE0D512-7962-4943-B21D-196A441A3BC8@dnss.ec> <SA1PR15MB43706DF6701A136927AB31F5B3482@SA1PR15MB4370.namprd15.prod.outlook.com>
To: Ben Schwartz <bemasc@meta.com>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dd/jp-YYr6F-P7s0YDaWblpnQpu8uw>
Subject: Re: [dd] DS-pinning and Alias mode limitation
X-BeenThere: dd@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DNS Delegation <dd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dd>, <mailto:dd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dd/>
List-Post: <mailto:dd@ietf.org>
List-Help: <mailto:dd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dd>, <mailto:dd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Feb 2024 11:54:01 -0000

Hi Ben,

> On 12 Feb 2024, at 14:44, Ben Schwartz <bemasc@meta.com> wrote:
> 
> Yes.  The DELEG DNSSEC pre-00 draft [1] says: "When computing the digest, the DNSKEY Owner Name is always set to "." (i.e., the root), because this DS record approves the use of the specified DNSKEY on any zone that is delegated to this endpoint.".

Thanks for that. 

There needs to be a few words in the document, possibly the security section, on the impact on the security/threat model (if any) when there is no direct cryptographic binding between the parent and the secure entry point DNSKEY of the child zone. (i.e. the chain of trust is between parent (via DELEG) and child (KSK) via the root, and not directly).

Warmly,

Roy



> 
> --Ben
> 
> [1] https://github.com/fl1ger/deleg/blob/main/draft-dnsop-deleg-dnssec.mdFrom: dd <dd-bounces@ietf.org> on behalf of Roy Arends <roy@dnss.ec>
> Sent: Saturday, February 10, 2024 7:33 PM
> To: dd@ietf.org <dd@ietf.org>
> Subject: [dd] DS-pinning and Alias mode limitation
>  !-------------------------------------------------------------------|
>   This Message Is From an External Sender
> 
> |-------------------------------------------------------------------!
> 
> I understand that DS pinning involves DS material that references a DNSKEY, uniquely tied to a {zone-name-server} pair.
> 
> It's important to note that the digest in a DS record is generated based on the DNSKEY owner name and DNSKEY RDATA.
> 
> DS pinning won't function properly in DELEG Alias Mode when the target serves multiple zones. For instance:
> 
> foo.example DELEG 0 generic.example.net
> bar.example DELEG 0 generic.example.net
> generic.example.net SVCB 1 …. ds=AABBCC ns=ns1example.net
> 
> In this scenario, there must either be a unique 1:1 pairing between the DELEG owner and target name (instead of N:1), or the requirement for the digest to contain the DNSKEY owner name must be eliminated for aliased pinned DS to work effectively.
> 
> Warmly,
> 
> Roy
> 
> 
> 
> 
> 
> 
> 
> 
> -- 
> dd mailing list
> dd@ietf.org
> https://www.ietf.org/mailman/listinfo/dd