IETF Logo Mail Archive

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

Jim Reid <jim@rfc1035.com> Wed, 23 April 2025 16:49 UTC

Return-Path: <jim@rfc1035.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 AB8B920216BA for <dnsop@mail2.ietf.org>; Wed, 23 Apr 2025 09:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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
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 iMND93nk1t2Z for <dnsop@mail2.ietf.org>; Wed, 23 Apr 2025 09:49:23 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (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 5B813202164C for <dnsop@ietf.org>; Wed, 23 Apr 2025 09:49:21 -0700 (PDT)
Received: from smtpclient.apple (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 3DD1A242109E; Wed, 23 Apr 2025 16:49:20 +0000 (UTC)
From: Jim Reid <jim@rfc1035.com>
Message-Id: <F8CE0CB6-6F52-440F-B32E-C230E02589E7@rfc1035.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DC4A36FD-BD73-4AD4-AE3A-9CA735DD566F"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Date: Wed, 23 Apr 2025 17:49:19 +0100
In-Reply-To: <39E139A3-A903-4D1E-BB5D-31368EF5C8B9@icann.org>
To: Paul Hoffman <paul.hoffman@icann.org>
References: <m1u5h1G-0000LcC@stereo.hq.phicoh.net> <83666fd3-a51f-46e1-a5ac-0b9a46361480@desec.io> <49E3B1B6-E960-4A46-9C5D-2721FD57132D@depht.com> <3b5fb9e7-8a2b-420f-a2fb-dd6f6a0b88ae@isc.org> <89047B78-A2B1-43F2-A996-94DF1E90538A@depht.com> <cc84f69c-c349-4d91-b942-80221b564a9b@isc.org> <ac48e27d-479f-42f3-b87f-891220ef2fe8@app.fastmail.com> <BE721880-6254-48F4-9F91-567A99E0511B@icann.org> <m1u7asT-0000MtC@stereo.hq.phicoh.net> <BB8275F1-538D-46B0-BFFA-F561A583EBFF@rfc1035.com> <39E139A3-A903-4D1E-BB5D-31368EF5C8B9@icann.org>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
Message-ID-Hash: BFUKR7FQGRJ5DNMKB4KQXVE7KM7CKZZ2
X-Message-ID-Hash: BFUKR7FQGRJ5DNMKB4KQXVE7KM7CKZZ2
X-MailFrom: jim@rfc1035.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" <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: [Ext] 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/oeszDbvBO73LjgruvcyGE02T0B0>
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 23 Apr 2025, at 17:15, Paul Hoffman <paul.hoffman@icann.org> wrote:
> 
> I'm 99% sure that there is no policy statement about "will never delegate" for .home, .corp, and .mail, but I could be wrong. I'm interested in any references to something official here that says "never", for many reasons.

You're picking nits Paul. AFAIK you're right. ICANN might not have literally said "never". However it has said these strings will not be considered for delegation until the security and stability concerns around them have been satisfactorily addressed*. Which pretty much means they'll never get delegated.

* Or words to that effect. I'm too lazy to dig out verbatim quotes. Paraphrasing what was said should be good enough for the thread here. The key point is ICANN put .home, .corp, and .mail on some sort of "do not delegate" list and that action didn't involve the IANA SUDN registry. Quibbling over the detail is unhelpful.

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