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.
    ICANN Publishes Proposed Agreement on .MOBI | Log in/Create an Account | Top | 7 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 it'll work.....
    by AmericaAtLarge on Thursday June 09 2005, @09:59PM (#15514)
    User #4126 Info | http://americeatlarge.org/
    But let me get it straight, mobile users won't mind typing in a domain name, but the extra 2 characters of the TLD is a little much. Ok, over many times it can become laborious, so why not just make the mobile devices default to .m? On another note, the reverse resolution seems to be alot like what new.net was doing all along doesn't it?

    I was staunchly against the introduction of new TLDs, mainly because there are just so many problems that need to be ironed out with DNS / registrars / registries / etc. However, if ICANN is to facilitate the working Internet, they also have to progress. So, in this I am torn.

    But, for mobile users, the existing platform doesn't work well. So, this opens up a whole industry if they do it right, or get laughed off the blog if they flop.

    Randy Glass
    [ Reply to This | Parent ]
    Re:Maybe it'll work.....
    by Anonymous on Friday June 10 2005, @03:29AM (#15515)
    Microsoft can make anything work and they have
    the software control point to do that.

    New.NET does not do Reverse DNS. New.Net mostly
    took the plug-in route and added to the root
    zone TLDs with market appeal. New.Net is not
    counting the WRT-54G and WRT-54GS users who are
    programming their $50 Cisco WIFI Routers from Radio
    Shack to enhance the DNS.

    ICANN creates instability via policies that
    encourage stagnation. The non-lawyer world is
    routing around ICANN.

    [ Reply to This | Parent ]
    "staunchly against the introduction of new TLDs" ?
    by Anonymous on Friday June 10 2005, @05:04AM (#15518)
    "staunchly against the introduction of new TLDs" ?

    In the consumer's minds, where the .NET really
    exists, there is only one TLD which is .COM.

    People working in "the industry" have a view that .NET is important (to them) and they protect that.

    If several thousand TLDs had been launched at the
    same time, consumers would have migrated away from .COM, to a much more diverse and fun Internet.
    Instead, they have walked away. Maybe that is
    good, because they have now found LOCAL WIFI and
    WIFI Max solutions and they will come back
    together (maybe) and people will see a much more
    diverse .NET

    The rest of the ISOC, IAHC, ICANN churn is just
    a charade and consumers largely ignore it. The
    lawyers create it and make a lot of money from
    the churn. They call it governance.
    [ 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