[UA-discuss] IDN Implementation Guidelines [RE: Re : And now about phishing...]

Asmus Freytag asmusf at ix.netcom.com
Fri Apr 21 19:10:38 UTC 2017

On 4/21/2017 11:47 AM, Andrew Sullivan wrote:
> On Fri, Apr 21, 2017 at 07:11:00PM +0200, Dusan Stojicevic wrote:
>> Besides paypal, apple, epic, there is as much brands as you want, which can be made from just Cyrillic chars: Coca-cola, Pepsi, Opel, IBM...
> See Asmus's notes, but there's a basic problem here: there is at
> bottom no way to fix this generally.  If you want to expand the
> character repertoire of identifiers to encompass all the characters
> humans use, it is going to come with a considerable risk of potential
> confusion.  There is nothing remotely new about this.  (The only
> really new thing here is someone successfully whipping up anxiety over
> this supposed "bug", and even that is just a rerun of previous similar
> events.)
> I think this group could do some useful things.  For instance, if we
> funded open code for variant calculation and found some additional
> people who were willing to learn about the details (this requires at
> least actually reading the Unicode spec) to pour into the i18n issues,
> I think that would be a contribution.

Two observations:

(1) Understanding how to use and define variants is a first step.

I created a draft to explain the technical side of that, but it's stuck 
in the ietf because of alleged controversies about its status while I 
get clear indication from the comments that nobody actually read much of 
anything past the abstract. >:(

For the record, here it is:

feedback welcome.

(2) There is considerable work being done on creating data that are 
better focused than what UTR#39 has; and in format more directly usable 
for anyone following RFC 7940. The trick is in collecting and publishing 
this somewhere.


More information about the UA-discuss mailing list