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 Announces Internationalized Domain Names to be Added to TLD Zones | Log in/Create an Account | Top | 12 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 Announces Internationalized Domain Na
    by fnord (groy2kNO@SPAMyahoo.com) on Monday October 01 2001, @06:47PM (#2669)
    User #2810 Info
    No. You say email and ftp won't work, you also say they will. Does XTNS do email? They were promising a month ago that they were working on it. How does that jibe with what you say here? Saying there is almost no difference between the Verisign MLs and XTNS MLs is absurd. The Verisign ones should shortly be in the root, the XTBS ones will never be. You don't get that distinction? -g
    [ Reply to This | Parent ]
    Re: Verisign Announces Internationalized Domain Na
    by Anonymous on Tuesday October 02 2001, @06:09AM (#2678)
    The question fnord is do YOU get the distinction. I fear you don't ...

    You do understand don't you that the actual multilingual NSI IDNs themselves are NOT going in the root? That it is only the AMC-ACE-Z representations of them that are going in the root? And that this means that the IDNs themselves (the actual foreign language character set names) will NOT work with email or ftp clients?

    So if NSI IDNs are in the root and XTNS ones are not, what is the difference? The SOLE practical difference is that users will be able to manage their own zone files in a usual manner rather than having to manage them via NSI's mltbd.com site. That is the ONLY difference.

    You didn't think that these IDNs going in to the root would make them work like ascii TLDs such as ".com" ".biz" etc, did you? That email or ftp or etc would work? Not only every email and ftp client on the planet has been upgraded to understand Unicode, and that's years off, but every smtp server etc would have to be upgraded too ...

    EMAIL: Right now both NSI's IDNs and XTNS's mlDNs are identical in the way they handle email. In both cases there is an ASCII equivalent of every name (was coded in RACE, now in AMC-ACE-Z, which is thankfully about to get its first real name). Thus both of them handle email in the form "sam@bq--nnn.com" or similar.

    What XTNS was talking about is an advanced multilingual email client and web-based email scheme that will enable users to not have to enter the lengthy ASCII encoded versions of the ML names.

    Clear now?

    Repeat after me, even when the NSI IDNs go in to the root there will be in real terms no difference between them and XTNS mlDNs ... as surprising or hard to believe as that might be to those of you who thought that getting in to the root solved everything, enabled ftp/email/etc, and so forth. Sorry to be the one to burst your bubble guys.

    Postscript: all this is NOT to say that NSI's IDNs are lesser for this reality lesson. Not that they have been 'reduced' to the level of XTNS names. Rather, what NSI and XTNS are doing are BOTH needed and highly sought after services and the method of achieving the goals for now may not be perfect, but they are the best we have.
    [ 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