Re: [DNSOP] data at delegation points

Ralf Weber <dns@fl1ger.de> Tue, 14 April 2020 16:35 UTC

Return-Path: <dns@fl1ger.de>
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 620313A09F7 for <dnsop@ietfa.amsl.com>; Tue, 14 Apr 2020 09:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5CcqDCbDqAbm for <dnsop@ietfa.amsl.com>; Tue, 14 Apr 2020 09:35:35 -0700 (PDT)
Received: from smtp.guxx.net (smtp.guxx.net [IPv6:2a01:4f8:a0:322c::25:42]) by ietfa.amsl.com (Postfix) with ESMTP id D27863A0CDB for <dnsop@ietf.org>; Tue, 14 Apr 2020 09:35:03 -0700 (PDT)
Received: by nyx.guxx.net (Postfix, from userid 107) id 194295F405E0; Tue, 14 Apr 2020 16:35:02 +0000 (UTC)
Received: from [192.168.2.128] (p54B8A2E9.dip0.t-ipconnect.de [84.184.162.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by nyx.guxx.net (Postfix) with ESMTPSA id 92BA85F40302; Tue, 14 Apr 2020 16:35:01 +0000 (UTC)
From: "Ralf Weber" <dns@fl1ger.de>
To: "Paul Vixie" <paul@redbarn.org>
Cc: dnsop@ietf.org
Date: Tue, 14 Apr 2020 18:35:01 +0200
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <6FDEF34B-45F9-4552-AED4-3AFDFCF5845C@fl1ger.de>
In-Reply-To: <70fa32cc-64ff-0a76-9025-b4c770ccc0e2@redbarn.org>
References: <060513e7-742d-6de9-cf16-c367fbb13845@redbarn.org> <DE1C0DEF-0479-4AF9-9D31-AEE2ADA67C46@fl1ger.de> <70fa32cc-64ff-0a76-9025-b4c770ccc0e2@redbarn.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/dnsop/0H47jijRuo5Bz_uPj6CN3TmsktM>
Subject: Re: [DNSOP] data at delegation points
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Apr 2020 16:35:43 -0000

Moin!

On 14 Apr 2020, at 17:59, Paul Vixie wrote:

> Ralf Weber wrote on 2020-04-14 08:57:
>> Just to clarify if I understand that correct. The DS for example.net 
>> would be example._dnssec.net DS. Correct? So would you propose to do 
>> example._ns2.net NS2 to distinguish parent and child NS2 records?
>
> i didn't understand the semantics of having more than one NS2, so i 
> don't know.
Mainly because of getting stuff in the parent is hard and starting with 
something in the child is easier. I assume I grasped the DS concept 
correct, so if we put the _ NS2 in the parent up to the root we could 
bootstrap securely in transport and validation from the root down.

So long
-Ralf
—--
Ralf Weber