Re: [dd] [Ext] DS pinning for secondaries

Paul Hoffman <paul.hoffman@icann.org> Tue, 27 February 2024 17:04 UTC

From: Paul Hoffman <paul.hoffman@icann.org>
To: Petr Špaček <pspacek@isc.org>
CC: "dd@ietf.org" <dd@ietf.org>
Thread-Topic: [Ext] [dd] DS pinning for secondaries
Thread-Index: AQHaaZ282BieL9U2xUCFrC0MXPIVq7Ee8N+A
Date: Tue, 27 Feb 2024 17:04:17 +0000
Message-ID: <2409EBB4-285A-484E-9070-87DDCB1C615F@icann.org>
References: <9ffd0747-054d-4f84-a7f9-43265974b07d@isc.org>
In-Reply-To: <9ffd0747-054d-4f84-a7f9-43265974b07d@isc.org>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="utf-8"
Content-ID: <293660CFB372894EA370D3B2C75E4100@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dd/hv1EsvxENvdLDFay55jZzauF1eE>
Subject: Re: [dd] [Ext] DS pinning for secondaries
Precedence: list

On Feb 27, 2024, at 08:55, Petr Špaček <pspacek@isc.org> 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.

That sounds like a good use case.

> 
> In my mind that translates to syntax like this:
> 
> signed.example.net. DELEG 0 operator.example. ds="12345678"

Why that, and not
   signed.example.net. DELEG 0 operator.example.
   signed.example.net. DS 32859 13 2 12345678
That is, the parent continues to publish the (signed) DS as normal, and operator.example just publishes the rest of the delegation information? 

--Paul Hoffman

[dd] DS pinning for secondaries Petr Špaček
Re: [dd] [Ext] DS pinning for secondaries Paul Hoffman
Re: [dd] DS pinning for secondaries Paul Wouters
Re: [dd] DS pinning for secondaries Petr Špaček
Re: [dd] DS pinning for secondaries Philip Homburg
Re: [dd] [Ext] DS pinning for secondaries Ben Schwartz