[DNSOP] Re: Working Group Last Call for draft-ietf-dnsop-cds-consistency
Joe Abley <jabley@strandkip.nl> Tue, 24 June 2025 12:04 UTC
Return-Path: <jabley@strandkip.nl>
X-Original-To: dnsop@mail2.ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id F14B038B7E3E for <dnsop@mail2.ietf.org>; Tue, 24 Jun 2025 05:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=strandkip.nl
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NyCGyj9ITyQr for <dnsop@mail2.ietf.org>; Tue, 24 Jun 2025 05:04:01 -0700 (PDT)
Received: from dane.soverin.net (dane.soverin.net [185.233.34.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 275C038B7E39 for <dnsop@ietf.org>; Tue, 24 Jun 2025 05:04:01 -0700 (PDT)
Received: from smtp.soverin.net (unknown [10.10.4.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by dane.soverin.net (Postfix) with ESMTPS id 4bRNsD2xYcz12xR; Tue, 24 Jun 2025 12:04:00 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.100]) by soverin.net (Postfix) with ESMTPSA id 4bRNsD13B6zKy; Tue, 24 Jun 2025 12:04:00 +0000 (UTC)
Authentication-Results: smtp.soverin.net; dkim=pass (2048-bit key; unprotected) header.d=strandkip.nl header.i=@strandkip.nl header.a=rsa-sha256 header.s=soverin1 header.b=oWcFmT39; dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=strandkip.nl; s=soverin1; t=1750766640; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6GW5R3eC40/UMA+Ry+6GpzRsg2t5g7Dc/3SS59YwlVc=; b=oWcFmT39lRWMAA8Y7TZoonqT57+25wU722va0wE1VkE7j5jYMTiK//MQDVF3isf6kQIwvY w2rdu5jIs5Pn+JI+7nyfz9yoHCyRNn+pmyxigS4piBpLDjIAxBnQclV8DWGA+cgXYyDxJV qmGz7W+QfR2vvfxKwMSms6mgmHHk+HGsCohgV3POs/4cWJE2rfwMiPR3HarZOLfNgaY4HI /GVmYbo3Q2QUQphFTHhZGqShfUpnDjXTawcVjozRJHgrbv2H3GqVQNHjG7nYf3+huuBbPF igCkr32rVMsjQNdqp0EWAiRLSoCEzMLGR9tOLm1pUI0ZR7T2JEfaeN83cF6Kwg==
X-CM-Analysis: v=2.4 cv=UsCZN/wB c=1 sm=1 tr=0 ts=685a9430 a=IkcTkHD0fZMA:10 a=pGLkceISAAAA:8 a=D2TFXCquufWB6yT9gdsA:9 a=QEXdDO2ut3YA:10
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
From: Joe Abley <jabley@strandkip.nl>
In-Reply-To: <75ebbdf6-678c-42e0-95c8-359c72211916@gmail.com>
Date: Tue, 24 Jun 2025 14:03:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <25C1A796-A276-40BC-8945-6DD8A9F1C18D@strandkip.nl>
References: <75ebbdf6-678c-42e0-95c8-359c72211916@gmail.com>
To: Ondřej Caletka <ondrej.caletka@gmail.com>
X-Spampanel-Class: ham
Message-ID-Hash: BFPKNOHPYR6POXN7GSX23S7LYMDAQXMP
X-Message-ID-Hash: BFPKNOHPYR6POXN7GSX23S7LYMDAQXMP
X-MailFrom: jabley@strandkip.nl
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: dnsop@ietf.org, oli.schacher@switch.ch
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: Working Group Last Call for draft-ietf-dnsop-cds-consistency
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/J1m4pXR4Up_Vk65Hmj1bol-dajM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>
Hi all, On 24 Jun 2025, at 13:42, Ondřej Caletka <ondrej.caletka@gmail.com> wrote: > sorry for chiming in a bit late but I find part of this proposal a bit harmful: > > > …the Parental Agent, knowing both the Child zone name and its NS hostnames, MUST ascertain that queries are made against all (reachable) nameservers listed in the Child's delegation from the Parent… > > You cannot send queries to hostnames, you have to query an IP address. So you have to somehow convert each NS hostname into a set of IP addresses. I am also unsure about this, because it feels like it's not a very DNS way of doing things. (I have mentioned this to Peter before, I think, but I can't currently remember whether it was on this list or somewhere else). Usually we accept any response from any authoritative nameserver as authoritative and don't poll all possible authoritative nameservers. We understand that there might be reasons why the responses are different, because we know that the DNS is only loosely-coherent for various reasons. I am uncomfortable with this. Perhaps it's fine. Perhaps therapy would help. Another potential pitfall is the assertion that the NS set either side of the zone cut is identical. Despite much fervent advice to the contrary, it is often possible for the delegation set in the parent to be different from the apex set in the child without any resulting failure. I used to work somewhere where the two sets were deliberately different for a reason (I forget what the reason was, but I remember there was a reason). I am not trying to reignite that particular debate, but I'll observe that "all (reachable) nameservers listed in the child's delegation from the parent" is not always the same as "all nameservers that are authoritative for the child zone". The parenthetical "reachable" also makes me wonder a bit. If it's ok not to consult some nameservers because they are not reachable from a particular vantage point, is not also ok to ignore them at other times? Is any of this necessary? Is it not sufficient to make the publication of information the child zone's administrator's problem? We do we find it necessary for the parent to assume the child is doing a poor job? Note we are talking about the DNS here, in case anybody of child-rearing age is feeling triggered. > Normally people do this by asking the local recursive resolver. But with the spirit of this draft this does not seems to be reasonable thing to do because in a multi-signer scenario, each party can resolve the same hostname to a completely different set of IP addresses. Using local recursive resolver might thus bring completely random results based on which authoritative server will it query. This seems like it could be true in some case but I am not sure why it needs to matter. It has the aroma of the same kind of bootstrapping problem that brought the gift of glue records into our lives, for example, gifts that we enjoy so much we often forget they are there. Can we not assume that either the hostnames concerned are able to be resolved, or they are not able to resolved in which case there is a fault that someone should fix? Joe
- [DNSOP] Working Group Last Call for draft-ietf-dn… Ondřej Surý
- [DNSOP] Re: Working Group Last Call for draft-iet… Ondřej Surý
- [DNSOP] Re: Working Group Last Call for draft-iet… Steve Crocker
- [DNSOP] Re: Working Group Last Call for draft-iet… Michael Bauland
- [DNSOP] Re: Working Group Last Call for draft-iet… Joe Abley
- [DNSOP] Re: Working Group Last Call for draft-iet… Frederico A C Neves
- [DNSOP] Re: Working Group Last Call for draft-iet… Brian Dickson
- [DNSOP] Re: Working Group Last Call for draft-iet… Joe Abley
- [DNSOP] Re: Working Group Last Call for draft-iet… Peter Thomassen
- [DNSOP] Re: Working Group Last Call for draft-iet… Brian Dickson
- [DNSOP] Re: Working Group Last Call for draft-iet… Oli Schacher
- [DNSOP] Re: Working Group Last Call for draft-iet… Ondřej Caletka
- [DNSOP] Re: Working Group Last Call for draft-iet… Joe Abley
- [DNSOP] Re: Working Group Last Call for draft-iet… Joe Abley
- [DNSOP] Re: Working Group Last Call for draft-iet… Peter Thomassen
- [DNSOP] Re: Working Group Last Call for draft-iet… Oli Schacher
- [DNSOP] Re: Working Group Last Call for draft-iet… Ondřej Caletka
- [DNSOP] Re: Working Group Last Call for draft-iet… Peter Thomassen
- [DNSOP] Re: Working Group Last Call for draft-iet… Ondřej Caletka
- [DNSOP] Re: Working Group Last Call for draft-iet… Peter Thomassen
- [DNSOP] Re: Working Group Last Call for draft-iet… Peter Thomassen
- [DNSOP] Re: Working Group Last Call for draft-iet… Peter Thomassen