Re: [idn] Re: process

Erik van der Poel <erik@vanderpoel.org> Fri, 25 February 2005 15:53 UTC

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02247 for <idn-archive@lists.ietf.org>; Fri, 25 Feb 2005 10:53:01 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1D4hfF-000CSv-4t for idn-data@psg.com; Fri, 25 Feb 2005 15:46:01 +0000
Received: from [207.115.63.98] (helo=pimout4-ext.prodigy.net) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D4hfB-000CSR-Q8 for idn@ops.ietf.org; Fri, 25 Feb 2005 15:45:58 +0000
Received: from [10.1.1.2] (adsl-64-174-147-206.dsl.sntc01.pacbell.net [64.174.147.206]) by pimout4-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id j1PFjmHb195030; Fri, 25 Feb 2005 10:45:53 -0500
Message-ID: <421F482B.1060909@vanderpoel.org>
Date: Fri, 25 Feb 2005 07:45:47 -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: Stephane Bortzmeyer <bortzmeyer@nic.fr>
CC: Doug Ewell <dewell@adelphia.net>, idn@ops.ietf.org
Subject: Re: [idn] Re: process
References: <D872CCF059514053ECF8A198@scan.jck.com> <421D8411.9030006@vanderpoel.org> <p06210208be4390618c81@[192.168.0.101]> <421E0D0C.2000309@vanderpoel.org> <p06210202be43c3888991@[192.168.0.101]> <E07CE813AD23B2D95DA0C740@scan.jck.com> <421E30F2.1040408@vanderpoel.org> <0E7F74C71945B923C52211F3@scan.jck.com> <421EA0C9.1010500@vanderpoel.org> <00a401c51af3$7863aae0$030aa8c0@DEWELL> <20050225113725.GA8820@nic.fr>
In-Reply-To: <20050225113725.GA8820@nic.fr>
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=BAYES_00 autolearn=ham version=3.0.1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Stephane Bortzmeyer wrote:
> The issue has been discussed at length. See
> the "Security Considerations" of RFC 3490.

It is true that some of the issues are pointed out by that section, so 
the registries and application developers have to pay attention. But one 
  might argue that we have recently been discussing a new *class* of 
homographs. The RFC mentions "multiple scripts" and one and l. These two 
refer to letters such as Cyrillic small 'a' and digits (the "one"). But 
the slash homograph recently raised on this list might be considered to 
be a new class of homograph (punctuation), not specifically indicated in 
the RFC. Not only is this type of character different from letters and 
digits, it is arguably even more dangerous than the script-based 
(Cyrillic) attack, since it can be done in a domain label that is not 
under the control of the registries. So that first line of defense is 
not there, and we must rely totally on the apps, and there are many.

One could argue that a new document should be published and widely 
circulated to warn about this new kind of attack. One of my questions is 
whether this warning should appear in a new version of the RFC, or in a 
separate document. Alternatively, it may be decided that this type of 
homograph is so different and so dangerous that a new version of the 
protocol that prohibits these characters, with a new ACE prefix, should 
be created. I don't know.

Also, the "multiple scripts" wording does not specifically cover the 
all-Cyrillic case. So that part could be tightened up too.

By the way, the RFC's Security section includes the following:

    No security issues such as string length increases or new
    allowed values are introduced by the encoding process or the use of
    these encoded values, apart from those introduced by the ACE encoding
    itself.

What does this mean, exactly? Are any new allowed values introduced by 
the ACE encoding? This part could be clearer.

Also, O and 0 are mentioned, but is this technically correct? I mean, 
aren't uppercase ASCIIs supposed to be lowercased? I'm sorry if I'm 
wrong about this part.

> Nothing new in the recent announces, just
> sensation papers.

Again, I think the slash homograph might be new. Do you have evidence to 
suggest that it *was* considered by the WG or anybody else?

> The Powers Above require that Something should be done

Have you seen any indication of this?

Thanks,

Erik