> On 4 Feb 2025, at 4:49 pm, Kim Davies <[email protected]> wrote: > > Hi folks, > > We have published a new version of the draft intended to document the > .internal top-level domain. > (https://datatracker.ietf.org/doc/draft-davies-internal-tld/) > > When we presented this work in Dublin, there was a lot of discussion both in > the meeting, and subsequently, on whether this should be a work item and also > whether the domain merited consideration as a special-use domain name per RFC > 6761. I don’t think there was clear consensus on either, but to further the > discussion on the latter point, Warren Kumari has provided strawman text to > stimulate discussion.
I have discussed this with Warren. Upon reflection I think that its a domain name with special use considerations that would largely fit into RFC6761 critera. The fact that this name "allocation" was the work of ICANN is less relevant in this context than the observation than a duly qualified body who can make such name allocations has indeed done so merits recording in the registry. Nit: Section 5.1 says: (Editor note (WK): It not yet decided if .internal should be added to the list of special-use domain names at https://www.iana.org/assignments/special-use-domain-names/ (https://www.iana.org/assignments/special-use-domain-names/).' while near the end of the document it says: Notes (for removal before publication) * It is currently assumed this domain should NOT be designated as a special-use domain name at https://www.iana.org/assignments/special-use-domain-names/ (https://www.iana.org/assignments/special-use-domain-names/). It seems to me that the Note should be removed. Thanks, Geoff
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
