Accountapprovers, antispam, confirm, emeritus
4,925
edits
Changes
no edit summary
This page explains the plan for changing the mechanism by which Firefox decides whether to display a given IDN domain label (a domain name is made up of one or more labels, separated by dots) in its Unicode or Punycode form.
==Background==
===The Problem===
If we just display any possible IDN domain label, we open ourselves up to [http://en.wikipedia.org/wiki/IDN_homograph_attack IDN homograph attacks], where one identical-looking domain can spoof another. So we have to have some mechanism to decide which ones to display and which ones to not display, which does not involve comparing the domain in question against every other single domain which exists (which is impossible).
===Current Algorithm===
of the policies of Chrome/Chromium and the other browsers. Unfortunately, no consensus has emerged on how to do
this. Those other mechanisms were considered, but many of them depend on the configuration of the user's
computer (e.g. installed languages), and this does not give site owners any confidence that their IDN domainname will be correctly displayed for all their visitors (and no way of telling if it's not).
==Proposal==
some domains which worked previously, and b) if a registry submits a
good policy, we have the ability to give them more freedom than the default restrictions do.
So an IDN domain would be shown as Unicode if the TLD was on the whitelist or, if not, if it
met the criteria above.
a definition for how we detect whether a string is "single script". Some Common or Inherited characters
are only used in a small number (but more than one) script. Mark Davis writes:
"The Unicode Consortium in U6.1 (due out soon) is adding the property [http://unicode.org/Public/6.1.0/ucd/ScriptExtensions.txt Script_Extensions],
to provide data about characters which are only used in a few (but more than one) script.
The sample code in #39 should be updated to include that, so handling such cases." We should
