Re: [idn] nameprep2 and the slash homograph issue

Erik van der Poel <erik@vanderpoel.org> Wed, 02 March 2005 17:22 UTC

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06308 for <idn-archive@lists.ietf.org>; Wed, 2 Mar 2005 12:22:32 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1D6XUx-000Ppm-1M for idn-data@psg.com; Wed, 02 Mar 2005 17:18:59 +0000
Received: from [207.115.63.101] (helo=pimout2-ext.prodigy.net) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D6XUu-000PpO-UB for idn@ops.ietf.org; Wed, 02 Mar 2005 17:18:57 +0000
Received: from [10.1.1.2] (adsl-64-174-147-206.dsl.sntc01.pacbell.net [64.174.147.206]) by pimout2-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id j22HIoaU328826; Wed, 2 Mar 2005 12:18:50 -0500
Message-ID: <4225F579.8080200@vanderpoel.org>
Date: Wed, 02 Mar 2005 09:18:49 -0800
From: Erik van der Poel <erik@vanderpoel.org>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gervase Markham <gerv@mozilla.org>
CC: idn@ops.ietf.org, Yngve Nysaeter Pettersen <yngve@opera.com>
Subject: Re: [idn] nameprep2 and the slash homograph issue
References: <421B8484.3070802@vanderpoel.org> <20050223072837.GA21463~@nicemice.net> <D872CCF059514053ECF8A198@scan.jck.com> <20050223105244.GE21463~@nicemice.net> <421CA114.9090302@vanderpoel.org> <20050224081721.GB12336~@nicemice.net> <421DEDFF.2000300@vanderpoel.org> <4225A87B.7030204@mozilla.org> <42251159.1040300@vanderpoel.org> <42257FA5.9060604@mozilla.org>
In-Reply-To: <42257FA5.9060604@mozilla.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gervase Markham wrote:
> Erik van der Poel wrote:
> > 
> > Also, do you know what happens if the domain name is very long? 
> 
> It just gets very long, currently.

I hope you will think about what to do when the name is really long, 
keeping in mind that the most important part of the name is the end (the 
right side).

> Well, the current domain indicator will show the domain, slash 
> homographs and all. We're still developing our response, but it's likely 
> that we'll have to blacklist this character. Opera's new beta already 
> has a small set of characters it doesn't allow.
> 
> Ideally, we wouldn't be acting unilaterally on this one, and would be 
> doing the restrictions based on consensus. But before we can go there, 
> we need to figure out what we think is needed first. That process is 
> still going on.

It's really great to hear this! I fully agree with you that consensus 
would be ideal. I'm taking the liberty of Cc'ing one of the Opera 
developers, in the hope that they might be willing to discuss their 
particular choices for the character blacklist. If various people can 
start to agree on a blacklist, this info can be fed into any RFC 
revision process (which I hope will begin).

> The issue, of course, is that the font designation we use has to produce 
> a good font on all platforms.

Yes, a good font on *all* platforms, and also for *all* parts of the 
world. I am quite aware of those issues. See the bottom of:

http://www.mozilla.org/projects/intl/fonts.html

One of the great things about open source is that lots of people from 
all over the world come to help you, with localizations, default font 
choices, etc.

Erik