Browser IDN display policy: opinions sought
jean-michel bernier de portzamparc
jmabdp at gmail.com
Sat Dec 10 01:19:48 CET 2011
I am afraid this debate is among people who read ASCII characters, believe
that Registries have IDNA2003 policies when IDNA2008 default should be OK
for all and is the rule for 3rd level DNs, confuse the TCP/IP international
network with the Internet, and think that ICANN and GAC have something to
do with the digital ecosystem technology.
There is only one thing which is demanded by users : WITISWISISWIS and no
application interference. Otherwise it means that every application and
each application version will result in its own internet.
Now, if browsers manufacturers want to support additional optional service
pluggins with A,B,C,.... Y,Z strategies this is very nice of them: they
write an RFC describing their protocosl and make their complete support
1. Browsers MUST support any IDN made of any IDNA2008 permitted character,
whatever the TLD, etc. etc.
2. Right clicking on an URL should allow users to see its punycode
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Idna-update