Discuss mailing list

[Coyo <coyo AT darkdna.net>]

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

I like UTF32. It is deliciously overkill.

There is no kill like overkill.

On 2/15/2014 5:40 PM, John Kozlowski (ShofarDomain.com) wrote:
> The DNS protocol uses bytes, so 16 or 21 bit Unicode characters
> have to be encoded.  Using UTF8 would work fine, but there was a
> concern that you could fool someone to going to a rouge site by
> using look alike characters, such as a Cyrillic ‘Ϻ’ in place of an
> Latin ‘M’.  Punycode makes it obvious that you are using extended
> characters.  However, this is just another way of doing things when
> UTF8 would be great.  Fundamentally this issue of misdirection is
> probably overrated.
> 
> To experiment with this I obtained a name using Cyrillic
> characters.  Some browsers, such as IE, display punycode
> (http://xn--80aa3agvl7b6d.net), while others like Firefox display
> the UTF8 (http://матрёшка.net).  The is Russian for Matryoshka.
> 
> Personally I think IE got it wrong (have you heard this before?)
> since this is unreadable for us normal humans.  It might be nice if
> Firefox would somehow highlight the fact that extended characters
> are used.
> 
> Clearly as long as you are sending compatible information in the
> DNS query how you store or manage that in an application can be
> either punycode, UTF8, UTF16, UTF32, or EBCIDIC.  You might have
> issues with the last one.
> 
> John Kozlowski
> 
> -----Original Message-----
> 
> 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.
> 
> 
> 
> 
> 
> 
> -------- You are a member of the OpenNIC Discuss list. You may
> unsubscribe by emailing
> discuss-unsubscribe AT lists.opennicproject.org
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS//y4AAoJEDEXTUGm1DyUeXcH/j59IWX14+79f+jU2COQLbmx
PgSlcIkboZpYGCeGwuMQEEufB0e5muRPq0ic6JjwVyhi8BgJSd9+YreBNQ8FnWGO
JWTAqZe2ulS3P2BSjZ/JD/X/cGRRcEB49C2rubWrjAhAm8jPtRNvTdbHfQBj6a/Z
uyLN5sjCOjc+Mds1SaLoLxpG5GuBKZnzXm8UZ6TmvaAj/xEwdekrS5EOBW7pgFvF
suWVVpGLAKVQTq26S2e4hkvCf0gonu2NDuIcghAO91pB3srSRwV9YuEHLwxOuaJ4
LA0fneHdrYX+fJfzLHF/CjSphHAkTw+9uLntWvL4tJ4jMdVyLppUyGF63kx2p8g=
=x75O
-----END PGP SIGNATURE-----