IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@icann.org> Tue, 17 June 2025 17:00 UTC

Return-Path: <paul.hoffman@icann.org>
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 C819B360DD6A for <dnsop@mail2.ietf.org>; Tue, 17 Jun 2025 10:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Y4Syf3v2FDNZ for <dnsop@mail2.ietf.org>; Tue, 17 Jun 2025 10:00:19 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) by mail2.ietf.org (Postfix) with ESMTP id 37E14360DD65 for <dnsop@ietf.org>; Tue, 17 Jun 2025 10:00:19 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa2.lax.icann.org (8.18.1.2/8.18.1.2) with ESMTPS id 55HH0IDT008235 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <dnsop@ietf.org>; Tue, 17 Jun 2025 17:00:18 GMT
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.1544.11; Tue, 17 Jun 2025 10:00:17 -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.1544.011; Tue, 17 Jun 2025 10:00:17 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: dnsop <dnsop@ietf.org>
Thread-Topic: [Ext] [DNSOP] on the more general problem of delegating to other namespaces in the DNS
Thread-Index: AQHb357uke33I+JjWkS7YFFasJqaxbQICLMA
Date: Tue, 17 Jun 2025 17:00:17 +0000
Message-ID: <96D1EC9A-DC37-4950-B391-E9C23B8C4686@icann.org>
References: <761F6D32-25FE-4742-9682-819A338C8EC9@strandkip.nl>
In-Reply-To: <761F6D32-25FE-4742-9682-819A338C8EC9@strandkip.nl>
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: <98011D55C5705E40B06D560E2E4FE9B9@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1099,Hydra:6.0.736,FMLib:17.12.80.40 definitions=2025-06-17_07,2025-06-13_01,2025-03-28_01
Message-ID-Hash: NXNU26MXKELS62IHFLORTHKCGVPHUYOA
X-Message-ID-Hash: NXNU26MXKELS62IHFLORTHKCGVPHUYOA
X-MailFrom: paul.hoffman@icann.org
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
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/3KvtMaMBrV-rzX2q7Us4FJ9rjzE>
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 Jun 17, 2025, at 08:44, Joe Abley <jabley=40strandkip.nl@dmarc.ietf.org> wrote:
> 
> Warren, Wes and I put our respective heads together in Prague and came up with this:
> 
>   https://datatracker.ietf.org/doc/draft-jabley-dnsop-zone-cut-to-nowhere/
> 
> This is some general advice for how to delegate a domain to another namespace.

This is a good idea, but I am wary of the implementation. Have the authors done any testing on what will happen with resolvers that are not aware of the new semantics? I ask because I can imagine that some resolvers, when seeing the delegation to "." would then pound mercilessly on the root servers. Maybe a different target for the nowheres would cause less damage from resolvers that don't know the new protocol?

--Paul Hoffman

v2.36.0 | Report a Bug | By Email | System Status