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

[John Levine <[e-mail]>]

It appears that Paul Hoffman  <[e-mail]> said:
>On Apr 23, 2025, at 09:07, Jim Reid <[e-mail]> wrote:
>> ICANN already has its own list/registry of TLD strings it will never delegate: .home, .corp, .mail, etc.
>
>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.

There are 43 two letter "user assigned" ISO 3166 codes that will never be
assigned to geographic places, so I think it is safe to assume they will never
be TLDs. The AGB for the last round had a list of 33 reserved names on pages 2-9
and 2-10 that I doubt will ever be delegated. I would be pretty surprised if I
were the only person squatting on one of those names on his private network.

I don't see any reason to treat .INTERNAL differently from .NIC or .AA. None of
them are delegated, none will be delegated, and if you use them internally,
you'll have to do something local if you validate DNSSEC.

Since this issue of "yeah it works if you trust your network's resolver but not
if you do your own DNSSEC checks" comes up over and over again I think it would
be worth looking at ways for networks to tell their hosts what the local trust
anchors are, but that's a separate can of worms.

R's,
John