|May the source be with you, but remember the KISS principle ;-)|
|Contents||Bulletin||Scripting in shell and Perl||Network troubleshooting||History||Humor|
|News||See Also||Recommended Links||One History of DNS||Humor||Etc|
by Ross Wm. Rader, firstname.lastname@example.org
Wednesday, April 25, 2001This is the html version of the file One History of DNS See also [PPT] Building a Better DNS
Like most Internet protocols, DNS (or “Domain Name Service) is 10% technical in nature and 90% political, which means that it is the conscious product of human design. Also like most other protocols, no one really realizes this until the time to make a change has long passed. The most unfortunate side effect is that the average person, who is generally the most affected, has little or no opportunity to participate in the process.
DNS acts as the backbone to the Internet. It is important to understand the dynamics that shaped the system. Why is ICANN important to every single person that uses the Internet? What role does the United States Government actually play behind the scenes? How did Network Solutions get to where they are today? The answers to these questions have, and will continue to determine what the Internet looks like today and what it will look like tomorrow. As George Santayana said, “Those who cannot remember the past are condemned to repeat it.” Without the benefit of these answers, the scope and scale of accomplishment in this sector will be limited.
“In [the early days] there was no ‘commercial motivation’… ”
- Dr. David Mills
The evolution of DNS has been long governed by technicians and politicians. Often time, the same people simultaneously assumed both roles. This makes it very difficult at times to look back at the events that critically shaped DNS and determine what really happened. Anthony Rutkowski, Vice President of Internet Strategy for Network Solutions Inc. stated, “The evolution of the Internet's method for names and number assignment is one of the Internet's most enduring and difficult transitions.”When Doug Engelbart created the ARPAnet NIC (Network Information Center) at Stanford’s Research Institute in 1967, DNS did not exist.
The network was small enough that the users and servers generally knew how to get around from service to service and interact with each other without the benefit of a global directory structure. As the network grew in size, it became apparent that such a service would be important, but due to scale reasons, it was never quite taken to its conclusion. Instead, in 1971, Peggy Karp conceived of “host mnemonics” (RFC 226), or more simply, Internet names.
Building on the concepts contained in RFC 226, she created lookup table that mapped all of the network resources in one text formatted file. Called “HOSTS.TXT”, the table contained all of the hostnames and their related IP addresses. Operators would install this file on their local server, which would then gain the capability to perform the requisite lookups locally and enable the computer to find resources out on the larger network without a lot of overhead. Whenever an operator added a new machine to the network, they would complete an email template with the appropriate information, send it off to the appropriate people at Stanford Research Institute (SRI) who would compile all of the changes and include them in the next release of HOSTS.TXT and store the new file on a globally available FTP server. Operators would retrieve the updated versions on a regular basis and install them on their local servers. The first version of this table was distributed in 1972. While this arrangement worked well for a number of years, but it suffered from one systemic problem – it wasn’t scalable.
As the network grew in popularity and new hosts were added, the size of HOSTS.TXT grew in direct relationship. For each host on the ARPAnet, HOSTS.TXT added a new record. Further exacerbating this problem of scale were the problems of authority. If operators did not update their records on a regular basis, HOSTS.TXT would grow out of date which led to name collisions and all sorts of confusion. Name collisions occur when the network thinks that more than host shares the same domain (i.e. ‘rader.example.com’produces an answer of both 10.10.10.141 and 10.10.10.25). On the brighter side, it was the success of the ARPAnet that led to the failure of the lookup service. Needless to say, both of these issues led the engineers of the time to come to the conclusion that a new structure would have to be put into place to replace HOSTS.TXT.
The Domain Name System was conceived in RFC (Request for Comments) 799 in 1981. Written by Dr. David Mills who was at COMSAT at the time, RFC 799 outlined the concepts and facilities required for an Internet Name Domains system that would eventually scale to facilitate addressing of “thousands of hosts”. Although a working solution to the much larger problem resulted, Mills initial intent was much more practical. “… The emerging intercommunity mail forwarding of the time was highly fragmented and ad hoc. Everyone knew that the mail world would eventually be fragmented according to conventional organizational principles. My interests [in creating Internet Name Domains] were more focused on the mechanics of doing this and on mail forwarding principles for the Internet. Not the least of my concerns were the mechanisms for handing off mail between forwarders and handling errors as they might develop,” He recently commented.
Interestingly enough, the solution would ultimately address a problem far larger than what Mills had originally designed. As Mills observes in the RFC, “it will not be practicable for every internet host to include all Internet hosts in its name-address tables. Even now, with over four hundred names and nicknames in the combined tables, this has become awkward.” The current DNS supports millions of host entries.
RFC 819, written by Jon Postel from the Information Sciences Institute (ISI) at the University of Southern California (USC) & Zaw-Sing Su from Stanford Research Institute (SRI) in 1982 built on the earlier work by Mills and gave the first general outline of the DNS structure and how it would allow for easier cross-network access. In November of 1983, Dr. Paul Mockapetris, also from ISI, published a request for comments to the Internet community entitled “Domain Names – Concepts and Facilities” as RFC 882 and “Domain Names – Implementation and Specification” as RFC 883. These two papers (later made obsolete by RFC 1034 and RFC 1035) outlined a completely new way of managing host name lookups. Most importantly, they included two very important concepts, delegation and authority.
Authority can be described as the “sphere of influence that one has complete control over”. In the case of DNS, this is true on a zone-to-zone basis. A zone consists of the sub-domains that fall directly beneath any given domain. For instance SRI has authority over all domains created below sri.com including mail.sri.com, www.sri.com, ftp.sri.com, usenet.sri.com, and so on. Delegation described the process by which someone gains authority for his or her zone. SRI Network Operations might delegate authority to their Hong Kong office for hk.sri.com. The Hong Kong office would then beauthoritative for the hk.sri.com domain and all sub domains that fell underneath it (for instance, mail.hk.sri.com and so on.) The Hong Kong office could also delegate authority to another party for the fourth level domain to yet another third party.
Delegation is the basis upon which all power and conflict in the DNS today is derived.
When the design work was finally complete, Jon Postel and Joyce Reynolds wrote RFC 920, which outlined the groundwork that had to take place and set the rapid pace at which the change would occur. RFC 920 was also significant for another reason: it outlined the initial top-level domain names that would be added to the DNS when it was finally deployed. These included .com, .net, .org, .edu, .gov, .mil and .arpa. The document also outlines plans for the creation of country- related TLDs using the two letter ISO (International Standards Organization) codes (becoming, .ca, .us, .uk etc) and TLDs for “multiorganizations” that called for the creation of TLDs for organizations that were “… large, and composed of other organizations; particularly if the multiorganization can not be easily classified into one of the categories and is international in scope.” The concept of multiorganizational TLDs was later assumed under the .int TLD.
The successful deployment of DNS made it apparent to the Defense Communications Agency (the “DCA”, now called the “Defense Information Systems Agency” or “DISA”) that a centralized management structure was necessary to manage the root and delegate authority to registrants within that root. As the DCA had split the ARPAnet into the ARPAnet and MILnet in 1993 (With MILnet becoming integrated into the Defense Data Network (DDN) shortly thereafter), it was important that whomever they choose to manage the technical operations of the root and the registry did so in a manner consistent with the requirements of the military.
The DCA chose the Stanford Research Institute to manage the registration of all domain names in the new DNS and awarded the root management and the operations of DDN-NIC (Defense Data Network Network Information Center, a semi-private digital packet switched network meeting the United States Department of Defense’s stringent communications standards) to ISI. After all, who better to manage the services, but those that had created it? In March of 1985, all of the work paid off and the first domain names were registered. (Some claim the very first “.com” was “symbolics.com” and others, “think.com”). By most accounts, 1985 was the year that the “Modern History” of DNS actually began.
For a number of years, the evolution of DNS progressed smoothly and functioned very much as back-office support to the operation of the network. In 1986, the growing needs of the academic community led to the creation of the NSFnet by the United States National Science Foundation, which awarded the backbone management contract to Merit Networks Inc. in 1987. The NSFnet was the last incarnation of the network prior to the Internet that we use today. By the time that the ARPAnet was retired in 1990, the network of networks had grown to include over 100,000 connected host computers.
The demise of the ARPAnet was certainly the end of the grand experiment and proved that the concept of a globally distributed, fault-tolerant, standards-based network was indeed a practical concept. It was the first step towards moving towards the commercialized environment that we know today. It was also the last time that politics was incidental to the DNS. Very quickly, politics would completely overshadow what the wizards behind ARPAnet had set out to accomplish.
“What we call 'Progress' is the
exchange of one nuisance for another nuisance.”
- Henry Havelock Ellis
In 1991, DISA awarded a small contract that would change the face of DNS. The contract specified the terms under which a new third party to take over the administration and maintenance of DDN-NIC, which had been up until this point under the management of SRI. A defense contractor, Government Systems, Inc. was awarded the bid in May. By late September, GSI had assumed operational responsibility for DDN-NIC. Although the official record indicates that the contract was fulfilled by GSI internally, GSI actually outsourced it to a small private-sector contractor, Network Solutions Inc. As Rutkowski points out, a number of people have incorrectly concluded that “… NSI was a spin-off because of the similar names and the fact that NSI was performing the entire DISA NIC contraEven Rutkowski himself had earlier been a believer of the misinformation. “It was only relatively recently that I found out that GSI outsourced the entire contract to NSI, and that they were in fact independent companies.” when commenting on the seeming paradox.
Leveraging the experience gained in managing the DDN-NIC operations for DISA, Network Solutions tendered a bid in May of 1992 with the National Science Foundation to provide network information services management to NSFnet and NREN (NASA Research & Education Network). NSI was awarded this contract in October of 1992 under the terms of NSF Cooperative Agreement # NCR-9218742 which, among other things, specified “The Non-military internet registration services to be provided under this agreement will initially include, but not be limited to, the following: Domain name registration, Domain name server registration, Network number assignment, Autonomous system number assignment”.
The import of this development is two-fold. First, the academics that had built the service were now no longer involved. Secondly, the central nervous system of the Internet was squarely in the hands of the private sector. Certainly NSF still exerted a great deal of control over the activities of Network Solutions and made sure that the Cooperative Agreement was executed in a manner consistent with the needs of the network and its community. The seeds of privatization had been sown.1994 was a watershed year in the development of the Internet. First, it was the year that saw the beginning of the popular adoption of Tim Berners-Lee’s World Wide Web with the release of NCSA Mosaic. Second, the National Science Foundation and the United States Government started to remove themselves from the picture allowing commercial interests to start exploiting the network. Suddenly, everyone wanted to get online, surf the net and dive into Gopher-space. The rush towards a connected society had begun.
Until 1995, academic policy on the name-space allowed anyone that had access to a name server to register a domain name with the NSI InterNIC – for free. Needless to say, as the perceived value of being online increased, so did the perceived value of Internet Domain Names. Thus, warehousing and speculation was born. It wasn’t unusual for a speculator to register hundreds, or even thousands of domain names simply based on the potential that someone might want to purchase the domain name from them in the future. After all, the names were free to the first-comer to register, why not grab as many as you could on the off chance you could make a few bucks? In an attempt to mitigate this as well as recover some of the costs of operation, NSF began to allow NSI to start charging $50 per domain name registration this same year. Needless to say, this did not please the general Internet public who were used to the US Government subsidies. The NSF was eventually forced to drop 30% of the $50 fee that had been earmarked by the US Government for general Internet infrastructure projects. The infrastructure fund was deemed an illegal tax because Congress had not approved it. The NSF, as a governmental body had no mandate to levy fees of this nature on the populace. During the short time period that this additional fee was collected, hundreds of thousands of dollars were collected from individuals not under US jurisdiction.
“The Internet is about consensus,
Never mistake truth for consensus.”
– Brian Reid
Network Solutions’ decision move to charge for domain names started a period in DNS history that some refer to as the “Domain Wars”. Battle lines were drawn around the thorny issue of who ultimately controlled the namespace in fact and who should control the namespace. These opposing camps could be roughly characterized as
Unfortunately, it was seldom easy to identify who belonged to which camp most of the time. Many people held multiple allegiances. Each of these players saw an opportunity to leverage control of the name space into something much larger. What that something was varied from group to group based on their agenda. The rallying point for these groups often centered on Network Solutions role as a monopoly within the DNS. Partially answering this question, Jon Postel released the first of his iTLD (International Top-Level Domain) drafts in May of 1996. These drafts were based on prior work of Larry Landweber that had been revised and iterated upon by Randy Bush, Karl Denninger and Brian Carpenter. The iTLD drafts put forth a number of very important concepts that completely define the political structure of DNS today. It also sparked a continuing unresolved debate.
Postel’s goals were very simple. One, his draft outlined a mechanism to allow open competition in domain name registration within the namespace, thus muting the monopoly that NSI had.
Second, it provided a way to give IANA the legal and financial umbrella it needed to survive. Later that month, the board of directors of ISOC (the Internet Society) voted to accept Postel’s draft as a proposal for the management and expansion of the namespace at their annual meeting in Montreal, Canada. While the board recognized that significant work was needed to complete the plan, it was thought that it could be achieved in a matter of months. This meeting would ultimately lead to the creation what would become known as the IAHC, or “Internet Ad Hoc Committee”.
Founded in October of 1996, the IAHC’s stated goal was to “… undertake defining, investigating, and resolving issues resulting from current international debate over a proposal to establish global registries and additional international Top Level Domain names (iTLDs),” according to Don Heath, who was then president and CEO of the Internet Society. The founding board read like a who’s who of the inside track of the Internet, with some interesting new faces as well. The International Telecommunication Union (ITU), the World Intellectual Property Organization (WIPO), and the International Trademark Association (INTA), ISOC, IANA, and the Internet Architecture Board (IAB) all appointed members to the IAHC board. The IAHC quickly became symbolic of the efforts of The Old Guard to change the face of the namespace. IAHC wasted no time and quickly announced to the world that they would quickly be creating seven new top-level domain names - firm, .store, .web, .arts, .rec, .info, and nom. They were also calling for the creation of a competing group of domain registrars.
The IAHC issued a report concerning the administration and management of gTLDs (generic top-level domains). The plan, released to the public on February 4, 1997, expanded on the concepts originally put forth by Postel and wrapped them in a number of compromises designed to satisfy the many interests involved in the process. The trademark community was represented, as were the privacy advocates, standards bodies and Internet and telecommunications carriers. These groups were to be embodied in a group known as the Interim Policy Oversight Committee (IPOC), a bootstrap committee that would later cede control to a permanent Policy Oversight Committee. Further, it also described in detail a new not-for-profit registry model that would be managed by a consortium of international registrars. This consortium was known as CORE. The IPOC/POC and CORE would be self-enacted through a document called the gTLD-MoU.
The gTLD-MoU, or “Generic Top-level Domain Memorandum of Understanding”, was released on February 4, 1997 for public comment to formalize the recommendations made by the IAHC. Some viewed it as simply a more complex and unworkable version of the earlier IAHC, Postel and ISOC efforts. Others still viewed it as a scary step towards a new world government led by the ITU and WIPO. These concerns, and many more, consumed almost all of 1997 in debate. The international flavor of the arrangements was a concern to many. The registry would be run by a Swiss non-profit (CORE), dispute resolution would be managed by a Swiss based, United Nations treaty organization, the World Intellectual Property Organization (WIPO) and administrative activities would be supported by another Swiss based organization, the ITU (International Telecommunications Union).
While IAHC Old Guard was pushing the gTLD-MoU as a done deal the dissident voices were getting louder. One of these voices coalesced into an organization known as eDNS. eDNS was a loosely knit group of individuals that came together to create an ‘alternative root namespace”. Led chiefly by Karl Denninger and Eugene Kashpureff, eDNS attempted to replicate what Network Solutions and IANA had already accomplished with .com, .net and .org. eDNS also set the pace for the Geeks involved in the process.
Their efforts proved to be short-lived. Infighting between the two leaders eventually led to Karl Denninger disassociating himself from eDNS’, which he characterized as “a disgusting joke begotten from what it was envisioned to be.” in his resignation letter.
While Denninger remained active around the fringes of the process, Kashpureff escalated his efforts to dethrone Network Solutions. In July, he altered the DNS for InterNIC.net, which was then Network Solutions primary face on the web, so that all traffic flowed instead to his new effort, AlterNIC, not once but twice. AlterNIC was essentially a protest vehicle against Kashpureff’s view of the NSI monopoly. In a statement to CNET, Kashpureff stated that “The hack was a result of a years' worth of work… I'm proud of what I did." However, "I have some remorse. I understand that what I did was wrong. My ideals, my emotions got the best of me".
Kashpureff ended up leaving the country and fled to Canada where he was eventually jailed for three months pending extradition. Upon his return to the United States, his penalties ended being a $100 fine and probation.
While The Old Guard debated and The Geeks revolted, another incident took place which, had it occurred at a different time, would have been nothing more than a temporary anomaly. On July 17, 1997, human error at Network Solutions corrupted the master zone files for .com, .net and .org throwing the Internet into a state of disarray. While the problem was resolved in roughly 4 hours, the repercussions of the meltdown were felt by the Internet community throughout the rest of that day and into the next. Not only did this event occur the same week that Kashpureff “hijacked” the InterNIC, the story was broken by John Markoff of the New York Times, a prominent writer known for his coverage of and subsequent book about Kevin Mitnick. With the story making headlines in the New York Times and many other major news outlets, everyone quickly realized that the Internet wasn’t as indestructible as they had been led to believe. In fact, many realized that the stability of the Internet rested largely with Network Solutions.
Through this uncertainty, President Clinton directed the Secretary of Commerce to “privatize, increase competition in, and promote international participation in the domain name system” as part of his administrations “Framework for Global Electronic Commerce”. Accordingly the Department of Commerce issued their first request for comments on July 2nd soliciting “… public input on issues relating to the overall framework of the DNS system, the creation of new top-level domains, policies for registrars, and trademark issues.”
This was widely viewed as a very important step. For the first time in the history of the Internet, the government of the United States had proven their capability to be aware of such arcane subjects as DNS. It was also the first indication that the deal The Old Guard was pushing was perhaps “not quite done”.
This confluence of events and uncertainty spurred the debate from which ARIN grew. ARIN, the American Registry for Internet Numbers, is a non-profit organization established for the purpose of administration and registration of Internet Protocol (IP) numbers for North America, South America, the Caribbean and sub-Saharan Africa.
Until 1997, InterNIC/NSI had taken care of these responsibilities, but as Kim Hubbard, past-president of ARIN puts it, “After NSI began charging for DNS registration and the discussion on DNS registration competition began, there was concern voiced among some in the industry that IP registration might somehow be affected.”Others in the business have a decidedly different view. “ARIN was created as a non-profit entity that Network Solutions could more or less spin off because there was just not going to be any money in that part of their business.” commented a source close to the issue that declined to be named for this article. Regardless of the primary motivation, it was quite widely held that the community had to move forward with the ARIN idea. “DNS registration competition discussions at one point became quite hostile and the last thing anyone wanted was IP registration to be pulled into the political morass that DNS had become,” said Hubbard.
“There was concern that while it was plausible to make DNS registration a financially competitive function, the same could not be said for IP registration. For various technical reasons, it was not viable for companies to compete on a monetary basis to allocate IP numbers”. Once the community had recognized the potential problems, ARIN was created quickly. As Hubbard indicates, “… it became evident that the best way to handle the situation was to separate the two registration processes in every way possible”. Through work with NSI, the Internet community and in consultation with the Federal Networking Council, ARIN officially opened for operation on December 22, 1997.
The situation with CORE and the gTLD-MoU was not progressing any smoother at this point. The US House of Representatives held hearings into the state of the DNS that were specifically concerned with the activities arising from the original IAHC plans. Opposition to the gTLD-MoU was at an all-time high as original supporters dropped out. Further, the involvement of the government gave the opposition a chance to derail the entire process that was still being sold as a “done deal” between the various parties and the US Department of Commerce. Success appeared to be at hand. On September 30, 1997 however, the deal start to unravel.
At one of the many House Committee hearings on the subject at the time, opponents of the IAHC/gTLD-MoU plan seemed to gain the upper hand. The Commercial Internet Exchange (CIX), Information Technology Association of America (ITAA), Tony Rutkowski representing World Internetworking Alliance (WIA) and Andy Sernovitz representing the Association for Interactive Media (AIM) all went on the record in some manner opposing the plan. Perhaps most damaging to the gTLD-MoU was Sernovitz’s denunciation of IAHC and IANA as betraying the United States to the governments of Libya and Iraq. While the claims were never completely substantiated or formally investigated, they damaged the credibility of the group behind the gTLD-MoU. Further, the total of all the comments successfully managed to call into focus the potential shift of power that the Internet represented to a country other than the United States.
Even though much damage had been done at the hearings and The Old Guard were now largely on the defensive, the gTLD-MoU continued to press forward. In October, the Internet Council of Registrars, CORE, awarded the technical management contract to run the registry system needed to support the new top-level domains and the shared registry system to Emergent Corporation, a small US consultancy.
On January 30, 1998, Ira Magaziner, who was the senior advisor to President Clinton for policy development, released a discussion paper that later became known as “The Green Paper”. According to Jonathan Weinberg who was working close to the matter at the time, the Green Paper was the result of thinking within the higher levels of the Government that “… the USG thought it could design an institution that would work better.” And, it appeared that Magaziner had the authority of the President to make certain that US rule of the DNS was maintained.
While Magaziner’s Green Paper was very similar to Postel’s original iTLD drafts, they made one very important distinction. The United States Government would remain involved over the short and mid terms to ensure a reasonable and orderly transition a new, non-profit organization, or NewCo. This statement would effectively unravel ISOC’s position as the driver behind the IAHC/gTLD-MoU process. It also spoke out directly against the trademark resolution processes that WIPO had written into the gTLD-MoU. While Magaziner was in favor of trademark protection as part of NewCo’s mandate, he made it very clear that the domain registrars and not NewCo should hold the cost of dispute resolution and all liability. Magaziner also outlined the early demise of the Network Solutions Cooperative Agreement with the US Government. His major points on this subject stated that: ?? “NSI will effectively separate and maintain a clear division between its current registry business and its current registrar business. NSI will continue to operate .com, .net and .org but on a fully shared-registry basis; it will shift operation of .edu to a not-for-profit entity. The registry will treat all registrars on a nondiscriminatory basis and will price registry services according to an agreed upon formula for a period of time.”?? “As part of the transition to a fully shared-registry system, NSI will develop (or license) and implement the technical capability to share the registration of its top-level domains with any registrar so that any registrar can register domain names there in as soon as possible, by a date certain to be agreed upon.”
“NSI will give the U.S. government a copy and documentation of all the data, software, and appropriate licenses to other intellectual property generated under the cooperative agreement, for use by the new corporation for the benefit of the Internet.”?? “NSI will turn over control of the "A" root server and the management of the root server system when instructed to do so by the U.S. government.”?? “NSI will agree to meet the requirements for registries and registrars” as defined by the Green Paper.
Magaziner’s Green Paper specifically indicated that NSI’s monopoly was scheduled to end on September 30 of that year. For the first time, there was a clear indication from the highest levels that the government endowed monopoly that NSI enjoyed was finite. The IAHC/gTLD-MoU detractors suddenly had a unified proposal to rally around, The Old Guard were left with a plan in shambles, Network Solutions was faced with a severe limitation of power and profits and Jon Postel was not happy with the new direction.
In response to the Green Paper, Postel issued a statement that note that ''I am in agreement with the main theme of the proposal... I am less comfortable with the details of the proposal on how new generic top-level domains, registrars and registries would be established, and the restriction to only five new gTLDs.''
On the weekend preceding February 4th, Jon Postel undertook what he characterized as a “transition plan test”. During this test, he had the root DNS system reconfigured to obtain DNS information not from the “A” root server operated by Network Solutions, but rather by one that he operated at ISI. In a written statement by Postel at the time he stated “I wanted to see how easily management of the root servers could be passed to another machine when the government gives up its control of the domain system as described in the Green Paper.”
The US Government did not react well to this test. According to a report published in Network World at the time, Becky Burr, a senior official with the Department of Commerce, said the government knew nothing of the test beforehand. ''The timing is unfortunate,'' she said, referring to the release of the controversial domain plan.
Although control of the DNS was quickly handed back to Network Solutions, and therefore the US Government, Postel had made it very clear that he was unhappy with the statements made in the Green Paper and that he was still very much in charge of the DNS, regardless of who had contractual control. On February 17, unknown individuals broke into Best Communications (now owned by Verio) and stole the registry servers that Emergent was installing for CORE. While this event was most likely the result of unfortunate timing, many at the time attributed the theft to a conspiracy backed by Network Solutions to discredit CORE and IAHC. Others seemed to think that this event was nothing more than an insurance fraud designed to underwrite the mounting costs faced by CORE.
To this day, it has not been established who was responsible for the break-in or what happened to the equipment, but it was clear that CORE now had some serious obstacles to overcome.
On June 5th, Magaziner released a revised version of the Green Paper that took into account the extensive public commentary that had been collected by the Government since the release of the original draft. This new document referred to as “The White Paper” was released as an official statement of policy on behalf of the Department of Commerce. Most relevant was Magaziner’s call to establish consensus on the issues presented in the White Paper by the relevant stakeholders. Essentially, he was granting the Internet one last chance to determine what their fate under the White Paper would look like.
Following the release of this document, a number of groups scurried to organize and forge towards consensus. At the time, Wired magazine’s online counterpart reported that “… the Clinton administration's new policy on Internet domain-name administration deferred most of the tough decisions about the system's shape and who would run it. Now, only two weeks after the plan's release, a host of companies, interest groups, and individuals are dashing into the decision-making vacuum. The rush is evident in a flurry of clashing announcements over the past 10 days that a variety of Internet "stakeholders" will hold conferences to address questions about the domain system and Internet governance.”
The most important of these emerging groups was the International Forum for the White Paper or, IFWP. The IFWP genesis can be traced back to the announcement of a slightly earlier group, the Global Incorporation Alliance Workshop (GIAW) that had come out of nowhere and announced a conference to be held in Washington on July 1stand 2nd. The prevailing sentiment quickly emerged that the GIAW was nothing more than a Network Solutions front to address the issues presented by the White Paper in a manner amenable to NSI shareholders. As Rick Wesson of Alice’s Registry Tools noted at the time on an IAHC mailing list, “It would seem NSI and all the folks that lay claim to the goldmine of TLDs are setting up a meeting… the scary part is it looks like only those folks that oppose the gTLD-MoU are coming”. Minutes from an organizers’conference call show that there was agreement on a need to “diffuse some of the negative associations with the GIAW”. Thus, the IFWP was born.
The IFWP described themselves as “an ad hoc coalition of professional, trade and educational associations representing a diversity of Internet stakeholder groups, including ISPs, content developers, trademark holders, networkers, intergovernmental groups, policy experts, and-users and others. This coalition has come together to sponsor a framework of coordinated international meetings, to be held around the world, called the International Forum on the White Paper, at which stakeholders will discuss the transition to private sector management of the technical administration of Internet names and numbers as outlined in the "White Paper" recently released by the United States Government. These international meetings are open to all Internet stakeholders, who are encouraged to support this on-going process.”
The IFWP quickly gained support for a few very important reasons. First, it was quickly gaining momentum at a time when the IAHC/gTLD-MoU/CORE process was losing steam. Second, each group that had felt left out of the IAHC process was specifically embraced by the IFWP. Lastly, Network Solutions’backed the IFWP lending it credibility where the IAHC lacked.
The IFWP sponsored a number of regional workshops held throughout the world in an attempt to address the issues raised by the White Paper and define a specific course of action that could fulfill the terms put forth by the Government. While The IFWP, it appears, did not produce a full working draft of bylaws for NewCo as requested by the White Paper, it succeeded by becoming a catalyst for the process the White Paper contemplated. Through July and August, Jon Postel wrote a new draft set of bylaws for a “new IANA” that would satisfy the role set forth by the White Paper. Postel positioned the new IANA as “… having responsibilities in three interrelated areas: Internet Protocol addresses, domain names, and protocol parameters. This will include the root server system and the work carried out currently by the existing IANA.” The new IANA's goal was to "preserve the central coordinating functions of the global Internet for the public good”. Postel released these drafts throughout June, July and August. The most important was released on September 17 with the benefit of the endorsement of Gabe Battista on behalf of Network Solutions.
This iteration was characterized as “the best elements of earlier drafts and include broad inputs from Internet stakeholders and users while remaining true to the guiding principles set forth in the US Government's White Paper”. The goal of these new drafts were to “… capture the best ideas from all sources, including the International Forum for the White Paper (IFWP), the business community, the Internet technical community and other stakeholders.” This draft is known the community as IANA/NSI Draft 4. Draft 5 followed a few weeks later on September 28, curiously, without the explicit support of Network Solutions.
Other groups, finding the NSI/IANA drafts lacking, engaged in a similar effort in an attempt to define NewCo. Most notably, The Boston Working Group was concerned that the NSI/IANA drafts lacked a clear set of checks and balances to ensure democracy within the new organization. Further, they posited, “… the IANA/NSI proposal is neither a product of the IFWP process nor does it conform to the IFWP consensus points. Nor does it meet the standards required by the NTIA White Paper, either in terms of content or the process through which that proposal was derived.” The Boston Working Group derived their name from the fact that their drafting efforts took place at an ad hoc working group meeting held on September 19th and 20thOn October 1, 1997, the NTIA announced that NewCo (or the new IANA) would be called the Internet Corporation for Assigned Names and Numbers, or ICANN. This same day, the Cooperative Agreement between the United States Government and Network Solutions had been scheduled to terminate and the transition to ICANN would Jon Postel was now mainly concerned with ensuring that the transition to ICANN would occur on terms that were agreeable and fair to everyone involved. On October 7, Joe Sims, Postel’s lawyer, appeared before the United States House of Representatives Subcommittee on Basic Research and The Subcommittee on Technology of the Committee on Sciences on Jon’s behalf. Postel, having recently taken ill, was unable to testify in person. Postel’s testimony included a simple statement describing his current feelings. “Most of the work to come will be done by others; IANA will continue its technical work and I will of course stay involved in the process, but it is time for ICANN to begin to lead this effort”. His words, although simple, foreshadowed far more than anyone could imagine.
On October 16, 1998 Jon Postel passed away. With Jon no longer involved, the processed wavered somewhat. However, having laid most of the groundwork with the flurry of drafts produced earlier that year, others were able to pick up where he left off. Through the remainder of October and most of November, Esther Dyson, Joe Sims, Mike Roberts and others worked towards satisfying the comments issued by the NTIA on the IANA drafts. On November 25, the United States Department of Commerce announced that they had finalized negotiations with NewCo and officially recognized it as the Internet Corporation for Assigned Names and Numbers for the purpose of transitioning DNS management from the US Government to industry.
Gabe Battista resigned as CEO of Network Solutions mid-November and Ira Magaziner left at the end of December. It appeared that there were very few people left standing outside of the new ICANN. Although ICANN had made it through the Domain Wars and was deemed worthy enough to assume the mantle from the Department of Commerce, the organization still had some significant challenges ahead of it. Now they were actually faced with overseeing the DNS, bringing competition to the namespace and adding new gTLDs to the root in an open, transparent and bottom-up manner. With an appointed interim Board of Directors in place, ICANN tackled the thorny issue of competition first. ICANN chose to pursue implementation of a Shared Registry Service with Verisign that would see Network Solutions split off into two entities, the registry and the registrar, while new competitive registrars would be accredited. The threat originally raised by Magaziner had come to pass. Jim Rutt, the new CEO of Network Solutions, drew up his battle plans. On October 7, 1998, Network Solutions entered into a revised Cooperative Agreement with the Department of Commerce. The Cooperative Agreement had granted Network Solutions their monopoly and was regularly amended by various governmental agencies and Network Solutions to address new operating realities. Most recently, Amendment 11 had specified that Network Solutions must work with “NewCo” through the transition specified by the DOC and enter into a contract with them to provide the DNS services that they had originally provided to the US Government. Rutt’s plan of attack was very simple. Amendment 11 was signed on October 7, prior to ICANN being named as “NewCo/New IANA”.
As such if NSI refused to recognize ICANN as being the NewCo described in the Cooperative Agreement, ICANN would have no one with whom to enter into an agreement. This put ICANN into a tough spot but they pushed forward with their plans to introduce competition. Network Solutions’tactics delayed this effort significantly, as the only way that ICANN could get NSI to do anything was to first file the request with the Department of Commerce that would then relay it to NSI. Despite the odds being against them, ICANN announced on April 25, 1999 that they had selected 34 companies that would be accredited to compete with Network Solutions for the registration of domain names. Five of these companies would be allowed to participate in a special test-bed which had been designed to allow a limited number of companies to work out the technical issues associated with the new Shared Registry System that NSI was implementing. On June 7, register.com Inc. announced that they had successfully registered the first domain name under the new competitive regime. The test-bed, originally scheduled to last until June 24, was extended until September 10, and then November 30.
NSI continued to refuse to recognize ICANN through the summer of 1999. The tactics worked reasonably well until the situation came under the scrutiny of a House Commerce Committee investigation into ICANN. The panel, chaired by Tom Bliley, grilled Rutt.
One of the most widely reported exchanges occurred between Jim Rutt and Bart Stupak, a House Representative from Michigan.
Stupak: NSI claims that it only has to recognize ICANN if ICANN has a “final agreement.” DoC says the agreement has been finalized. Sounds like a delay tactic to me. What do you think? Have you ever told ICANN or DoC that there is no final agreement?
Rutt: Let me ask my lawyer and get back to you tomorrow. Yes, I have said there is no final agreement.
The press jumped on the story as hard as the committee had jumped on Rutt. As ABCNews.com reported, “Rutt told the committee that although his company controls about 75 percent of the names on the World Wide Web and the Internet, it does not have a monopoly — which drew snickers from the standing-room-only crowd.
Democrats on the committee were even more skeptical of NSI’s claims that ICANN was out to destroy its business. “It seems to me NSI questions the very basis of ICANN’s authority,” said Rep. Bart Stupak, a Michigan Democrat. “This sounds to me like a classic delay tactic.” Network Solutions stalling tactics were now out in the open. The Commerce Committee did not take it lightly. Andy Pincus, general counsel for the Commerce Department, summed it up best at the hearings, “If we hit a stone wall, we’ve got to do it another way.” Industry insiders widely regard the July hearings as Rutt’s Waterloo. Nonetheless, Network Solutions still maintained enough leverage with ICANN and the Department of Commerce to push the issue closer to the concessions that NSI wanted.
Between November 2nd and the 4th, 1999, ICANN’s first annual general meeting was held in Los Angeles, California at the Sheraton Gateway Hotel. The agenda was specifically geared towards ratifying a proposed agreement between ICANN and Network Solutions. Everyone agreed a truce was necessary, but few felt it could be pulled off. While ICANN kept a firm grip on the proceedings, there was a new sense of empowerment amongst certain groups, a feeling that anything could be accomplished given the right effort. There was an unspoken understanding that this agreement would make or break ICANN. If the parties did not successfully arrive at a conclusion on this issue, it was almost certain that the structure would disintegrate.
The original agreements tabled provided Network Solutions with significant concessions. Through a number of informal meetings held by a number of interests through the week, various positions were readied for presentation during the November 3rdPublic Comment forum. The comment forum was especially raucous. People were lining up for hours to present their views. In some cases, such as with the Registrars group, dozens of proposed revisions to the agreement were put forward to the ICANN Board. Somehow, the board of directors and ICANN staff managed to reconcile most of these presentations and to negotiate a revised agreement with Network Solutions through the night.
On November 4, ICANN and Network Solutions agreed to a truce. Among other things, the agreements specifically provided that Network Solutions would have to separate their registry and registrar businesses, that they would receive an extension to their operating agreement if they divested one or the other business in two years time and most importantly, that they recognized ICANN as NewCo. As expected, a few weeks later, the Department of Commerce also accepted these revised agreements.
The ensuing year went relatively quietly. The introduction of new registrars precipitated an average price drop from $35 per year to roughly $15. Registration rates rose rapidly. ICANN occupied itself with the introduction of new generic top-level domains. Although the introduction process took quite some time, the ground covered was well trod by the previous debates. On the 16th of November 2000, the ICANN Board of Directors finally approved the introduction of seven new top-level domains, .aero, .biz, .coop, .info, .museum, .name, and .pro.
While this process is not yet completed, it is expected that the general public will be able to register these domain names sometime during the last half of 2001.
ICANN’s work is not yet done, nor have the dynamics of DNS become any less complex. The industry is still struggling with internationalizing the namespace, the impact of private root systems and a myriad of other issues. ICANN itself is also still the center of a maelstrom of controversy, but, for better or worse, work is being done and progress is being made.
It’s dry and it’s factual. But it’s DNS, and the story needs to be told… ”- Tim DentonAll the material for this article was gathered through hours of research on the Internet, including web sites, mailing list archives and the venerable IETF RFC server. While every attempt has been made to verify that the actual events occurred as documented, incomplete transcripts, poor memories and non-existent web archives made this a difficult task.
As Anthony Rutkowski says on www.domainhandbook.com, “a lot of this stuff is like reading chicken bones”. If you feel that an important event was missed or unfairly portrayed in this article, please drop Ross Rader (email@example.com) a line with the corrections for inclusion in future versions of this essay.
Thanks go out to everyone who took time out of their busy days to assist in the creation of this piece, including Anthony Rutkowski, David Mills, Tim Denton, Richard Sexton, Jonathan Weinberg, Antony Van Couvering and many others. Special thanks go out to the countless thousands that built the system and implemented the policy that made it worthwhile to write this article in the first place.
The Internet protocol architecture was originally developed under DARPA (Defense Advanced Research Projects Agency) sponsorship to meet both military and civilian communication requirements, but given that US defence budgets played a major role and there was little commercial interest, the .MIL, .EDU, and .GOV have become de facto restricted to the US - other countries adding Country Codes (cc) as in .gov.ca, or using different solutions as in .ac.uk "academic United Kingdom" replacing .edu - although in earlier days, .EDU didn't require that the institution had to be US accredited (as it does now), so there were/still are a few .EDU domains outside the US.
1967: ARPAnet NIC (Advanced Research Projects Agency Network, Network Information Center) created at Stanford Research Institute (SRI) by Doug Engelbart; the network was small, users knew how to get around. Note: ARPA and DARPA were practically synonymous in the early days of the internet
1971: Host mnemonics invented by Peggy Karp (RFC 226)
1974: V. Cerfand and R. Kahn, "A Protocol for Packet Network Intercommunication", IEEE Transactions on Communication, led to the "DDN Protocol Handbook", NIC-50004, NIC-50005, NIC-50006, (three volumes) and "ARPANET Information Brochure", NIC-50003, both by SRI International in December 1985 which formalized a parallel civilian/military approach.
1981: over four hundred (Wow!) names and nicknames in the combined ARPANET-DCNET tables; so expansion was proposed by COMSAT's Dr David Mills to ARPA (ARPANET), COMSAT (DCNET), DCA (EDNET, WBNET), UCL (UCLNET, RSRENET, SRCNET), MIT (CHAOSNET), INTELPOST (INTELPOSTNET) (RFC799)
1982-84: Jon Postel, from Information Sciences Institute at the University of Southern California, and Zaw-Sing Su from Stanford Research Institute, developed the basis of what we know today (RFC822, 823) - Domain Name Service (DNS) as a proposal to deal with the increasing size of hosts table, to prevent the necessity of routing-map distributions and periodically downloaded hosts databases for the world, by the world.
1984: Jon Postel and Joyce Reynolds first proposed .MIL, but as there were no "country codes" it can be assumed that there was no intended monopoly for the USA (RFC920)
1987: proposal for ARPAnet to be expanded to EDU, MIL, and ARPA (RFC1034) - and by RFC1035 DNS was fully acceptable
1989: Tim Berners-Lee "invented" the World Wide Web with a line-mode user interface (named the "WWW" at CERN, Conseil Européen pour la Recherche Nucléaire)completed in late 1989.
1990: The Defense Communications Agency (DCA, now the Defense Information Systems Agency or DISA) split the ARPAnet into the ARPAnet and MILnet; soon after ARPAnet retired, with over 100,000 hosts on the network
1991: DISA awarded the administration and maintenance of DDN-NIC, which had been up until this point under the management of SRI to Government Systems, Inc. who subcontracted it to the small private-sector Network Solutions Inc. Tim Berners-Lee's World Wide Web was used on a minor network in March 1991. May 1991 was the first time that the information-sharing system using HTML, HTTP, and a client software program (www) was fully operational on the multiplatform computer network at the CERN laboratories in Switzerland.
1993: MILnet became integrated into the Defense Data Network (DDN)
1993: Marc Andreesen, National Center for Supercomputing Applications (NCSA) at Champaign-Urbana released Mosaic (pre-beta in March) - and in November (1st full release) the commercial explosion started. Gopher, which grew parallel to the web, fast became moribund.
1994: "top-level domain names" (TLDs) were the generic TLDs (EDU, COM, NET, ORG, GOV, MIL, and INT), and the two letter country codes from ISO-3166. It was considered extremely unlikely that any other TLDs would be created.
1995: Beginnings of the commercial over-exploitation of the namespace, e.g. the registration by Proctor & Gamble of ~200 domains having to do with their products and the symptoms thereoof (e.g. diarrhea.com), all contributing to the profitability of Network Solutions.
1996: proposal to introduce firm, .store, .web, .arts, .rec, .info, and nom. Start of domain name wars, privatization of the management etc. One immediately apparent problem the tension between trademark owners/domain owners/registrars and the domain name dispute resolution process.
1998: beginnings of marginal use of some country codes (.TO, .WS, etc), and the commercial abuse of others - e.g. .TV figured out that ccTLDs (Country Code Top Level Domains) could be a substantial source of revenue and began marketing them to entities with no connection to those countries - the 2-letter ones are still reserved (supposedly) for independently discriminatable geographical entities.
1999: .TEST .EXAMPLE .INVALID .LOCALHOST were "reserved". .CAN./LAN./SAN./WAN. and LOCAL used in intra/extra nets, and are occasionally seen publicly indicating a company name or LAN-use name on a promiscuous relay. LOCAL, USENET, BITNET, UUCP, and a couple others are commonly used as "tokens" for TLDs
2000: four new TLDs (.biz, .info, .name, and .pro) "unsponsored" i.e. market supply/demand, and three new TLDs (.aero, .coop, and .museum) "sponsored" or managed by narrow professional/business interests.
Recent: The Open Root-Server Confederation (ORSC) now makes a further 800 or so TLDs available - see http://dns.vrx.net/tech/rootzone/db.root - .CINEMA, .TEENS, .XXX, etc [more or less] ad infinitum...
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes. If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner.
ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least
Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.
Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: February 19, 2014