IETF Logo Mail Archive

Re: [idn] nameprep2 and the slash homograph issue

"JFC (Jefsey) Morfin" <jefsey@jefsey.com> Wed, 23 February 2005 17:14 UTC

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13523 for <idn-archive@lists.ietf.org>; Wed, 23 Feb 2005 12:14:37 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1D4025-000Mir-SI for idn-data@psg.com; Wed, 23 Feb 2005 17:10:41 +0000
Received: from [63.247.74.122] (helo=montage.altserver.com) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D401w-000Mhu-Tz for idn@ops.ietf.org; Wed, 23 Feb 2005 17:10:33 +0000
Received: from if12m4-235.d2.club-internet.fr ([212.195.66.235] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1D401v-0003Jf-6Y; Wed, 23 Feb 2005 09:10:31 -0800
Message-Id: <6.1.2.0.2.20050223180502.031d5730@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Wed, 23 Feb 2005 18:06:33 +0100
To: Erik van der Poel <erik@vanderpoel.org>, IETF idn working group <idn@ops.ietf.org>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Subject: Re: [idn] nameprep2 and the slash homograph issue
In-Reply-To: <421CA114.9090302@vanderpoel.org>
References: <421B8484.3070802@vanderpoel.org> <20050223072837.GA21463~@nicemice.net> <D872CCF059514053ECF8A198@scan.jck.com> <20050223105244.GE21463~@nicemice.net> <421CA114.9090302@vanderpoel.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ops.ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
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

At 16:28 23/02/2005, Erik van der Poel wrote:
>Adam,
>The IETF generally only specifies the "wire" protocol, not UI behavior. 
>The IETF does not specify how apps interface with users; it only specifies 
>how apps interface with other apps, over the wire. Note that this does not 
>even include APIs in many cases.
>
>However, it *would* be very wise to *warn* implementors about any 
>dangerous homographs in the new RFC (if we decide not to ban them outright).

Yes. But this does not prevent to warn in proposing solutions to the system 
conceptual problems, like for tables. The same for TLD Managers.
jfc

v2.23.0 | Report a Bug | By Email