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

Karl Dyson <karldyson@gmail.com> Fri, 18 April 2025 10:24 UTC

Return-Path: <karldyson@gmail.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 5C55C1E08357 for <dnsop@mail2.ietf.org>; Fri, 18 Apr 2025 03:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_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=gmail.com
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 3btFW85frvlZ for <dnsop@mail2.ietf.org>; Fri, 18 Apr 2025 03:24:05 -0700 (PDT)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 003481E08352 for <dnsop@ietf.org>; Fri, 18 Apr 2025 03:24:04 -0700 (PDT)
Received: by mail-wr1-x429.google.com with SMTP id ffacd0b85a97d-39c30d9085aso1254159f8f.1 for <dnsop@ietf.org>; Fri, 18 Apr 2025 03:24:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744971844; x=1745576644; darn=ietf.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=yqImnzISWbgfLMSxjFtsXTInUihVeYq3MkkQPiJGbs8=; b=b3isHm5yI9dv1H/gSxeMtk+r0rsego/aaPPCr4xNlkGS0tS8Sm6kU2qmAqSIhaQoaD syB9sE6o/WD2HSD6QRZfL6xC3iltF80wRpfri5lNkXh/iFoFEPEpDF0uV8YhIdFykf7N 95xhdC+s7xEAI8d8leEmADzsMBj9mhSpzb6auyBB/krbE369xYUSh4ASUuTvg7nV6vJo RWsD/4mOsx6EZGlqi0jBpz4Pd0JVAOJOfB+IrEsBGaUPrimK0FkXb8I4ONr/RfQNoyOc ALulc8nGGeuFTHjaIVTnc4iA2m6SXXMQzM8jpLohtol5PHPa9v0YqUkfwJv3tb5KB9md Du4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744971844; x=1745576644; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=yqImnzISWbgfLMSxjFtsXTInUihVeYq3MkkQPiJGbs8=; b=pYsyf14aswgf3kaKo10DxKe4X344YZqBqhz7xDBHr+hI8lFlKWhlYmnj3EhJkTBDoV 0KRngFusXMNzVmgi8DPAxlxtYgF72DuK8COiPPdCJpxZ6rHAOx3cws/RauA5J25b4Xwi KudFnSk5nqF6NjcoVW12zqN8VX5HDjli/q0GGHMF4dd34dH/q2mEc6e2x6X5RLDIoidj +5L0uZ0TSRYBtBzGiLs5ZDRCU8PHHzwvim9DWqhi6+PHmMFDn5OOWe1NCWqyQbsZhz1F ufQgfK15z+RQX06W1kNqthiJihipK9S2eDATLD1CdNW9uylSzdEUETWKykGHPAK29Zg3 pqWA==
X-Gm-Message-State: AOJu0YwEV9Oak/Bw8Oq0M/fFzoQ3VcnddkF3krh5UWZ9e3GmMnpvv2OE XWgyqb3T6BEHDoWUzbMX0RiQwl1iz+tx+lq+lqNC6FbF+PRyQxZrH5SMaQxg
X-Gm-Gg: ASbGncvZlDQZudouWWVvnJ7/3UViHH/SfKBvDDbNQxXx8AcE5aHNIQDqs8Zy9KZxUU3 OaehiWvNjeEXeJUI/MVx/S4/qibxBo7y2tFDi92T1ueOju69OT5kVk0SzR4Xog/rizfePhDwKdS Dhix0c+cW5STf69K12GqwB9qJ4tBPWhuNdI0fQt3goF9GllC7UhnXUSHGbKqq/VhnfQlF7fjyqp 7X/dkqxd5VnjT+dcU46xEpxmlysaldS+oYS3a4V2WOX0lKl7PadxMQ9F7SYzf7LUAaL2Ihl1Vv4 RXVSfV989zAY92PR6bjiz7KYuLszbkSigMwrFrMUSGzyPlC8eA==
X-Google-Smtp-Source: AGHT+IGiJaWeMdePlmEy4GAjOJFsUUgsnpYO9z3lasewSZgJVckT9Ubq2KxpepT2Fv9MiNvIj4zleA==
X-Received: by 2002:a05:6000:2584:b0:39a:ca05:5232 with SMTP id ffacd0b85a97d-39efba399c5mr1781920f8f.5.1744971843959; Fri, 18 Apr 2025 03:24:03 -0700 (PDT)
Received: from carbon.junesta.net (carbon.junesta.net. [2001:19f0:7401:8ac9::157]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-39efa4a5150sm2276772f8f.82.2025.04.18.03.24.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 18 Apr 2025 03:24:03 -0700 (PDT)
Date: Fri, 18 Apr 2025 10:24:02 +0000
From: Karl Dyson <karldyson@gmail.com>
To: Joe Abley <jabley@strandkip.nl>
Message-ID: <20250418102402.hsrsufimj2iz5v67@carbon.junesta.net>
References: <20250418094613.qndp4cu5ccelsahx@carbon.junesta.net> <32B393D3-AEC5-4108-A351-866F8423F596@strandkip.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <32B393D3-AEC5-4108-A351-866F8423F596@strandkip.nl>
Message-ID-Hash: WE5ZRUYWX4XPXDRLSFC53U3GJB6S3YZL
X-Message-ID-Hash: WE5ZRUYWX4XPXDRLSFC53U3GJB6S3YZL
X-MailFrom: karldyson@gmail.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: dnsop@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: [EXTERNAL] 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/xmdCbg8hp3rkJ57vMcv_61ir7XE>
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 Fri, Apr 18, 2025 at 12:00:19PM +0200, Joe Abley wrote:
> On 18 Apr 2025, at 11:47, Karl Dyson <karldyson@gmail.com> wrote:
> 
> > I agree we should not repeat mistakes, however, if a precedent already
> > exists for handling of special case TLDs, we should be consistent in our
> > approach, to avoid confusion among folks implementing, operating and
> > troubleshooting this camel.
> 
> I think the question is why this particular domain is special. 
> 
> It is special in terms of namespace management, which is ICANN's domain. There will never be a new gTLD assigned that is called INTERNAL.
> 
> I don't think it is special as far as the DNS is concerned, though.
> 
> I don't think it is different from INTERNAL.STRANDKIP.NL, for example, if we imagine that is a domain that is invisible to most of the internet that is not connected within my apartment in Amsterdam. I don't need the DNS protocol to work differently from normal for INTERNAL.STRANDKIP.NL to work as I want it to work. If I had decided to name things under the INTERNAL top-level domain I also would not need special handling by the DNS protocol.
> 
> People are of course free to configure their software to treat names under INTERNAL differently. But they don't need to. Everything will continue to work as expected regardless of whether they do or not. 
> 
> So I don't think INTERNAL is special, I don't think it needs to be added to the special use domains registry, I don't think this document needs to exist and so I don't think the working group should adopt it.
> 
> 
> Joe

Hello,

I read this a few times and it led to my other reply supporting
adoption.

I kept thinking about the parallels with RFC1918 address space and
concluded, rightly or wrongly, that it should be considered by the WG.

Thanks,
Karl

-- 
Karl Dyson