Re: [idn] punctuation

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

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04754 for <idn-archive@lists.ietf.org>; Thu, 24 Feb 2005 18:09:16 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1D4S1n-0005nd-CY for idn-data@psg.com; Thu, 24 Feb 2005 23:04:15 +0000
Received: from [207.115.63.101] (helo=pimout2-ext.prodigy.net) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D4S1m-0005mZ-B1 for idn@ops.ietf.org; Thu, 24 Feb 2005 23:04:14 +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 j1ON40uq126642; Thu, 24 Feb 2005 18:04:05 -0500
Message-ID: <421E5D60.3050802@vanderpoel.org>
Date: Thu, 24 Feb 2005 15:04:00 -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: John C Klensin <klensin@jck.com>
CC: tedd <tedd@sperling.com>, 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> <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>
In-Reply-To: <0E7F74C71945B923C52211F3@scan.jck.com>
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

John C Klensin wrote:
> 
> So, like it or not, I think you had best let this one go and get
> used to it.  FWIW, my ordering preference is the same as yours.

OK, I'll stop talking about domain name display order. (But you've all 
been warned.)

Back to the business at hand: For Nameprep, I've been wondering whether 
it would make sense to explore what exactly would have to happen if we 
were to change the ACE prefix from xn-- to something else. I.e. clients 
would have to be updated, servers would have to accept both the old and 
the new during the transition period, etc. I'm not even sure this is 
correct.

Anyway, I think such an exploration, including many details, might tell 
us whether or not we should even contemplate making an incompatible 
change to Nameprep.

Or do people think that we should approach this from the other side? 
I.e. if we can come up with seriously dangerous homographs and other 
characters that must be banned or mapped in a new nameprep, then this 
could in itself be viewed as justification for a new ACE prefix, 
regardless of how hard it might be to add it or move to it.

Thoughts?

Erik