Re: Internationalized domain names in the root
> Wait until the FCC, FTC, and IRS finish taking over the Internet. You forgot FBI, NSA and CIA, just to mention a few more three letter agencies ... k'mon gimme a break. Cheers
Re: Internationalized domain names in the root
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/7/2010 22:53, Peter Beckman wrote: > On Fri, 7 May 2010, Jeroen van Aart wrote: > >> David Conrad wrote: >>> Perhaps a bit off-topic, but some folks might get support calls... >>> >>> http://وزارة-الأتصالات.مصر/ >> >> That actually looks quite handsome. :-) > > And this is what it looks like to DNS: > > http://xn--4gbrim.xnrmckbbajlc6dj7bxne2c.xn--wgbh1c/ > > Hurrah for Punycode. Yeah I was experimenting around with that yesterday. Imagine a zone file full of such domain names. Ack! "Did I accidentally hit x in the middle of that name in VIM? Better run it through the converter to make sure." Yay yet another level of complexity in DNS management. Some of the names look as ugly as the contents of DNSSEC RRs. :-) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvluX8ACgkQ2fXFxl4S7sTghwCg8sh1ZrKpa3d/GlYaGYhAZKN+ /HEAmgPrKZaaHynHRQuTAYfe4xQAWIh1 =cO/L -END PGP SIGNATURE-
Re: Internationalized domain names in the root
On 5/8/2010 07:36, Phil Regnauld wrote: > Neil Harris (neil) writes: >> >> To fix it, the .eg / .xn--4gbrim TLD registrar needs to contact the >> Mozilla Foundation in order to inform the Foundation of their >> official IDN name allocation policy, so that the native-script URL >> display can then be switched on for their domain. >> >> See https://bugzilla.mozilla.org/show_bug.cgi?id=564213 and >> http://www.mozilla.org/projects/security/tld-idn-policy-list.html > > Wow, talk about layer violation. > > Is there a central place where various TLDs' IDN policies will > be maintained ? I see a scalability issue if TLDs have to communicate > to every single application maintainer out there what their policy is. Wait until the FCC, FTC, and IRS finish taking over the Internet. -- Somebody should have said: A democracy is two wolves and a lamb voting on what to have for dinner. Freedom under a constitutional republic is a well armed lamb contesting the vote. Requiescas in pace o email Ex turpi causa non oritur actio Eppure si rinfresca ICBM Targeting Information: http://tinyurl.com/4sqczs http://tinyurl.com/7tp8ml
Re: Internationalized domain names in the root
>> To fix it, the .eg / .xn--4gbrim TLD registrar needs to contact the >> Mozilla Foundation in order to inform the Foundation of their >> official IDN name allocation policy, so that the native-script URL >> display can then be switched on for their domain. > > Wow, talk about layer violation. Yeah, security can be like that. Things which technically are treated the same are often semantically very different. > Is there a central place where various TLDs' IDN policies will > be maintained ? Yes, of course. See http://www.iana.org/domains/idn-tables/ It doesn't have the new IDN TLDs yet, but that's not surprising since ICANN didn't bother to tell the registries in advance that would be making the TLDs active. See http://www.circleid.com/posts/by_the_way_your_idn_is_live/ R's, John
Re: Internationalized domain names in the root
Neil Harris (neil) writes: > > To fix it, the .eg / .xn--4gbrim TLD registrar needs to contact the > Mozilla Foundation in order to inform the Foundation of their > official IDN name allocation policy, so that the native-script URL > display can then be switched on for their domain. > > See https://bugzilla.mozilla.org/show_bug.cgi?id=564213 and > http://www.mozilla.org/projects/security/tld-idn-policy-list.html Wow, talk about layer violation. Is there a central place where various TLDs' IDN policies will be maintained ? I see a scalability issue if TLDs have to communicate to every single application maintainer out there what their policy is. Cheers, Phil
Re: Internationalized domain names in the root
On 06/05/10 21:27, Zaid Ali wrote: I agree Safari experience looks much nicer and yes whole host of potential malice to arise. Firefox shows punycode http://xn--4gbrim.xnrmckbbajlc6dj7bxne2c.xn--wgbh1c/ar/default.aspx Now if I understood arabic only and was travelling or happen to use Firefox which showed punycode how would I trust it? If it was directly translated to latin characters I could trust it with verification from someone I know who understands english. I would not trust puny code because an end user does not know what it means, I think there is potential for a lot of issues here. Zaid This is indeed a security issue, and the behaviour in Firefox is currently that way by design. To fix it, the .eg / .xn--4gbrim TLD registrar needs to contact the Mozilla Foundation in order to inform the Foundation of their official IDN name allocation policy, so that the native-script URL display can then be switched on for their domain. See https://bugzilla.mozilla.org/show_bug.cgi?id=564213 and http://www.mozilla.org/projects/security/tld-idn-policy-list.html -- Neil
