[NCAP-Discuss] .INTERNAL proposed as string to meet SSAC113 request….

[Warren Kumari]

Hi there all,

"SAC113 - SSAC Advisory on Private-Use TLDs
<https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-113-en.pdf>"
requested that ICANN reserve a string for private use, and that the string
be:
1. A valid DNS label
2. Not already delegated in the root zone.
3. Not confusingly similar to another TLD in existence
4. Relatively short, memorable and meaningful.

The ICANN board asked the IANA to select the string, and I'm please to
announce that they have identified “INTERNAL” as appropriate for this
purpose.

Prior to review and approval of this reservation by the ICANN Board, they
are seeking feedback on whether the selection complies with the specified
procedure from SAC113, and any other observations that this string would be
an inappropriate selection for this purpose. See the Public Comment page
<https://www.icann.org/en/public-comment/proceeding/proposed-top-level-domain-string-for-private-use-24-01-2024>
for link to provide input

Unsurprisingly[0], I think that this is a great option, but (obviously)
please provide whatever feedback you have….
W

[0]: See Matt Thomas' recent mail (Subject: [NCAP-Discuss] .internal) to
the list,
https://datatracker.ietf.org/doc/pdf/draft-wkumari-dnsop-internal-00,
SSAC113, the fact that I keep droning on about this string and it being
used in various cloud providers, etc as to why y'all probably won't be
surprised that I personally think its a good choice…
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/ncap-discuss/attachments/20240124/c8465026/attachment.html>