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.
    VeriSign embarks on a Multilingual Strategy | Log in/Create an Account | Top | 15 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.
    Re: VeriSign embarks on a Multilingual Strategy
    by fnord (groy2kNO@SPAMyahoo.com) on Thursday June 13 2002, @10:01AM (#7158)
    User #2810 Info
    Similar, to the extent that they are combined client-server solutions, but not identical. And Veri$ign has been running its mltbd.net multilingual testbed for quite some time. Veri$ign also doesn't appear to be going (at this time) for the other ways that new.net names can be resolved, via a client DNS reset or via the use of participating ISPs. I also haven't seen mention of whether the plugin will auto-update as the new.net one does. If not, it will be a bureaucratic nightmare, if so, it gives Veri$ign the opportunity to put foistware, spyware, or other drek on your system, and given Veri$ign's track record I can see them trying just that.

    Bottom line is, Veri$ign pre-sold a bunch of multilingual domains, they were near useless, so the pressure was on for them to either be accepted by ICANN, IETF, et al, which they weren't, or to come up with another solution. This is their other solution. As many of the pre-reg names were registered by speculators and cybersquatters, this may get interesting. Can AOL file a UDRP claim against, for example: aol.mltbd.net? I don't think so.

    I also think new.net really missed an opportunity here, they promised to have some functioning non-roman TLDs almost from their inception but haven't managed any to date, though I remain unclear from the reports to date whether Veri$ign's IDN will be IDN.IDN or eg: IDN.com (which was their testbed model). IF they stick with the latter, new.net or someone else could still have an opportunity. -g

    [ Reply to This | Parent ]
    Re: VeriSign embarks on a Multilingual Strategy by fnord
    Re: VeriSign embarks on a Multilingual Strategy
    by Anonymous on Thursday June 13 2002, @10:09AM (#7160)
    IDN.IDN's that are not supported in the ICANN root will create massive confusion for everyone. Verisign will not dare go down this path. I hope that new.net doesn't either. It needs to be done in a controlled fashion otherwise we all lose. If anyone thinks they can deploy IDN.IDN and steal money from end-users and stay in business....they are wrong. There will be support nightmares when the names don't work and nobody will renew or buy a multilingual domain name again
    [ 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