New RFC on Private Namespace TLDs

[james@icann.guru]

There has been some extensive discussion on this in dnsop that I suggest folks read through also https://mailarchive.ietf.org/arch/browse/dnsop/ 


---
James Gannon
On 6/16/2020 5:46:12 PM, Bruna Martins dos Santos <bruna.mrtns at gmail.com> wrote:
Hey all, 

Just saw this discussion on the SubPro mailing list, and decided to share it with you.  A new informational RFC on the creation of private namespace TLDs was just submitted, you can find the description below: 

(...)  The ISO 3166 standard is used for the definition of eligible designations for country-code top-level Domains. This standard is maintained by the ISO 3166 Maintenance Agency. The ISO 3166 standard includes a set of user-assigned code elements that can be used by those who need to add further names to their local applications. 

Because of the rules set out by ISO in their standard, it is extremely unlikely that these user-assigned code elements would ever conflict with delegations in the root zone under current practices. This document explicitly reserves these code elements to be safely used as top-level domains for private DNS resolution."
<https://datatracker.ietf.org/doc/draft-arends-private-use-tld/?include_text=1 [https://datatracker.ietf.org/doc/draft-arends-private-use-tld/?include_text=1]>


The document speaks a little bit about the use of strings to facilitate private spaces within the DNS, and this RFC seems to touch upon the topic of special use domains that was also under discussion by the New Subsequent Procedures WG. 

Sharing it on the list because I would love to hear your thoughts on the matter. 

best, 

--

Bruna Martins dos Santos 

Skype ID: bruna.martinsantos

@boomartins
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20200616/5691ae90/attachment.htm>