Re: [dd] DS pinning for secondaries

Paul Wouters <paul@nohats.ca> Tue, 27 February 2024 17:31 UTC

Return-Path: <paul@nohats.ca>
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 8D745C1516E1 for <dd@ietfa.amsl.com>; Tue, 27 Feb 2024 09:31:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 (1024-bit key) header.d=nohats.ca
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 p5P8PSYaH2oK for <dd@ietfa.amsl.com>; Tue, 27 Feb 2024 09:31:42 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E04E1C151063 for <dd@ietf.org>; Tue, 27 Feb 2024 09:31:23 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4Tkkzs1tPKz9qF; Tue, 27 Feb 2024 18:31:21 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1709055081; bh=HvzMxTEelXMSH/5xcKhJojlQbq1rtyV9tgvhxGMoP3I=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=jta7LO5v65rVfPC+ant7H0ELXTV9t+Qnf0VFNUtL00CK8DFT3Xy8kz6kIBoHMeROT IRKTqttPujwVn4ApznwVvmWdo5Hnd0KGIRmV2ulaE7K6EX8ql7OeJnsm61bj/kYRaN ZYCx9vC3B53AdZymHhvhaahTlgg3Q+OIHDXPtz1g=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id QF9yw0PdojT9; Tue, 27 Feb 2024 18:31:20 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 27 Feb 2024 18:31:20 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 645B611716AA; Tue, 27 Feb 2024 12:31:19 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 6182811716A9; Tue, 27 Feb 2024 12:31:19 -0500 (EST)
Date: Tue, 27 Feb 2024 12:31:19 -0500
From: Paul Wouters <paul@nohats.ca>
To: Petr Špaček <pspacek@isc.org>
cc: dd@ietf.org
In-Reply-To: <9ffd0747-054d-4f84-a7f9-43265974b07d@isc.org>
Message-ID: <45b4a54d-8d85-caf0-e1df-74f61c81b1a6@nohats.ca>
References: <9ffd0747-054d-4f84-a7f9-43265974b07d@isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dd/BANw_2MeOULjguehl1ge_-uR5PQ>
Subject: Re: [dd] DS pinning for secondaries
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, 27 Feb 2024 17:31:46 -0000

On Tue, 27 Feb 2024, Petr Špaček wrote:

> Today I've presented DELEG work to CENTR Tech group [1] and there was a 
> request to support use-case where ALIAS points to secondaries who are 
> supposed to serve signed version of the zone, but cannot resign it 
> themselves.
>
> In my mind that translates to syntax like this:
>
> signed.example.net. DELEG 0 operator.example. ds="12345678"

Why not a regular DS at the parent to lock this? And only use DELEG
for NS/glue.

Or rather, what would this use case gain from a DELEG record, other
than various transport security options?

You would also need a signal for this. Combing alias + non-alias seems
to open pandoras box of contradictions and complicated error paths. It
seems the easiest signal is the old fashioned DS record trumping DELEG
ds= entries.

Paul