[NCAP-Discuss] ICANN says NFT's are a possible threat to the DNS

[Jothan Frakes]

Hi Tom and happy holidays and new year to you and the NCAP discussion group.

I saw an article about this over on Domain Name Wire and responded after
confirming with the director of operations at ENS.

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.

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.

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

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.

I describe the situation and possibility there are misunderstandings in my
response on DNW.
https://domainnamewire.com/2021/12/21/nfts-trip-up-uniregistrys-top-level-domain-auctions/#comment-2266982

Jothan Frakes
Tel: +1.206-355-0230



On Wed, Dec 22, 2021 at 12:24 AM Tom Barrett via NCAP-Discuss <
ncap-discuss at icann.org> wrote:

> interesting blog post today:   NFTs trip up Uniregistry's top level
> domain auctions - Domain Name Wire | Domain Name News
> <https://domainnamewire.com/2021/12/21/nfts-trip-up-uniregistrys-top-level-domain-auctions/>
> where ICANN appears to be trying to block TLDs from integrating with
> blockchains.
>
> See ICANN's letter here:   reconsideration-21-3-dot-hip-hop-bamc-recommendation-request-16dec21-en.pdf
> (icann.org)
> <https://www.icann.org/en/system/files/files/reconsideration-21-3-dot-hip-hop-bamc-recommendation-request-16dec21-en.pdf>
>
> Key paragraph:
> "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."
>
>  I know that NCAP has not addressed this (yet).  Who has?  Any thoughts?
>
> Tom
>
>
> --
> Thomas Barrett
> President
> EnCirca, Inc
> +1.781.942.9975 (office)
> 400 W. Cummings Park, Suite 1725
> Woburn, MA 01801 USA
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.
> www.avg.com
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#m_5135819393499953252_m_2162789295124003921_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> _______________________________________________
> NCAP-Discuss mailing list
> NCAP-Discuss at icann.org
> https://mm.icann.org/mailman/listinfo/ncap-discuss
>
> _______________________________________________
> 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 (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/ncap-discuss/attachments/20211222/6e8abc6a/attachment.html>