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)


     
    Multi-lingual Domain Names Punycode IDN now active for .com and .net
    posted by michael on Tuesday December 23 2003, @01:29PM

    yggdrazil writes "I can't see that anyone has mentioned this, so I will: IDN domain names using the proper Punycode standard are now active in DNS!!! Domain names previously registered with a BQ-- prefix is now active in the root zone for .com and .net as their XN-- equivalent. Happened a few days ago.

    Example:
    http://www.grötärgött.com/
    http://www.xn--grtrgtt-7wa4ne.com/

    This means that these domains now work in standards based browsers, like Firebird, Camino and Opera. Currently the IDNNow plugin seems to be required to get it to work in MSIE. And I don't think it works in Safari yet."
    [Editor's note: didn't work for me in Mozilla 1.5 either...]



    "BQ-- prefixed IDN domain names seems to be missing from whois, and replaced by their XN-- equivalent.

    I think about 5% of .com and .net domain names are IDN domain names. So this is not a fringe market, this is a sizeable market worth getting your systems to support.

    Time for all of you to fix your isValidEmailAddress and isValidURL methods, etc. Domain names now contain more than A-Z, a-z, 0-9 and - "

     
      ICANNWatch Login  
    Nickname:

    Password:

    [ Don't have an account yet? Please create one. It's not required, but as a registered user you can customize the site, post comments with your name, and accumulate reputation points ("karma") that will make your comments more visible. ]

     
      Related Links  
    · http://www.grötärgött.com/
    · http://www.xn--grtrgtt-7wa4ne. com/
    · More Multi-lingual Domain Names stories
    · Also by michael
     
    This discussion has been archived. No new comments can be posted.
    Punycode IDN now active for .com and .net | Log in/Create an Account | Top | 11 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.
    Not quite right
    by KarlAuerbach on Tuesday December 23 2003, @04:09PM (#12764)
    User #3243 Info | http://www.cavebear.com/
    The main article said:

    "Domain names now contain more than A-Z, a-z, 0-9 and -"

    That's not quite right - the actual domain name carried in DNS packets still consists of the same character set as before, which for "hostnames" is alphanumerics and embedded hyphens. The "new" character sets exist outside of the DNS protocol and are the result of a mapping/translation process layered upon DNS, not within DNS.

    In other words, if you are sniffing the packets flying past on the network, the bytes in the DNS queries, even if it represents an IDN name, still consists of the same old character set.

    The IDN "view" is created by user applications, not by DNS itself. (And as the main article points out, relatively few applications are able at this date to create the "view".)

    (By-the-way, that limited "hostname" character set - it is far far from clear to me whether that limitation ought to apply to DNS names that are clearly not host names, such as ENUM/NAPTR names or names of SPF anti-spam records.)
    [ Reply to This | Parent ]
    Not in Mozilla 1.4b
    by ldg on Wednesday December 24 2003, @01:34AM (#12766)
    User #2935 Info | http://example.com/
    It didn't work in Mozilla 1.4.b or 1.01 either. I think I read something about an add-in or module somewhere in the docs for 1.5, but you have to hunt for it and choose to include it.

    I don't read or speak any languages that use IDN characters, so I would not choose to implement additional modules and prefer to not receive email in languages I don't understand. I think many people will feel the same way, so the market for the IDN domains will be within the areas where the languages are spoken/read. I don't know how ISPs will handle email, however. Many filter on non-english character sets because of the high numbers of spam using them. It's going to be interesting.
    [ Reply to This | Parent ]
    This forum messed up the link...
    by dtobias (dan@tobias.name) on Wednesday December 24 2003, @03:22PM (#12768)
    User #2967 Info | http://domains.dan.info/
    I think ICANNWatch's software filters out funny characters from links... it came out as http://www.grtrgtt.com/, with the non-ASCII stuff removed. That would explain why the link doesn't work even in supporting browsers.
    [ Reply to This | Parent ]
    • 1 reply beneath your current threshold.
    IDN in TLDs?
    by ukryule on Thursday December 25 2003, @11:37PM (#12772)
    User #3723 Info
    Are there any proposals to have new international TLDs? In particular, it's all very well allowing domains like '游允斌.com' - but '游允斌.台灣' makes a lot more sense as you aren't mixing two completely different character sets.

    I know that there is a new TLD application process underway [icann.org], but haven't heard if anyone is considering proposing some IDNs. I would assume that all countries with a non-Latin based language (e.g. Asian & Middle-Eastern) would love this: offer full domains in the local language AND get everyone in the country to buy a new domain (loadsa money!).
    [ Reply to This | Parent ]
  • 1 reply beneath your current threshold.

  • 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