ICANNWatch
 
  Inside ICANNWatch  
Submit Story
Home
Lost Password
Preferences
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
ICANNWatch FAQ
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)


     
    This discussion has been archived. No new comments can be posted.
    Security and Stability Advisory Committee Recommendations | Log in/Create an Account | Top | 1 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Threshold:
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
    We can "route around" Verisign
    by odonnell (michael_odonnell@acm.org) on Wednesday September 24 2003, @12:14PM (#12295)
    User #3447 Info | http://people.cs.uchicago.edu/~odonnell/

    The DNS root zone, as supported by Verisign, bundles together two different services:

    1. Handle service: a handle is a token (not necessarily humanly readable or mnemonic) that can be owned by a user and reassigned to different IP numbers as that user migrates around the network;

    2. Name service: a name is a humanly meaningful token that resolves to an IP address.

    DNS is currently the only handle service, which gives Verisign a sort of monopoly power. There are many different name services, including DNS, Yahoo, Google, which could compete more evenly if none of them were bundled with the only handle service.

    We could deploy a handle service with almost no administrative burden, using current DNS software, at a lower level of the DNS hierarchy (perhaps a 3d level domain), providing meaningless numerical handles freely to all. Bob Frankston has described this idea in his dotDNS proposal: http://www.circleid.com/article/225_0_1_0_C. It only requires a stable institutional sponsor with a highly defensible domain name (e.g. nicesponsor.org), the technical oomph to run a name server at traffic levels similar to the alternate root servers, and the willingness to provide silly looking subdomains (e.g. 188828281282232.dns.nicesponsor.org) to all who request them.

    If a handle service under dns.nicesponsor.org proves useful, it can migrate up to a higher level in DNS, and future software deployment can eventually treat it as a new root. Users can assign their own handles using public-key signatures and secure hashing, depending on the sponsor only for dissemination and not for authorization. In the meantime, dotDNS does not interfere at all with the current DNS. Nobody has to abandon her use of DNS while exploiting the alternative value of dotDNS.

    It's time to just do this.

    [ Reply to This | Parent ]


    Search ICANNWatch.org:


    Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
    You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com