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

Michael De Roover <ietf@nixmagic.com> Fri, 09 May 2025 21:04 UTC

Return-Path: <ietf@nixmagic.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 D5C5726FE7D2 for <dnsop@mail2.ietf.org>; Fri, 9 May 2025 14:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 k2zOVMiiRehU for <dnsop@mail2.ietf.org>; Fri, 9 May 2025 14:04:21 -0700 (PDT)
Received: from nixmagic.com (e1.nixmagic.com [116.203.235.171]) by mail2.ietf.org (Postfix) with ESMTP id CAF8426FE7CD for <dnsop@ietf.org>; Fri, 9 May 2025 14:04:21 -0700 (PDT)
Received: from thonkpad.lan (wlan0.thonkpad.lan [192.168.10.23]) by nixmagic.com (Postfix) with ESMTPSA id 3C6EFCA98B; Fri, 9 May 2025 21:04:21 +0000 (UTC)
From: Michael De Roover <ietf@nixmagic.com>
To: dnsop@ietf.org, John Levine <johnl@taugh.com>
Date: Fri, 09 May 2025 23:04:20 +0200
Message-ID: <3356637.44csPzL39Z@thonkpad.lan>
Organization: thonkpad.lan
In-Reply-To: <19e72705-33dc-9895-f8af-07f8e87f456b@taugh.com>
References: <1C9E8ABA-4399-491B-A9F4-D9ACCB1BA72C@virtualized.org> <4980511.GXAFRqVoOG@thonkpad.lan> <19e72705-33dc-9895-f8af-07f8e87f456b@taugh.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Message-ID-Hash: OUEQS72K6INIVMA7ULHRF2NOIAPBDJAX
X-Message-ID-Hash: OUEQS72K6INIVMA7ULHRF2NOIAPBDJAX
X-MailFrom: ietf@nixmagic.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/XmAwNokmVfw93LZReTUADqgJNv8>
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 Friday, 9 May 2025 22:56:54 CEST John R Levine wrote:
> Consensus is a very loose term.  I would guess that most of the people 
> running networks that have private internal TLDs have no idea who the IETF 
> is, who sets the rules for the way the Internet works, and wouldn't use
> DNSSEC even if they knew what it is.

Sadly, that is true. Most of the people I talk to have no idea who the IETF 
is, and that even includes a variety of ISPs that I'd otherwise imagine to 
have a vested interest. Especially for .internal, where the expectation (as 
drafted) is to run your own zones for it too, but otherwise to be bog-standard 
DNS.

As far as relevance goes, I don't think that funneling as much of the .lan, 
.corp, ... usage as possible into .internal would be a bad thing. That would 
help establish the DNS and its root as a global namespace, that fewer people/
organizations would have a reason to unilaterally walk out of. Just like 
private-use address spaces (that are also loosely divided into 192.168/16 for 
home and 10/8 for professional use), .internal could be that 10/8 for DNS 
names.

-- 
Met vriendelijke groet,
Michael De Roover

Mail: ietf@nixmagic.com
Web: michael.de.roover.eu.org