Re: [DNSOP] [Ext] Fwd: I-D Action: draft-toorop-dnsop-ranking-dns-data-00.txt

Paul Hoffman <paul.hoffman@icann.org> Mon, 11 March 2024 15:04 UTC

Return-Path: <paul.hoffman@icann.org>
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 7D6BEC14F5FB for <dnsop@ietfa.amsl.com>; Mon, 11 Mar 2024 08:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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
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 aiDB0CkckpK2 for <dnsop@ietfa.amsl.com>; Mon, 11 Mar 2024 08:04:54 -0700 (PDT)
Received: from ppa4.dc.icann.org (ppa4.dc.icann.org [192.0.46.77]) (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 B26B9C14F5E5 for <dnsop@ietf.org>; Mon, 11 Mar 2024 08:04:54 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa4.dc.icann.org (8.17.1.24/8.17.1.24) with ESMTPS id 42BF4nge011448 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 11 Mar 2024 08:04:49 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Mon, 11 Mar 2024 08:04:49 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) by MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) with mapi id 15.02.1258.028; Mon, 11 Mar 2024 08:04:49 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Ray Bellis <ray@bellis.me.uk>
CC: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [Ext] [DNSOP] Fwd: I-D Action: draft-toorop-dnsop-ranking-dns-data-00.txt
Thread-Index: AQHac8V2U9ki7UbVZUm7a7UlEBBJEw==
Date: Mon, 11 Mar 2024 15:04:49 +0000
Message-ID: <A6FA73E4-3BC5-4646-9E02-5207C9E96510@icann.org>
References: <57517c17-fa72-4180-a1ac-b74eac12ca88@NLnetLabs.nl> <9dfb3b11-c5ea-42f0-8aa1-9b0d65066848@bellis.me.uk>
In-Reply-To: <9dfb3b11-c5ea-42f0-8aa1-9b0d65066848@bellis.me.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <66B1AC8E030DB84CA9DDDDBA714A093A@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1011,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2024-03-11_10,2024-03-06_01,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tocyzMgAv_37bT0H3xWZcEoiLTA>
Subject: Re: [DNSOP] [Ext] Fwd: I-D Action: draft-toorop-dnsop-ranking-dns-data-00.txt
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: Mon, 11 Mar 2024 15:04:58 -0000

On Mar 11, 2024, at 07:30, Ray Bellis <ray@bellis.me.uk> wrote:
> 
> I think this document gives an opportunity to explicitly clarify expectations regarding the NS records either side of the zone cut.

Wearing my co-author hat: yes, that's the purpose.

> I get the impression with DELEG on the horizon that there's a shift towards the parent side data being considered more "authoritative" even though in protocol terms it explicitly isn't.

Wearing my BoF co-chair hat: it is waaay to soon to say that. There were explicit requests for child-side declarations to be in scope for the eventual working group.

> Even if that's not the case, discussion of when child-side NS records should be purged and then re-learned by following the parent-side delegation would be useful.

Wearing my DNSOP participant hat: that's why I encouraged Shumon and PaulV to revive <https://datatracker.ietf.org/doc/draft-ietf-dnsop-ns-revalidation/>.

> I also idly wonder what would happen if one were able to incorrectly put the DS records for a zone into the child zone...

Wearing my Hackathon hat: I'm working on a small testbed, using Shumon's code, that could test that.

--Paul Hoffman, who rarely actually wears hats, but will in Brisbane because of the sun