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.
    .museum's Awfully Defensive Statement on Its Wildcard | Log in/Create an Account | Top | 18 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.
    Who has the authority to bind a domain name?
    by odonnell (michael_odonnell@acm.org) on Wednesday October 08 2003, @09:57AM (#12423)
    User #3447 Info | http://people.cs.uchicago.edu/~odonnell/

    Wildcards themselves are a technical device. The wildcard concept is a red herring in the discussion of Verisign's, MuseDoma's and others' insertion of wildcards into their tables. Whatever the actual reason

    why the IAB was too honest to say "Wildcards bad, end of story"
    the correct reason is that wildcards are not inherently bad, and no statement about wildcards is in fact the end of the story.

    The key question behind Verisign's and MuseDoma's actions is, "who has the authority to bind each domain name?" The operator of a DNS zone performs its duties for a particular constituency, which varies from zone to zone. Authority for general policies comes from the constituency, and entails particular authorities over particular domain names. An operator is responsible for respecting the authority of its constituency, and for encouraging healthy technical practices.

    In the case of the root zone, .com and .net, the constituency is essentially all of humanity. ICANN is the least problematic organized representative of humanity for this purpose. Verisign holds a contract (and apparently a very lucrative one with high profit margins) from ICANN to perform a large part of the .com and .net operations. Within these subdomains, it is widely accepted that control of a particular name is valuable, and must be awarded to particular applicants based on a combination of temporal priority, willingness to pay, and rights to trade names and marks connected naturally to the domain name. Verisign bound a huge number of these domain names without approval from its constituency, nor from ICANN as a representative of its constituency. Furthermore, it appropriated to itself a commodity with a high market value which it does not own, but holds as contractual steward for ICANN and humanity.

    It appears that the constituency for .museum may be well represented by MuseDoma, which may have acted totally responsibly to the authority of the constituency. If so, there is no objection to their use of a wildcard entry based on authority.

    It also appears that MuseDoma crafted its wildcard entry entirely to support a particular sort of Web browsing. If so, they are probably guilty of an engineering error. Healthy technical practice dictates that DNS responses must serve all possible applications at the IP level, and not just higher-level protocols, such as HTTP. In a very small subdomain, created solely for the exercise of HTTP, it is OK to ignore other uses. It is unlikely that .museum is small enough to qualify for this exception. But, based on the information before us, MuseDoma has probably made a modest and correctible technical error, and has not exceeded its authority.

    Of course, the technical objection applies very strongly to .com and .net, since addresses in those domains may be used for anything. As a really good steward, Verisign would have resisted popular pressure to add the sort of wildcard that it did, and explained to its constituency why every table entry must support all possible IP uses, and not only a subset of higher-level protocols---not even the subset consisting of all protocols in use today. To have instituted a technically unhealthy step (and it would be unhealthy even if the immediate consequences were all positive, because it constrains future innovation) against the wishes of its constituency is a serious ethical, and apparently contractual, offence by Verisign.

    Mike O'Donnell
    [ Reply to This | Parent ]
    Who has the authority to bind a domain name? by odonnell


    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