[idn] Re: stability

Simon Josefsson <jas@extundo.com> Tue, 15 March 2005 21:59 UTC

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25357 for <idn-archive@lists.ietf.org>; Tue, 15 Mar 2005 16:59:06 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1DBJze-000CL7-Is for idn-data@psg.com; Tue, 15 Mar 2005 21:54:26 +0000
Received: from [217.13.230.178] (helo=yxa.extundo.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44 (FreeBSD)) id 1DBJzS-000CJ9-Mp for idn@ops.ietf.org; Tue, 15 Mar 2005 21:54:15 +0000
Received: from latte.josefsson.org (c494102a.s-bi.bostream.se [217.215.27.65]) (authenticated bits=0) by yxa.extundo.com (8.13.3/8.13.3/Debian-6) with ESMTP id j2FLs3ib008879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 Mar 2005 22:54:05 +0100
From: Simon Josefsson <jas@extundo.com>
To: Erik van der Poel <erik@vanderpoel.org>
Cc: Mark Davis <mark.davis@jtcsv.com>, idn@ops.ietf.org, "Martin v. Löwis" <martin@v.loewis.de>
Subject: [idn] Re: stability
References: <421B8484.3070802@vanderpoel.org> <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> <A574CA1BE87BFDA3C2A1AC0E@scan.jck.com> <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>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
Blog: http://www.livejournal.com/users/jas4711/
X-Hashcash: 1:21:050315:martin@v.loewis.de::g9fbYied2bAw3vqe:0Nsu
X-Hashcash: 1:21:050315:idn@ops.ietf.org::NHRcOPwT7KQmLHuX:0MNQ
X-Hashcash: 1:21:050315:mark.davis@jtcsv.com::lb+dSFqyYnF1MXyX:Bsrg
X-Hashcash: 1:21:050315:erik@vanderpoel.org::01WwhjinQezDRSMz:KOrz
Date: Tue, 15 Mar 2005 22:53:43 +0100
In-Reply-To: <423754F3.50405@vanderpoel.org> (Erik van der Poel's message of "Tue, 15 Mar 2005 13:34:43 -0800")
Message-ID: <ilumzt47ezc.fsf@latte.josefsson.org>
User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on yxa.extundo.com
X-Virus-Status: Clean
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

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

>>> More importantly, this mistake only affects highly unusual,
>>> malformed data. I think that if IDNA decides not to follow
>>> Unicode's recommendation now or in the next couple of years, 10 or
>>> 20 years from now we would look back in time and regret this
>>> decision. 
>> I don't think so. "We" could still change the decision in 20 years,
>> and
>> not a single registration would be affected. The sequences causing the
>> behaviour change are *really* unusual - I don't know if software can
>> visually render them in a meaningful way, and I guess a native speaker
>> would just consider them moji-bake. So it is unlikely that anybody would
>> try to use them as input to IDNA in the next 20 years in a reasonable
>> application.
>
> If we do not correct the specs, more and more implementations will be 
> created and deployed, some implementing it one way, the others the other 
> way. It is hard to change something when a lot of implementations have 
> been deployed. This is why we have to act now (or soon). We have to nip 
> it in the bud.

I think it may be too late to do a simple flag day and fix things.

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.

Thanks,
Simon