Discuss mailing list

[Coyo <coyo AT darkdna.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 2/15/2014 2:24 PM, Alex Hanselka wrote:
> On 2/15/2014 2:08 PM, Coyo wrote:
>> It looks like unicode is not directly supported, but has an
>> encoded form called Punycode.
>>> In other words, is a TLD like උʘຯᛜ, for instance, or ฿tc or Ⓐno
>>> as
> It sure is possible! They are called Internationalized Domain
> Names (IDN).  Some browsers will do all the punycode on the backend
> so you still see the unicode, some don't (and this applys for
> second and third level too).  There are a handful in use at this
> time with ICANN and more on the way. I know Japanese みんな meaning
> all or everyone is currently in preorder status.
> 
> Here are some links for future research :)
> 
> http://en.wikipedia.org/wiki/Internationalized_country_code_top-level_domain
>
> 
http://en.wikipedia.org/wiki/Internationalized_domain_name
> http://en.wikipedia.org/wiki/Punycode 
> http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains 
> http://icannwiki.com/index.php/New_gTLD_IDN_Applications (this is a
> list of all of the proposed new IDNs for the gTLD thingy)

Would it be possible to use DNS without punycode? I realize this would
be non-standard, and would break compatibility with DNS servers in the
public Internet, but is there any protocol-specific reason you can't?

My understanding was that the engineers who came up with DNS decided
allowable characters to be ASCII simply because they didn't expect the
Internet to become international and huge.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS//WBAAoJEDEXTUGm1DyUIi4IAKvOkHXVL2PuKi9k6ugHozKd
tBzUK/FuMxa8yZgt55FZUw6Np4MlM5/GxrMjQ6v8mvKxR5fxSSYgX5xEKoku7eO6
0VVSPz3lLe/ig7JVMY6KyznSuQd00XIwEqO6dd+KmpjmtqiVbh5Z4Ti284JIVUOs
wCBMKLc7EyuOL0i0RVLPMYYRg27LkcdMqeJd04eCnKW+IIs8FTuRhqxBdUOEPtYV
QBxfUw1Mm0YOmA+/LL456it0EeFrDdpl7/0COmRYzKN+A5IJb4qFFMUouQ829Ym2
nws8/IT2cuQPdODesrXs3qJzP7UQFT3+ikKJiWSCPga2IcRIC3JMPAdIqbCcP6k=
=cKMB
-----END PGP SIGNATURE-----