(DNS), which plays a key role in routing the large majority of Internet traffic, was designed at a time when there were few hosts and the pre-Internet network was limited mostly to academic users, researchers, and noncommercial traffic. The idea of giving internetworked computers easily remembered names dates back at least to 1971 when Peggy Karp, an early author and editor of the network engineers’ Requests For Comments, prepared the first hosts.txt file, the predecessor of the modern “root” file. Each version of the DNS since then has sought to provide routing efficiency, ease of use, and the ability to scale, although it’s unlikely many of the founders foresaw quite how much it would need to scale. Today, with a substantial part of the name-resolution infrastructure still provided on a volunteer basis (and the name assignment function increasingly regulated and commercialized), the DNS continues to meet its objectives of providing mnemonicto-IP mappings while preventing name collisions on the Internet. It thus undergirds part of the network’s fundamental technical stability. Technical success, however, has bred social issues. In the mid-1990s, the DNS and the people admin-
[1]
A. Michael Froomkin,et al.
Wrong Turn in Cyberspace: Using Icann to Route Around the APA and the Constitution
,
2000
.
[2]
Sofie Juel,et al.
The Uniform Domain Name Dispute Resolution Policy
,
2000
.
[3]
Jon Postel,et al.
Domain requirements
,
1984,
Request for Comments.
[4]
Jon Postel,et al.
Domain Name System Structure and Delegation
,
1994,
RFC.
[5]
Milton L. Mueller.
Rough Justice: A Statistical Assessment of ICANN's Uniform Dispute Resolution Policy
,
2001,
Inf. Soc..
[6]
A. Michael Froomkin.
Semi-Private International Rulemaking: Lessons Learned from the WIPO Domain Name Process
,
2000
.