Slashdot Mirror

← Back to Domains

Domain: i-d-n.net

Stories and comments across the archive that link to i-d-n.net.

Comments · 7

  1. Re:God what a clusterfsck by Zeinfeld · · Score: 1 · on VeriSign Changes DNS Servers: No ASCII Needed
    I understand that having non-ascii characters in host/domain names would be desirable, however if they can't do it without breaking the DNS protocol, then they should get their ass right back to the R&D lab and try harder.

    The DNS protocol has been extended to support non-ascii characters years ago. There is no real disagreement over the general approach, you simply use an approach similar to Base64 encoding on the domain name with a prefix of '--' which is safe because leading dashes are not permitted in DNS names, although the servers are required to resolve them.

    If the IAB were not almost exclusively American academics this whole spec would have been finished four years ago. Instead they are happy to discuss any issue for years so long as there is no danger of a resolution.

    It is particularly ironic that they are waffling about DNSSEC since it is the timidity and ineffectiveness of the IAB and IESG that has caused that spec to be delayed so long. It has taken three years for them to accept that the original DNSSEC spec was broken.

    Internationalization and DNSSEC have been going on for ten years. The IAB seem quite content for them to go on for another ten years.

    So don't get too excited by IPV6. It does not look likely that anyone is going to kick the IAB and IESG into action.

  2. Not True by waldoj · · Score: 5, Informative · on Sometimes, Microsoft is Right...

    As much as we English loving types had no use for real names, it was a viable way for Asian countries to use their own characters for DNS entries. It had a chance of being a standard.

    Speaking of standards...

    The IETF Internationalized Domain Names Working Group
    IBM On Unicode Domain Names
    Slashdot: Why Unicode will Work on the Internet
    Verisign's Internationalized Domain Name Testbed

    -Waldo Jaquith

  3. Re:Real Names sucks, 'cept for ALL of Asia by fungus · · Score: 4, Informative · on Sometimes, Microsoft is Right...

    Unicode DNS exists.

    Even Microsoft supports it.

    Some internet draft...
    another interesting one.

  4. idn should help by dimitri_k · · Score: 1 · on Is The Internet Destroying Spanish?

    IDN should help with at least one barrier, multilingual domain names.

    d

  5. Multilingual Domain Names by Smuj · · Score: 3 · on Registrations Now Accepted For Asian Domain Names

    A few notes...

    The Internet Society probably isn't too happy about this. They released a statement on November 8th encouraging NSI to back off and let the IETF IDN WG do its job.

    Also, there are companies that are already currently operating in this market, including WALID, which is taking registrations for Arabic domain names (AND RESOLVING THEM), and will soon be adding Hindi, Tamil, and two Chinese scripts before moving into other markets.

  6. Internationalized Domain Names by jseng · · Score: 1 · on ICANN Plans Non-English Character Domain Testbed

    For those who are interested in IDN, here are some URL.

    IETF IDN WG
    http://www.i-d-n.net/

    NSI Registry Testbed
    http://www.nsiregistry.com/

    i-DNS.net (Technology Provider for NSI ML.com testbed)
    http://www.i-DNS.net/

    Multilingual.COM Promotion
    http://we-multilingual.com/

  7. It's not ICANN, and it's not non-English by paulhoffman · · Score: 2 · on ICANN Plans Non-English Character Domain Testbed
    As pointed out in the main link, ICANN has nothing to do with the testbed. NSI Registry (not the registrar) decided to do it because, if the IETF makes this available, it would be nice of the registrars in com/net/org were able to register the names. There are already other testbeds run by other (less newsy) groups of people; you can even set up your own. It's not that big of a deal.

    And it's "non-ASCII", not "non-English". There are already plenty of domain names that are non-English, as others have pointed out already. ASCII is a character set (of sorts); English is a human language. The differences are defined in detail in the requirements document for the IETF's working group.

    Full details on the working group can be found at http://www.i-d-n.net. Maybe folks should consider reading the copious archives before declaring that it can't be done. It can be done, and hopefully it can be done right. We're quite sure that the Powers That Be in the IETF won't allow it to become a standard if it isn't right.