3,197
edits
Changes
→Further Proceedings
===ENS Reliance on/connection to DNS===
===ENS Reliance on/connection to DNS===
The Ethereum Name Service is compatible with the [[DNS]], and if a domain owner wants to utilize their web address as an Ethereum wallet address, they must enable DNSSEC protocols on the domain, add an "_ens" record to the DNS records of the domain through their registrar, and complete additional steps to establish the connection between a specific wallet and the associated human-readable name.<ref name"dnstoens">[https://medium.com/the-ethereum-name-service/step-by-step-guide-to-importing-a-dns-domain-name-to-ens-d2d15feb03e8 Medium.com - Step-by-Step Guide to importing a DNS domain name to ENS], August 26, 2021</ref> It is possible that this technical interoperation is the source of ICANN's concern regarding the bundling of an ENS NFT with a TLD. However, this cross-compatability exists in the status quo now, so it is unclear how bundling the right to act as an "ENS registry" for a specific domain is independently problematic.
The Ethereum Name Service is compatible with the [[DNS]], and if a domain owner wants to utilize their web address as an Ethereum wallet address, they must enable DNSSEC protocols on the domain, add an "_ens" record to the DNS records of the domain through their registrar, and complete additional steps to establish the connection between a specific wallet and the associated human-readable name.<ref name"dnstoens">[https://medium.com/the-ethereum-name-service/step-by-step-guide-to-importing-a-dns-domain-name-to-ens-d2d15feb03e8 Medium.com - Step-by-Step Guide to importing a DNS domain name to ENS], August 26, 2021</ref> It is possible that this technical interoperation is the source of ICANN's concern regarding the bundling of an ENS NFT with a TLD. However, this cross-compatability exists in the status quo now, so it is unclear how bundling the right to act as an "ENS registry" for a specific domain is independently problematic.
===Further Proceedings===
In response to ICANN's requests for information, Uniregistry at some point notified ICANN that the NFTs related to the TLDs had been destroyed.<ref name="jjblog">[https://www.icann.org/en/blogs/details/relying-on-icann-community-developed-processes-for-a-safe-secure-internet-5-1-2022-en ICANN.org Blog - Relying on ICANN Community Developed Processes for a Safe and Secure Internet], January 5, 2022</ref> This did not appear to assuage ICANN's concerns regarding the marketing of the auction.<ref name="jjblog" /> Indeed, ICANN's public response to the community indicated that it was more concerned about the marketing materials that conflated "assignment" of Uniregistry's rights with "ownership" of a particular TLD. Industry observers pointed out that this was both common parlance for registry operators, and in any event was best described as puffery.<ref>[https://en.wikipedia.org/wiki/Puffery Wikipedia - Puffery]</ref><ref>[https://domainnamewire.com/2022/01/13/icann-explains-its-side-of-unr-registry-transfer-holdup/ Domain Name Wire - ICANN Explains its Side of the UNR Transfer Holdup], January 13, 2022</ref>
==References==
==References==