User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31 Steps to reproduce: DNS Belgium (the registry for the .be ccTLD) has implemented IDN (Internationalized Domain Names General availability of second-level IDN under .be will start on 11 June 2013. DNS Belgium has implemented IDNA2008. We will only accept latin codepoints so there is no danger for IDN homograph attacks. Our policy and the list of supported IDN codepoints can be found here: http://www.dns.be/en/idn Maarten Bosteels Head of Development at DNS Belgium Expected results: Second-level .be domain should be rendered in their unicode form by the browser. Therefore the .be TLD should be added to the whitelist for IDN TLD's.

In my opinion this request does not depend on 479520 [1] We would like .be to be added to the IDN whitelist ASAP and not wait until firefox implements IDNA2008 (although we are of course in favor of implementing IDNA2008). Our policy is equally or more restrictive than the one set out in the algorithm document at [2] so all conditions (listed on [3]) to be added to the whitelist stated are met. Please note that .de also implements IDNA2008 and they are on the whitelist. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=479520) [2] https://wiki.mozilla.org/IDN_Display_Algorithm [3] http://www.mozilla.org/projects/security/tld-idn-policy-list.html

It still depends on bug 479520, but that one doesn't block the addition of .be to the whitelist. The link was just a reminder to the people from bug 479520 that there's one more TLD that will start to use IDNA2008.

Jo, this ticket is only about adding .be to the whitelist and you state yourself that bug 479520 isn't needed to do that. Isn't that the definition of "depends on" ? What about creating a separate ticket requesting support for IDNA2008 for .be ? That one would depend on 479520.

I created 883796 which depends on 479520.

I also created bug 883796 which depends on bug 479520.

We now have an algorithmic method of determining IDN suitability, and so we are no longer accepting additions to the whitelist. See https://wiki.mozilla.org/IDN_Display_Algorithm for more details. Gerv

'... and so we are no longer accepting additions to the whitelist.' => That contradicts what is written on https://wiki.mozilla.org/IDN_Display_Algorithm <quote> In between adopting this plan and shipping a Firefox with the restrictions implemented, we will admit into the whitelist any TLD whose anti-spoofing policies at registration time were at least as strong as those outlined above </quote> Maarten

Apologies, I just discovered that bug https://bugzilla.mozilla.org/show_bug.cgi?id=722299 is marked as resolved and is part of firefox 22. Just downloaded firefox 22 and did a quick test: second-level .be domain are now rendered in their unicode form by the browser. Thanks!