[DNSOP] Re: [Ext] on the more general problem of delegating to other namespaces in the DNS

Joe Abley <jabley@strandkip.nl> Tue, 17 June 2025 18:14 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 DF3633618AF3 for <dnsop@mail2.ietf.org>; Tue, 17 Jun 2025 11:14:36 -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 pcOLhxPPYssD for <dnsop@mail2.ietf.org>; Tue, 17 Jun 2025 11:14:36 -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 378923618AEB for <dnsop@ietf.org>; Tue, 17 Jun 2025 11:14:36 -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 4bMFQ31NwJz1KT4; Tue, 17 Jun 2025 18:14:35 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.99]) by soverin.net (Postfix) with ESMTPSA id 4bMFQ26DHMz8x; Tue, 17 Jun 2025 18:14:34 +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=T53/2oHe; dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=strandkip.nl; s=soverin1; t=1750184074; 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=Qv7dT6bTtBT7B3tJ7A6ZgBR4Egd3J3dHulBZxNXkI5g=; b=T53/2oHesw8K41QNkoIgrG+IVcspXPzP2olz4zI+dOklzSYcUu/ajBBf8F/YTnNMb0wZLK +Od0gOs3er2boONHMIhBbHjuLqeodLHsruE1jVsSaLr8WioZHizT0jjh3pWrsaemFEGfZT zmU7IEfgfsxwi56VtTq5yRolLLi/8Zbma/o1lPUMJWjBc1MLt5pzVKgljOAiLYaEon6u9G /XJ9lYPrE6BJ9Qh1043bX3Y+iNj6fGYvArDBLa+/dD6UHhJwIE/2hiQtK0DLPNQG95aLd8 HFQbtyRPabCxUmRGUe0D+M6pfJkDr9a4Esx+dFyKDjwOR2bCJp3YL9QfijhblQ==
X-CM-Analysis: v=2.4 cv=d/oPyQjE c=1 sm=1 tr=0 ts=6851b08a a=tNF5heSCPcKR_L7q:21 a=IkcTkHD0fZMA:10 a=m9shYIPOAAAA:8 a=y9plqzxeAAAA:8 a=NN8BQSI2AsoW7dQbsUUA:9 a=QEXdDO2ut3YA:10 a=lBp3Ekt4YYfsEVDhWcye:22
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Joe Abley <jabley@strandkip.nl>
Mime-Version: 1.0 (1.0)
Date: Tue, 17 Jun 2025 20:14:24 +0200
Message-Id: <7F53BD74-09D7-400B-B176-9A5575DC57AB@strandkip.nl>
References: <E30999C0-9ECA-49ED-A109-B42C0C9DCADA@icann.org>
In-Reply-To: <E30999C0-9ECA-49ED-A109-B42C0C9DCADA@icann.org>
To: Paul Hoffman <paul.hoffman@icann.org>
X-Spampanel-Class: ham
Message-ID-Hash: B63YH7SO2NMHIQCNH5TDASBBOLF2DMB6
X-Message-ID-Hash: B63YH7SO2NMHIQCNH5TDASBBOLF2DMB6
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 <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: [Ext] on the more general problem of delegating to other namespaces in the DNS
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FuCungU8NdqK6SbcSjuzAVI99ak>
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>

On 17 Jun 2025, at 20:05, Paul Hoffman <paul.hoffman@icann.org> wrote:

> On Jun 17, 2025, at 10:54, Joe Abley <jabley@strandkip.nl> wrote:
>> Using "." to mean "not available" has some history and it feels nice not to deviate;
> 
> I would generally agree, but in this case noname (".") has a particular meaning in the DNS that it doesn't in, for example MX records. Thus my concern.

Well, an MX target is a hostname to which packets are sent; an NS target is a hostname to which packets are sent. So I'm not sure the situations are so different. 

In both cases a client that for some reason thinks the empty string is a valid hostname might try to resolve it. Such resolution will look for a root zone apex A or AAAA record. There isn't one; the cacheable NODATA responses from the root servers should confirm that to be the case.

I agree that software is riddled with crazy nonsense and nothing is impossible, but what I would expect to see is either nothing much or increased volumes of ./IN/A and ./IN/AAAA at the root servers. 

The root servers are well-provisioned to be able to handle junk, which is good because junk is mainly what they receive. But yes, science seems appropriate. 


Joe