Changes

Jump to navigation Jump to search
no edit summary
Line 156: Line 156:     
===Functionality===
 
===Functionality===
Commentators note that alternative name systems today are clunky, hard to reach, and expensive; they put the onus on browsers, which do not want to govern.<ref>Tyler Mason, GoDaddy Blockchain Domain Names Webinar, 12/1/2021</ref> Adapting applications to use multiple alternative naming systems is complicated and particularly if the names overlap. Applications would have to know which alternative naming system to look up for each domain name or define an order for making the lookups. The approach for defining an order in the DNS has proved non-deterministic and problematic.<ref>[https://www.icann.org/en/system/files/files/octo-034-27apr22-en.pdf Challenges with Alternative Name Systems, pg. 8, ICANN OCTO, April 27, 2022]
+
Commentators note that alternative name systems today are clunky, hard to reach, and expensive; they put the onus on browsers, which do not want to govern.<ref>Tyler Mason, GoDaddy Blockchain Domain Names Webinar, 12/1/2021</ref> Adapting applications to use multiple alternative naming systems is complicated and particularly if the names overlap. Applications would have to know which alternative naming system to look up for each domain name or define an order for making the lookups. The approach for defining an order in the DNS has proved non-deterministic and problematic.<ref>[https://www.icann.org/en/system/files/files/octo-034-27apr22-en.pdf Challenges with Alternative Name Systems, pg. 8, ICANN OCTO, April 27, 2022]</ref> Web gateways do not require any set up on the client's side, but they have to be maintained over time, must scale with demand, and are a single point of failure and a target for [[Threat Actor|malicious actors]].
</ref>
      
====Early altroots====
 
====Early altroots====
Bureaucrats, Check users, lookupuser, Administrators, translator
14,927

edits

Navigation menu