Re: [idn] punctuation

Erik van der Poel <erik@vanderpoel.org> Thu, 24 February 2005 18:04 UTC

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24017 for <idn-archive@lists.ietf.org>; Thu, 24 Feb 2005 13:04:10 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1D4NIO-000JqK-LN for idn-data@psg.com; Thu, 24 Feb 2005 18:01:04 +0000
Received: from [207.115.63.77] (helo=pimout1-ext.prodigy.net) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D4NIM-000Jpw-Cw for idn@ops.ietf.org; Thu, 24 Feb 2005 18:01:02 +0000
Received: from [10.1.1.2] (adsl-64-174-147-206.dsl.sntc01.pacbell.net [64.174.147.206]) by pimout1-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id j1OI0xSJ208658; Thu, 24 Feb 2005 13:01:00 -0500
Message-ID: <421E165B.6040706@vanderpoel.org>
Date: Thu, 24 Feb 2005 10:00:59 -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: IETF idn working group <idn@ops.ietf.org>
Subject: Re: [idn] punctuation
References: <421B8484.3070802@vanderpoel.org> <20050223072837.GA21463~@nicemice.net> <D872CCF059514053ECF8A198@scan.jck.com> <421D8411.9030006@vanderpoel.org>
In-Reply-To: <421D8411.9030006@vanderpoel.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=BAYES_00 autolearn=ham version=3.0.1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> If they were displayed 
> in the opposite (big-endian) order, the 3rd example above would become:
> 
> http://xx.baz.com|bar.foo
> 
> Notice how the "com" and "foo" are now separated.

There was a gap in my logic here. A phisher could easily keep the "com" 
and "foo" next to each other. My real point is that big-endian display 
of domain names would put the important parts of the name near the 
beginning for a left-to-right reader:

> The "real" (unspoofed) 
> URI would look like this:
> 
> http://com.foo

Erik