<div dir="ltr"><div>Hi Tom and happy holidays and new year to you and the NCAP discussion group.<br><br>I saw an article about this over on Domain Name Wire and responded after confirming with the director of operations at ENS.<br><br>The NFT in this case was a gimmick for PR to promote UNR's efforts to bring as many parties to participate in the bidding process when they were attempting to sell off UNR TLDs.</div><div><br>The ENS project is complementary to ICP-3 and will not be generating name collisions beyond .ETH, which would have been unavailable due to it being ISO 3166 for Ethiopia and unlikely to get delegated under general circumstances.<br><br>Where TLDs are expressed in the ENS, they would be a TLD delegated via the ROOT maintained by the IANA. They are not creating any additional TLDs beyond those in the root managed under ICP-3</div><div><br></div><div>I suspect that the ENS project that won't collide was lumped in with the other blockchain _stuff_, like Unstoppable Domains or Handshake that have been inventing new namespace that will collide once application time would open with ICANN. <br><br>I describe the situation and possibility there are misunderstandings in my response on DNW. <a href="https://domainnamewire.com/2021/12/21/nfts-trip-up-uniregistrys-top-level-domain-auctions/#comment-2266982">https://domainnamewire.com/2021/12/21/nfts-trip-up-uniregistrys-top-level-domain-auctions/#comment-2266982</a></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><br>Jothan Frakes<br>Tel: +1.206-355-0230<br><br></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 22, 2021 at 12:24 AM Tom Barrett via NCAP-Discuss <<a href="mailto:ncap-discuss@icann.org">ncap-discuss@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">interesting blog post today:
<a href="https://domainnamewire.com/2021/12/21/nfts-trip-up-uniregistrys-top-level-domain-auctions/" target="_blank">NFTs trip up Uniregistry's top level domain auctions - Domain Name Wire | Domain Name News</a> where ICANN appears to be trying to block TLDs from integrating with blockchains.<div><br></div><div>See ICANN's letter here:
<a href="https://www.icann.org/en/system/files/files/reconsideration-21-3-dot-hip-hop-bamc-recommendation-request-16dec21-en.pdf" target="_blank">reconsideration-21-3-dot-hip-hop-bamc-recommendation-request-16dec21-en.pdf (icann.org)</a></div><div><br></div><div>Key paragraph:</div><div>"As an example, it has been unclear how such public statements as "the winner of each TLD will receive ownership rights to the Top Level Domain asset. .. [and.] ... the NFT representing their TLD on the ENS" so they could "control the entire TLD namespaces on DNS and ENS" were to be evaluated against the incomplete requests for assignment. As we have communicated to UNR, these statements may not be consistent with important ICANN community-developed policies and agreements that govern registry operations which clearly state that any registry operator would have no property ownership rights or interests in a TLD. Further, the creation of such NFTs and potential operation of a suffix identical to the top-level domains in the DNS in an alternate name space may create risks to security or stability of the TLDs in the DNS."</div><div><br></div><div> I know that NCAP has not addressed this (yet). Who has? Any thoughts?</div><div><br></div><div>Tom</div><div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><font face="arial, helvetica, sans-serif" size="2">Thomas Barrett</font><div><font face="arial, helvetica, sans-serif" size="2">President</font></div><div><font face="arial, helvetica, sans-serif" size="2">EnCirca, Inc</font></div><div><font face="arial, helvetica, sans-serif" size="2">+1.781.942.9975 (office)</font></div><div><font face="arial, helvetica, sans-serif" size="2">400 W. Cummings Park, Suite 1725<br></font></div><div><font face="arial, helvetica, sans-serif" size="2">Woburn, MA 01801 USA</font></div></div></div></div></div><div id="gmail-m_5135819393499953252m_2162789295124003921DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid rgb(211,212,222)">
<tbody><tr>
<td style="width:55px;padding-top:13px"><a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" target="_blank"><img alt="" width="46" height="29" style="width: 46px; height: 29px;"></a></td>
<td style="width:470px;padding-top:12px;color:rgb(65,66,78);font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free. <a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" style="color:rgb(68,83,234)" target="_blank">www.avg.com</a>
</td>
</tr>
</tbody></table><a href="#m_5135819393499953252_m_2162789295124003921_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div></div></div>
_______________________________________________<br>
NCAP-Discuss mailing list<br>
<a href="mailto:NCAP-Discuss@icann.org" target="_blank">NCAP-Discuss@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ncap-discuss" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/ncap-discuss</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div>