IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Tue, 17 June 2025 17:16 UTC

Return-Path: <johnl@iecc.com>
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 B5CB23611C73 for <dnsop@mail2.ietf.org>; Tue, 17 Jun 2025 10:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="h3HKyuG4"; dkim=pass (2048-bit key) header.d=taugh.com header.b="Fl+S3Bw0"
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 LwLlUQ33yErc for <dnsop@mail2.ietf.org>; Tue, 17 Jun 2025 10:16:36 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 360763611C6D for <dnsop@ietf.org>; Tue, 17 Jun 2025 10:16:36 -0700 (PDT)
Received: (qmail 55344 invoked from network); 17 Jun 2025 17:16:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=d82e6851a2f3.k2506; t=1750180585; x=1750526185; bh=bXW91LqWt84uAgTjlob4qp6qlp2wYNxqjSR/To47VA8=; b=h3HKyuG4+jSvClGgSAbWMK3DOeBSPm2Y6rUMJAR5lz7+1a+LXbAclqZKGZxh3EaIcLYR7g1vq26oDAWo/HayPzeshT7j/VGRTS0joq/9Mz8nKNrc/RK8kdMAFkOJ51MzXRSXX3cq33P95mhexlO0LmJaqwgy2o6jVWw6riyBPCt/RYYYe4OZronOq2UpfeIcVWVsr6PfqL1P6AWuf/7lFDiYWl1Ev0GXiwhf/DUsxaX8/d9JEPZox9VVV4Nh1+1eOIXPiuZVmmp0F7m7St6Ug7OnoAFAPkEXZJEN6g4Y9zKDSRxGoeBdctgC3i5E8vKG5EdRuW0RNisNXgiV3j0ang==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=d82e6851a2f3.k2506; bh=bXW91LqWt84uAgTjlob4qp6qlp2wYNxqjSR/To47VA8=; b=Fl+S3Bw042fkIZrLiblMF8mRP1lAq05noH5LLL33dSN7Ux3lhYAA3EV5PwS128M0cH72EJp3DsfUQmw7iN/SMdhn1xkwjwkfRPD9b/4KSvM+ahnOeXJyh6VAw38TUz2utzENQEtZgv6VgSw3VwRhPYZqceab1IK4SV3CXnokkhJp2BOL1DvMrtnrUDwUieDmPRE7jZ10uRSmszd0WhMiA6fm1VjzU44g0TmGm4K9HyBWH1ooq15GIh1t7iJmofFEm5NzDoXiQNxAyzr5uuI6cV+XF85O8bmY9ODrz7PfkfFsp8vjbp2ykZpwwXPUq41hqPwgCi+hHC8Nk5HdKaQhRQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 17 Jun 2025 17:16:35 -0000
Received: by ary.qy (Postfix, from userid 501) id 152F1CE968AC; Tue, 17 Jun 2025 13:16:34 -0400 (EDT)
Date: Tue, 17 Jun 2025 13:16:34 -0400
Message-Id: <20250617171635.152F1CE968AC@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <96D1EC9A-DC37-4950-B391-E9C23B8C4686@icann.org>
Organization: Taughannock Networks
References: <761F6D32-25FE-4742-9682-819A338C8EC9@strandkip.nl> <96D1EC9A-DC37-4950-B391-E9C23B8C4686@icann.org>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: ZZJR6F2BUCPSC6XBDB5PTFVINFMPUSI2
X-Message-ID-Hash: ZZJR6F2BUCPSC6XBDB5PTFVINFMPUSI2
X-MailFrom: johnl@iecc.com
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: paul.hoffman@icann.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/tBOLjt2CCEYZ-x7OF_th2BVO5MQ>
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>

It appears that Paul Hoffman  <paul.hoffman@icann.org> said:
>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?

We had the same question about RFC 7505, the "MX ." trick to say there's no e-mail.  Someone
looked, the traffic was miniscule.

It couldn't hurt to check but I would be astonished if the result were different.

As far as the merits go, as one of the authors of "MX ." I can hardly object.

R's,
John

PS: So what happens if you have a DS next to your "NS ." ?

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