DNS: A Safe Haven
|Making handle assignment political, threatens the basic "glue" of the Internet.|
The strength of the Internet is its simplicity. Fortunately we can preserve the simplicity of domain names by creating a "safe haven" of DNS names that are not subject to the controversies being addressed by ICANN. This can be done within the existing DNS framework and without requiring that current users change their practices. To reduce confusion, we can use the term "handle" rather than "name" for these identifiers.
The problem is that in addressing the issue of the scarcity of commercially meaningful names has made the assignment of names a political rather than a technical process.
The solution is to create a "safe haven" of handles that have no semantics and thus assure that the process of assigning them is as simple as taking the next number.
This allows ICANN to focus on the apolitical function of assigning identifiers rather than issues of commerce and policy.
|Updated August 2001 with thanks to David Reed for helping to clarify this point.|
Ever wonder why so many people are called Smith or Miller? The answer has a lot to do with the current confusion over what to do with the DNS. Once upon a time, people's surnames were their occupation - it was a simple way to sort out the Johns and Thomases from each other, and also served as a cheap form of marketing. But eventually, the use of surnames as a distinguishing mark faded because it became more important to have stable names that didn't change when a family member took up a new occupation.
The stability of names becomes necessary when you are dealing with groups much larger than a village — the name you know someone by can be passed along to friends, and with that name goes the implied trust that you pass along with it.
As the Internet has grown from a village to vast anonymous cyberspace, stability of DNS names has become increasingly necessary — it is the "glue" that enables links between websites to remain stable over time. These names become handles rather than descriptions.
But this stability is in conflict with the idea of names as tradeable property whose value is in what they "advertise". It is as if top-level domain names such as ".miller" or ".smith" must somehow be tied to "real" people who mill corn or hammer iron.
So instead of migrating to a system of relatively meaningless handles (as surnames have done), the whole DNS community seems bent on a foolish errand — to make the DNS namespace a repository of meaning, to go head-to-head with the search engines who do a much better job of capturing meaning.
Rather then being a simple registry, using simple mechanisms like "First come first served", the DNS names have been turned into assignable "property rights". Speculation about what DNS names may be worth continues well past the dot-com crash. And lawyers, presuming that names ought to be valuable, try to craft legal frameworks that impose that value system on the rest of us.
Can this be prevented? Not as long as we insist on the meaning of the names rather than their role as a stable handle. But in this "fools gold rush" it is important to ensure that there is still a "safe harbor" of stability, where a name cannot be usurped merely at the whim of a plaintiff who can convince a court. In the long run, the valuable names with be those that are compatible with intelligent search strategies, but to preserve the stability of the underlying Internet information and processes, we must make sure that inexpensive stable names are available to glue together such things as the World Wide Web and our digital relationships.
The DNS is a simple system serving a vital purpose. Each registry stores information records. There are records for providing the IP address of a system with a given handle, records that specify mail delivery routes, other records that can transfer authority to named subdomains, etc. See the technical backgrounder for more details.
Just like an animal threatened with extinction because of its valuable pelt, the DNS is threatened because the identifiers can have commercial value as names. While we cannot save tigers by painting them green, we can preserve the DNS by creating a safe haven of handles that do not have commercial value. Thus, instead of Frankston.com, one may have 123-3.1231.zzz.
These names are just like phone numbers. To avoid confusion, we can refer to these as domain handles.
Just as with phone numbers, one would use a directory service to translate a descriptive name into a handle. Unlike the problems associated with the scarcity of .COM names, the mapping of names into phone numbers is a well-established process within an existing legal framework.
The use of directory services works even better with computers. With current browsers one can type a name directly into the address line and be presented with likely alternatives. The choice can be stored in one's address book.
We can go one step further and allow the phone numbers themselves to be used as handles in a .phone.int domain, though phone numbers themselves are not currently long-term identifiers.
The simple function of assigning names and numbers has been complicated by a focus on the intellectual property issues associated with commercially valuable domain names. These issues are only a side effect of the use of the English alphabet for DNS identifiers. Unfortunately, the result has been to expand ICANN's charter into a role of trying to control the use of the Internet. This threatens the fundamental mechanisms that have allowed the Internet to become the economic engine of the 90's and beyond.
The power of the Internet is in the ability to create infrastructure without a separate wire for each connection. Connections are made using handles such as IP addresses and DNS keys. Making handle assignment political threatens the basic "glue" of the Internet. ICANN can revoke handles and thus invalidate the linkages (such as URLs) that hold the Web together.
In fact, there is no "Internet" as such. The term is applied to the collection of systems that use common protocols and handles. Thus the assignment of handles is a vital function. IP addresses provide the fundamental links between systems. Services, such as the World Wide Web and Email need a permanent handle in order to assure stable and long term linkages.
The difficulty of defining the boundaries of the Internet exacerbates the problem of legitimizing the authority of ICANN thus creating additional controversy.
We can separate out the controversial political issues of ICANN from the basic function of assigning names and numbers (handles) by addressing the artificial scarcity. There is no shortage of domain names, just a shortage of ones that have commercial value. ICANN need only assign the next integer for second level domain names. Most domains will be below these so there shouldn't even be a large demand for such names.
These second level registries would be similar to the current top level registries except that there would need be no arbitrary limits such as allowing only one per country. Anyone who has a registered domain can create additional domain registrations at lower levels. These registries have no cost and be easily created and abandoned (if the owner chooses) thus facilitating innovative use of these handles.
The other artificial scarcity is the IPV4 address. This must be addressed in order to provide end point identifiers for the billions of devices that will be connected using Internet protocols. The details of how to implement this are still being worked out with IPV6 being the current specification. But the result must be to make the process of assigning new addresses a clerical operation and the issues of how to route messages a technical issue.
The complex issues of trademarks and intellectual property are not new and have nothing to do with the operation of the Internet. They are only "Internet" issues because of the focus on .COM to the exclusion of other directory mechanisms. Issues of copyright protection and intellectual property are exacerbated by the increased connectivity but are not Internet issues per se.
The "safe haven" approach of creating noncontroversial domain names is remarkably simple and can be implemented within the existing DNS framework. Doing so won't remove the controversies associated with existing names but it will assure that they do not threaten the basic mechanisms of the Internet.
The Safe Haven doesn't require any technical changes to the DNS; it just opens one new top level domain and a small number of second level domains to ease the technical and managerial burden on the DNSO.
ICANN was created by Congress to address trademark and other issues. Why is this proposal directed at ICANN?
One reason is that the DNSO, which manages the DNS, reports to ICANN so it does have responsibility. This proposal gives ICANN a way to assure the technical viability of the IP Infrastructure by providing leadership and drawing a line between the technology and the policies.
This proposal does nothing to resolve the issues with .COM. People will still want their vanity names.
True. But the problems with .COM are fundamentally intractable. They do not, for example, reflect the use of geography and industry classifications that are vital to resolving names. Guessing a .COM name doesn't hint at other's who might have the same business name. .COM is simply unable to provide easy-to-guess names for individuals whose names are not unique. Instead, this proposal is the basis for a cleaner approach that doesn't inherit from .COM.
How do I tell someone my URL if I can't give them a simple name?
We've already developed many ways to deal with this for phone numbers. If you can't get a person (or company) phone number directly, you go to one of the directory services. The growth of national directory services in the US (and, eventually, world wide) demonstrates the improved capabilities for providing such services. These can handle URLs just as easily. Even better since the same technology obviates the need for retyping the URL. If one looks up the number online the URL is already on the computer and can be automatically stored in the local address book. Try typing a name into a recent browser. If it's a company name, you'll see a proposed first choice and other likely choices. It's as easy as typing the .COM name with the added advantage of identifying alternatives. Without the bias towards .COM there can be an effective marketplace for such services. Specialized services would do a better job in their areas of expertise such as business-to-business, school friends, genealogical searches etc.
How does this new "Safe Haven" actually work. Will there be a massive registry will billions of entries?
While a single massive directory might work, it isn't necessary and is probably not a good idea. Instead, the DNSO can make it easy for others to provide the services. Any organization (or individual) requesting an entry in the new hierarchy (or Top-Level Domain) would be assigned one. Each name would be of uniform length, perhaps a mixture of letters and digits. One question is whether there should be any requirements of performance or an escrow mechanism so that those who register with these registrars would have some assurance of permanence. But there is no need to extend such governance to additional levels.
But typing this new names will be difficult since they will be hard to remember and hard to type.
There should be little reason to type a URL. It's already the case that many URLs are long. The favorites mechanism and, of course, clicking obviate the need for typing. As noted, one can type a name rather than the URL on the address line in the browser. The same search tool can be made available wherever it is useful to type a URL. One other refinement is to integrate the local address book and favorites list into this search. These are technologies that are already available and just need to be refined.
Don't we get the same problem with Real Names and the other new services?
Some of the providers will do a better job than others and some will seek advantage by tactics such as getting their names embedded in URLs. But unlike the stranglehold of .COM, a marketplace for such services will serve to limit the degree to which one player can recreate the current dominance of .COM
What about cybersquatters, pirates and child pornography?
Cybersquatting becomes moot in the absence of this artificial scarcity. The other issues are associated with how the Internet is used. The traffic on the network itself consists of bits that have no meaning. Controlling illegal behavior is indeed a societal issue. But it cannot be addressed by building "smarts" into the Internet. The only effect is to frustrate those trying to enforce rules and, worse, make it difficult to use the Internet for other purposes. Appeals to protect children must be viewed with suspicion Not because protecting children is not vital (it is indeed important) but because such appeals can be used to mask bad policies and hidden agendas.
Isn't it too late to do any of this?
No. This proposal doesn't require any new mechanisms and it doesn't require changing current behavior. What it does is assure that there is a reliable system for stable handles. The issue of resolving .COM conflicts still exists but is no longer critical. It is possible to create new and better solutions. By taking the pressure of .COM, the problems won't get worse and can become less important in the face of much better alternatives.
What if one company becomes dominant and thus has the same control as .COM
It's a very big world (and not just the United States) with lots of players competing. We see examples in the search engine and directory services. The big opportunity for competition is in moving beyond simple naming services to matches based on other criteria such as how close a store is or what other products it sells. In the worst case, it's still a much better situation than we have now since that provider will not still not control the underlying linkages and will not have official authority over the naming system. Thus the dominance can be challenged without damaging the underlying infrastructure.
Isn't the IP address more appropriate as a technical handle?
The IP address cannot serve as the handle for applications because it is associated with a system rather than applications. One can create a DNS name for each application. The URL is more appropriate, but it still is dependent upon the DNS name. In practice, the IP address is more problematic since it is generally considered to be owned by the access provider and is frequently reassigned as the Internet routing changes.
Why not just create .SHOP and .PIZZAWITHANCHOVIES as top level domains in order provide for more names and remove conflicts?
Because it makes things even worse. It means that each business must declare the type of business it is in an unambiguous taxonomy that doesn't reflect the complexities of the real world. Nor does it remove conflicts between Joe's Pizza in Cleveland and the one in Singapore. What is the domain for the sandwich shop/dry cleaning business (a real example). And it doesn't do anything for the "John Smith" problem. This proposal is part of what is most frightening about mixing social policy with technology. It builds a naive and short-sighted "solution" into the infrastructure and exacerbates the problem. This is part of the reason why it is so vital that we create a "safe haven". This of .good and .bad why they can't work.
How can I start using these new "meaningless" URLs without waiting for it to be fully implemented?
Browsers and servers generally support redirect capabilities. You can still advertise a simple public name such as http://www.myeasyname.old and have it translated into http://188828281282232.numbers/MyEasyName. This user won't have to type the new names but it will be provided by the browser in response to the simple name for future connections. You can include a descriptive name as part of the path so that can understand the URL even if it is hard to remember.
This document is a "work-in-progress" as I discover more issues and improve my understanding. Rather than rewrite this document, the goal is to work with others to produce an implementation proposal.
This is the point mode in the "It's even Worse!" section. The problem is exacerbated because URL's are used in many contexts. For example, they are used to create unique namespaces for XML as well as provide the definitions and presentation templates for XML.
After typing http://www.microsoft.com or other variations, the problem confusion of the DNS with a directory service is even more evident. Trademark law protects not just the exact name but other names that could be confused. Thus Lexus the car and Lexis the search service went to court to resolve their issues. Eventually both were allowed because they were in different industries. In the DNS neither problem is addressed. Theft by similarity is rife and there is no concept of "different industry". Creating the crime of "Cybersqautting"is a clumsy attempt to address the similarity issue.