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.
    ICANN Makes Nice to ccTLDs (Again) | Log in/Create an Account | Top | 5 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.
    .COM and .NET and the Coming Front-End Services
    by Anonymous on Tuesday July 13 2004, @06:32AM (#13936)
    Vinton Cerf is telling everyone that 4-letter TLDs
    (like .INFO) do not work. You might as well forget
    all TLDs with more than 3-letters.

    Paul Twinkie is telling everyone that .BIZ is a
    failure. He is of course working his GAC Community
    to promote 2-letter TLDs. The 2-letter TLDs are
    mostly picked over with only a few (.TV .AM .FM)
    achieving any wide-spread usage. .ORG is a lost cause with operational problems
    and no support from any serious telecommunication
    companies. Not even the RIRs (ARIN, RIPE and
    APNIC) use the .ORG TLD. They use .NET, even
    though they claim to be non-profit.

    That pretty much leaves .COM and .NET. People
    might as well get used to the fact that it is a
    two-TLD world. From a banking point of view, this
    is like viewing the world as Visa and Mastercard.
    The rest of the business is not interesting.

    Starting with .COM and .NET one can start to
    rebuild using Front-End Services. Just as PayPal
    created their own "currency" (and brand) as a
    Front-End to Visa and Mastercard, companies can
    now rely on .COM and .NET to be the foundation
    for a variety of Front-End Services.

    The Registrars really do not like .COM and .NET
    because they do not profit from those. There is
    no money fighting for 20 cent mark-ups on a
    $6 per year regulated product. The Registrars
    make their real money by preying on consumers
    who forget to renew registrations. They charge
    hourly fees to *help* the consumer get back
    online. Since many of the .ORG owners are not
    net-savy, they are more desirable to the
    Registrars who now work the drop-queues and
    warehouse names hoping to redirect e-mails to
    their servers where they can review them and
    find out if the domain has any value. The e-mails
    can of course be returned or forwarded for a fee.

    The .COM and .NET owners are more net-savy and
    do not allow their names to fall into Registrar's
    hands. The 10-year registrations allow them to
    pay $60 and not worry for a long time. The .COM
    and .NET owners could easily deal directly with
    the Registry or have their Reseller (Web-Host/ISP)
    company handle the transaction. That is exactly
    what existed PRIOR to the ICANN-regime of DNS
    regulation. There is no need for ICANN to be
    involved in .COM and .NET. No one cares what
    ICANN does with the 2-letter TLDs. All of the
    focus is now on .COM and .NET.

    Verisign and Microsoft of course have studied
    this and done their market research and see that
    Front-End Services will be the next wave. Since
    some of those Front-End Services benefit from
    more rapid updates of the DNS TLD servers it
    should be no surprise that Verisign would be
    enhancing .COM and .NET TLD servers to handle
    that trend.

    Just as Windows overlayed DOS as a Front-End
    Extension, the new Front-End Services will
    assume only .COM and .NET and will be an overlay
    which will give consumers the illusion of a
    system that ICANN (IANA) does not want them
    to see. Fortunately, with the backing of
    Verisign and Microsoft, via .COM and .NET,
    the world can move forward and ignore ICANN
    and their small closed "community".
    [ Reply to This | Parent ]
    Re:.COM and .NET and the Coming Front-End Services
    by Anonymous on Tuesday July 13 2004, @09:14AM (#13937)
    http://australianit.news.com.au/articles/0,7204,10 120033%5E15306%5E%5Enbv%5E,00.html

      "However, after the last round of seven new domain names, including .name, .biz and .info, were released to a less than thriving post-dotcom market in 2001, there is is unlikely to be widespread support for ICANN to spend its time and money on a follow-up."

    "I doubt that the operators of .biz and .info would consider them very successful," Mr Twomey conceded.
    [ 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