IETF Logo Mail Archive

[DNSOP] Re: Call for Adoption: draft-davies-internal-tld

Philip Homburg <pch-dnsop-6@u-1.phicoh.com> Fri, 18 April 2025 08:24 UTC

Return-Path: <pch-b6CAFA0C7@u-1.phicoh.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 80B511DFDE37 for <dnsop@mail2.ietf.org>; Fri, 18 Apr 2025 01:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 jYeHpJuGdVyz for <dnsop@mail2.ietf.org>; Fri, 18 Apr 2025 01:24:20 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [IPv6:2a10:3781:2413:1:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-ECDSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D1EB31DFDE32 for <dnsop@ietf.org>; Fri, 18 Apr 2025 01:24:19 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305) (Smail #158) id m1u5h1G-0000LcC; Fri, 18 Apr 2025 10:24:18 +0200
Message-Id: <m1u5h1G-0000LcC@stereo.hq.phicoh.net>
To: dnsop@ietf.org
From: Philip Homburg <pch-dnsop-6@u-1.phicoh.com>
Sender: pch-b6CAFA0C7@u-1.phicoh.com
In-reply-to: Your message of "Tue, 15 Apr 2025 10:38:42 +0200 ." <a7220ba0-5e8c-4273-a353-c8371ea23c50@NLnetLabs.nl>
Date: Fri, 18 Apr 2025 10:24:18 +0200
Message-ID-Hash: S4LWQRNLDXT2MIVNE2DT2KBFSYVQSHHM
X-Message-ID-Hash: S4LWQRNLDXT2MIVNE2DT2KBFSYVQSHHM
X-MailFrom: pch-b6CAFA0C7@u-1.phicoh.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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: Call for Adoption: draft-davies-internal-tld
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gWvuYAFFJAM7_PcbloOwcKc5Tls>
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>

> Please review the draft and share your thoughts on the mailing
> list, clearly stating whether you support its adoption by DNSOP.
> Also let us know if you are willing to contribute text, provide
> reviews, or help in other ways.

The current draft contains the following text:
DNSSEC validating resolvers will fail to resolve names ending in "internal".

In my opinion we should not have a specification that leads to DNSSEC
validation errors.

One option is to simply not have a draft at all. The IETF is not in charge
of the DNS namespace. The IETF deals with technical aspects of DNS.

A second option is to have a draft that recommends against using this domain
because doing so leads to DNSSEC validation errors. So the points in Section
5.1 (in particular point 1) should be changed that the use is not recommended.

A third option is to find a way to avoid DNSSEC validation errors. That is 
not a technical problem, there are multiple ways. But it seems that
none of those is acceptable.

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