Re: [idn] Re: stability

"Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord.cnri.reston.va.us> Wed, 16 March 2005 09:20 UTC

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23054 for <idn-archive@lists.ietf.org>; Wed, 16 Mar 2005 04:20:34 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1DBUZ2-0009EM-Cy for idn-data@psg.com; Wed, 16 Mar 2005 09:11:40 +0000
Received: from [64.36.79.201] (helo=nicemice.net) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44 (FreeBSD)) id 1DBUYv-0009Dd-Ah for idn@ops.ietf.org; Wed, 16 Mar 2005 09:11:33 +0000
Received: from amc by nicemice.net with local (Exim 4.44) id 1DBUYp-0006Kq-5f for idn@ops.ietf.org; Wed, 16 Mar 2005 01:11:27 -0800
Date: Wed, 16 Mar 2005 09:11:27 +0000
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord.cnri.reston.va.us>
To: idn@ops.ietf.org
Subject: Re: [idn] Re: stability
Message-ID: <20050316091126.GA24254~@nicemice.net>
Reply-To: IETF idn working group <idn@ops.ietf.org>
References: <42322CE2.4040509@vanderpoel.org> <4232B2FD.1080104@vanderpoel.org> <4232BA56.5090001@vanderpoel.org> <iluk6odazwb.fsf@latte.josefsson.org> <00e801c528a8$99ad37d0$72703009@sanjose.ibm.com> <ilull8qb5n5.fsf@latte.josefsson.org> <42367B63.6080300@vanderpoel.org> <4237450A.9010901@v.loewis.de> <423754F3.50405@vanderpoel.org> <ilumzt47ezc.fsf@latte.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <423789AA.9010203@vanderpoel.org> <ilumzt47ezc.fsf@latte.josefsson.org>
User-Agent: Mutt/1.5.6+20040907i
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

Erik van der Poel <erik@vanderpoel.org> wrote:

> I was referring to the RFC that has a pointer to UAX #15, i.e. RFC
> 3454 (Stringprep).  The pointer should be updated to tracking number
> 24 or higher.
>
> http://www.unicode.org/reports/tr15/tr15-24.html

I agree.  Right now there does not exist a correct implementation of
Unicode normalization anywhere.  Some implementations are wrong because
they deviate from the spec, and other implementations are wrong because
they adhere to the spec which itself is wrong (because it violates all
the fundamental properties that anything called a canonical form is
assumed to have).  It's an unfortunate situation, but the best thing to
do now is fix the spec and encourage all implementations to converge on
the fixed spec, which is what the Unicode Consortium is doing.  Our part
in this is to update our pointer, so that it points at a correct spec
rather than a wrong spec.

Simon Josefsson <jas@extundo.com> wrote:

> I believe it would be useful to start thinking of the problem in terms
> of a transition plan from what we have today and what we would like to
> have tomorrow.  It is not clear to me exactly what we would like to
> have tomorrow, so settling that would have to be part of the plan as
> well.

It's clear to me what we ought to have tomorrow: a canonical form
(that is, a function that selects a unique representative from every
equivalence class).  The Unicode Consortium is taking care of defining
that.

Do you have any ideas for a transition to that?

AMC