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

Our Mission
ICANN for Beginners
About Us
How To Use This Site
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
    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.
    Maybe .pro Should Wildcard
    by jberryhill on Tuesday October 07 2003, @08:40PM (#12413)
    User #3013 Info

    Of course, if it wasn't for the wildcard in .museum, you'd never find any museums, since the naming convention is counter-intuitive.

    For example, if you want to find broadband internet services, you go to:


    If you want to find the National Heritage Agency of the Isle of Man, you go to:


    And, how many times have you been looking for a frog museum in your country? It would be a long time before you stumbled across:


    But hurry. In order to qualify for a .museum domain name, the museum must be open to the public, and the swiss.frog.museum is only open for three hours every month.

    [ Reply to This | Parent ]
    • Why Not? by Anonymous Wednesday October 08 2003, @06:03AM
    What's with the sarcasm?
    by Anonymous on Tuesday October 07 2003, @09:49PM (#12414)
    No really. The poster of this article is cynical and sarcastic. However, the .museum makes excellent points. Essentially, the .museum domain owners support the wildcard behavoir, they've never hidden the fact that they have a wildcard, and no one has ever complained. In other words, there is no problem.

    I hope the outcome of this wildcard discussion is something along the lines of, "If you want to impliment a wildcard in your TLD, these are the rules you should follow." Then, .museum, and the other wildcard domains will follow these guidelines, and things will be great.

    (of course, i think there are many domains that wildcards are inappropriate for, but that's another story...)
    [ Reply to This | Parent ]
    by RFassett on Wednesday October 08 2003, @06:13AM (#12419)
    User #3226 Info | http://www.enum.info
    the market place dictates that .com domain name registrations are a commodity. For those DNS business models this is of benefit to, there is no problem until threatened. Same would be true for .Museum except for the fact the market place does not dictate second level registrations as a commodity, by its own design. It seems ok to capitalize upon the commodity value of .com as long as you are not "the provider". Technical issues aside, I am not sure I get this logic.
    [ Reply to This | Parent ]
    Hypocracy In Action
    by Anonymous on Wednesday October 08 2003, @07:23AM (#12420)
    This outlash against VeriSign is full of inconsistencies.

    The Internet is more than the web.

    Wildcarding does not factor in other protocols.


    It is ok if .museum or .tv use a wildcard to target web browsers.

    [ 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