IETF Logo Mail Archive

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

Joe Abley <jabley@strandkip.nl> Fri, 18 April 2025 10:00 UTC

Return-Path: <jabley@strandkip.nl>
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 8A1731E0538F for <dnsop@mail2.ietf.org>; Fri, 18 Apr 2025 03:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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=strandkip.nl
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 sQvEzY4l3F5t for <dnsop@mail2.ietf.org>; Fri, 18 Apr 2025 03:00:36 -0700 (PDT)
Received: from st43p00im-ztdg10073201.me.com (st43p00im-ztdg10073201.me.com [17.58.63.177]) (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 F2BB51E05382 for <dnsop@ietf.org>; Fri, 18 Apr 2025 03:00:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=strandkip.nl; s=sig1; bh=72kf9hK+LQ/TfETiqg1laOTZZD5ohO13ZzpjxZLQoKM=; h=Content-Type:From:Mime-Version:Subject:Date:Message-Id:To:x-icloud-hme; b=W/uiGu68ezZdvpn0twDY9l4mRBD0VGI0JmKdmtdVoSrd74kvbVYG2hXdqTgv7lmPi fPQqp8dSH8hIjwE59ZfqeLk5YtY4VB5Ok4aF8dMg6fKT0bLKRWEaNtfv1wT8UhYpng 2XaFn6WdzuBsk+3N3ivahcJNhr+bgRyZ+MeZ5DFaiekFn/qbw64LPpGwSPRqEbn5w/ OkmZhsUKp6q7rrZZ6rj/bFH+BH05Fh1PrKKEBf7/sJeAALKTjX/dq0jeX78MRA5EPP FBCAVan1iibUK5ZRjo4fpTJy7b+LxNfNdjOQ3jQHyEvDaBmMaSUK1lb9GUQ9JEWJXN wQc5/HGF8xrug==
Received: from st43p00im-ztdg10073201.me.com (st43p00im-ztdg10073201.me.com [17.58.63.177]) by st43p00im-ztdg10073201.me.com (Postfix) with ESMTPS id 3459F9C06E9; Fri, 18 Apr 2025 10:00:35 +0000 (UTC)
Received: from smtpclient.apple (st43p00im-dlb-asmtp-mailmevip.me.com [17.42.251.41]) by st43p00im-ztdg10073201.me.com (Postfix) with ESMTPSA id EE5749C06F7; Fri, 18 Apr 2025 10:00:33 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
From: Joe Abley <jabley@strandkip.nl>
Mime-Version: 1.0 (1.0)
Date: Fri, 18 Apr 2025 12:00:19 +0200
Message-Id: <32B393D3-AEC5-4108-A351-866F8423F596@strandkip.nl>
References: <20250418094613.qndp4cu5ccelsahx@carbon.junesta.net>
In-Reply-To: <20250418094613.qndp4cu5ccelsahx@carbon.junesta.net>
To: Karl Dyson <karldyson@gmail.com>
X-Mailer: iPhone Mail (22E252)
X-Proofpoint-ORIG-GUID: k_aKs9RvcvizJG6sjd1VXzDg1lZnDJNp
X-Proofpoint-GUID: k_aKs9RvcvizJG6sjd1VXzDg1lZnDJNp
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1095,Hydra:6.0.680,FMLib:17.12.68.34 definitions=2025-04-18_03,2025-04-17_01,2024-11-22_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 phishscore=0 mlxlogscore=999 adultscore=0 mlxscore=0 malwarescore=0 clxscore=1030 spamscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2308100000 definitions=main-2504180073
Message-ID-Hash: 7WEQZKELVHBUS5KO4M6QOGXKDYZOBWIF
X-Message-ID-Hash: 7WEQZKELVHBUS5KO4M6QOGXKDYZOBWIF
X-MailFrom: jabley@strandkip.nl
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/4eKH2GcC8qC8uHPJCHm80vmI_NI>
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 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

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