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

[Suzanne Woolf <[e-mail]>]

Hi,

David said this better than I was about to:

On Apr 17, 2025, at 6:57 PM, David Conrad <drc=[e-mail]> wrote:


On Apr 17, 2025, at 2:51 PM, Jim Reid <[e-mail]> wrote:

How does that make things better (or stop them getting worse)?

Since the IETF is deemed to have change control over the DNS, it means folks who are trying to develop/operate DNS implementations have one place to go to instead of trying to figure out through rumor, lore, and oral tradition what the rules are.

(Note: I'm making a distinction between efforts like .internal that assume the use the DNS protocol from the various non-DNS efforts like GNS)

I’ll also note that we can sidestep the issues around the SUDN entirely:

On Apr 16, 2025, at 5:19 AM, S Moonesamy <[e-mail]<mailto:[e-mail]>> wrote:

"The IAB/IETF did not voice any objection to the ICANN Board permanently reserving a top-level string according to the ICANN Board minutes for the meeting dated 24 July 2024.  The expectation of the IETF Chair and the IAB Chair was that the string be reserved within the IANA-managed reserved domain registry rather than the special-use domain names registry.  There is an editor note in Section 4 of draft-davies-internal-tld-03 which states that: "It not yet decided if the "internal" top-level domain should be added to the list of special-use domain names".  The positions taken are somewhat contradictory.

The Liaison correspondence between IETF and ICANN regarding the .internal issue, including a link to the original letter from the ICANN CEO, is at https://datatracker.ietf.org/liaison/1706/.  Taking the IAB/IETF advice there allows for clear meaning to the reservation of the string, in both the IETF and ICANN contexts. In the IANA “reserved” registry, it's clearly under the control of IANA and separate to the SUDN registry.

(The reserved domains registry is not in the usual place because it’s not an IETF registry; as the liaison statement notes, it’s an IANA registry and can be found at https://www.iana.org/domains/reserved. The IETF wouldn’t be directing the reservation of .internal in an IETF registry but providing information that IANA had reserved it, in an Informational RFC.)


Suzanne