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

Karl Dyson <karldyson@gmail.com> Fri, 18 April 2025 09:46 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 336681E045CB for <dnsop@mail2.ietf.org>; Fri, 18 Apr 2025 02:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_NONE=-0.0001, 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 54xnfYSxW0R5 for <dnsop@mail2.ietf.org>; Fri, 18 Apr 2025 02:46:16 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 CC1EC1E045C3 for <dnsop@ietf.org>; Fri, 18 Apr 2025 02:46:16 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id ffacd0b85a97d-3913d129c1aso1143498f8f.0 for <dnsop@ietf.org>; Fri, 18 Apr 2025 02:46:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744969575; x=1745574375; darn=ietf.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=oWvY11qJnBHy61iki0zT/8oW5ONlajoANsQTZLcErMM=; b=dHaF5wHV/ZhdEBuAxpYJ+gyLlAvc4pl3W25yW9WzMQ5k/HTu2w+bZaUKDzfH3DmsX6 oV8CfYU7qzVvfCzstgk8RnUgNO/7lf5L05Dqk+ZAbO2rgtvZFmKrI1WCtBjWZM8XY4RV Nj7VfOCf4hcywBQii7dcVwFgCZkQ6gwGLkNuMF4/exCdx6yQBkbF8eE0JFlMoQ9U9kaV KtEdNkb9J7PJeZ2H5Dfjy8uWCurYPgUdEoTOsJtmKZAjlhcEE+Qm+mnR/9bp46Qq2B4A JHAxhIU+9HcwfiQlXi+dlDaUvIaYY+1MaWa22lFRICUJoK8DjjEQBqeCTE0mvltZESj3 LHqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744969575; x=1745574375; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=oWvY11qJnBHy61iki0zT/8oW5ONlajoANsQTZLcErMM=; b=q1KVYY3PCRgN9Kwz0YUSmBkoOScmAY4kR7kBzW0SXQTweQTdniwoiglaPbRaGUa4cZ 00TZ4MMLJG4hTmaKOYqRYvHOzsqzi7ZNs+LsoStzonqj82pXKeZp8f8J3op5kG5R2Ewq lwEiwxFlcFmO407Bae9X/VqwYAgbdfgeDgTd1AHiqKeSsb19JzVf06CTDAvk6MKBMLnJ 0bJMJkv6E9cz0xWn5Rt22hkgJuGnw/uSTBsyfFzDa3Q243LdFbaphywcthO6Od6RY3Un pdE1epSq89U5dvpyWQzJA9viALdOlBC21fAPFFpVmjzZV2xgLkPO/1Fnubf+KheKv1Ro AKAA==
X-Gm-Message-State: AOJu0YyDendSLMnGPa1tE9AzIn0AYE+s7u5js4T5LLjXKkqgLuK21YVK 9ObEPPZqzqukx9wWNVV26+/IfcTfujlFPuVGGrqyMWBjlCYYfY4y6yLSNyZA
X-Gm-Gg: ASbGncvtQMROyJP/B4CDBjsbKefyQazbKYQCtesQvmkhjD6x8N6QdOatSxR1XHeTvLj BJH3luYUHfB0po86d7hg4ELqYBnXHKkPtXH2PqYxZbPOVI59hIP6C/x0OXWlkTSdytoHs0Oo6q7 ABOhtnJrYsq7vn5eNDbPiWsKV5tr2+a8tttqucdWBMgUsdJhR2kJkmX+eGSgAI/NhUgJ1dRRAmk J+kOcdAgHeKDGSPTi7HAVEUYWx5GQPxONVTTBQXe9cNVQDHOakajIE8NWpgPpWuFsMdpWui0hh+ Z9l7aP5bQJH+/jz6TTBDdQgfu7Rfqi1Ya7wo9KXF3aZyduYxFNnZZfteitmz
X-Google-Smtp-Source: AGHT+IHrWp0m5CRFOR7OI0fT/YSPD7QhP4A1vfv6kyamTcesnKnDI80JUM8l0DHD+QYN4l5Pm++OsQ==
X-Received: by 2002:a05:6000:1ac9:b0:391:98b:e5b3 with SMTP id ffacd0b85a97d-39efbd682e5mr1409754f8f.14.1744969575399; Fri, 18 Apr 2025 02:46:15 -0700 (PDT)
Received: from carbon.junesta.net (carbon.junesta.net. [2001:19f0:7401:8ac9::157]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-39efa4931e7sm2251935f8f.67.2025.04.18.02.46.14 for <dnsop@ietf.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 18 Apr 2025 02:46:14 -0700 (PDT)
Date: Fri, 18 Apr 2025 09:46:13 +0000
From: Karl Dyson <karldyson@gmail.com>
To: dnsop@ietf.org
Message-ID: <20250418094613.qndp4cu5ccelsahx@carbon.junesta.net>
References: <016201dbaee8$d1106580$73313080$@gmail.com> <B3F33508-46B5-4B19-A265-C4EAFE9D4000@strandkip.nl> <1C9E8ABA-4399-491B-A9F4-D9ACCB1BA72C@virtualized.org> <A7B914F4-78DF-4210-B8B3-49FE852646AD@rfc1035.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A7B914F4-78DF-4210-B8B3-49FE852646AD@rfc1035.com>
Message-ID-Hash: MT6MI5XPRPTBH2N6VHOPAWXSEJCQ5PV5
X-Message-ID-Hash: MT6MI5XPRPTBH2N6VHOPAWXSEJCQ5PV5
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
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/Ei3CjQP5lXGqCHJG-K-rkwaQ2DI>
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 Thu, Apr 17, 2025 at 07:22:18PM +0100, Jim Reid wrote:
> 
> Well there is the cost of setting up and maintaining some sort of registry which fully documents these special TLDs.* And the layer-9+ bickering over what does and doesn't go into this registry, who gets to decide, defining the criteria for adding or removing entries, etc, etc. IMO this isn't an issue for the IETF. I realise that ship has sailed because of earlier mistakes over the likes of .onion, .gns and friends. This doesn't mean we should repeat those mistakes.
> 

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.

>
> If ICANN or some other body wants to have some sort of registry for its "special" TLDs, they can go ahead and do that. There's nothing stopping them. They don't need IETF approval. IMO there's nothing for the IETF to do here - apart from keeping well away from those toxic swamps.
> 
> * I suppose developers and DNS admins will have costs writing/maintaining/configuring code to support these special TLDs. A perceived(?) IETF-approved registry for them will just encourage more of this unpleasantness.
> 

...does the registry not already exist, tho?

I agree that we don't want unpleasantness, but again; if it already
exists, we should be consistent at least.

Not wanting or having unpleasantness is perhaps a ship that has
sailed...


Best wishes,
Karl

-- 
Karl Dyson