| I actually did a "side project" to fix this about 10 years ago. Never "released" it; I just wanted to see if it would work. I still think it could. Imagine being being able to get a copy of a zone file and that file reliably revealing something about what was being served from the associated IP address. Where each name was by the nature of its tld disambiguated from any other name. "Collision-proof" naming. Arguably, it already exists IRL. As a member of the public I can get a list, or search a database, of trademarks that reveals exactly what type of goods or services each mark ("name") covers. I do not need to submit each name/good/service I am interested in to a gatekeeper advertising company who will try to guess what it is I want based on other people's searches or personal information gathered about me. OTOH, if, for example, a trademark office started running an authoritative nameserver, serving its own zone with its own descriptive tlds and giving trademark registrants a matching domain name within a class-specific tld, I would not hesistate to add those tlds to the custom root.zone I use. It stands to reason that a business owner should trust a government entity with some accountability more than it trusts a made-up "authority" like ICANN. The "organisation of the world's information" should not be controlled by a private company. Any such company would obviously stand to benefit from the continued disorganisation of information on the web. A lack of organisation that only they have the "expertise" necessary to rectify. The ambiguity of ICANN domain names is one contributor to the ongoing state of disorganisation. Nor should the control of domain names be entrusted to a private company. They, too, benefit from the ambiguity. The profits from selling (through contractors) dispute resolution services and then new tlds to trademark holders are only possible when the ambiguity continues to exist. |