Re: [idn] Re: stability

Erik van der Poel <erik@vanderpoel.org> Wed, 16 March 2005 18:16 UTC

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17878 for <idn-archive@lists.ietf.org>; Wed, 16 Mar 2005 13:16:28 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1DBd0N-000Al0-Qp for idn-data@psg.com; Wed, 16 Mar 2005 18:12:27 +0000
Received: from [207.115.63.102] (helo=pimout3-ext.prodigy.net) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1DBd0I-000AkY-4B for idn@ops.ietf.org; Wed, 16 Mar 2005 18:12:26 +0000
Received: from [10.1.1.2] (adsl-64-174-147-206.dsl.sntc01.pacbell.net [64.174.147.206]) by pimout3-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id j2GIBU9N393712; Wed, 16 Mar 2005 13:11:34 -0500
Message-ID: <423876D2.2070809@vanderpoel.org>
Date: Wed, 16 Mar 2005 10:11:30 -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: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
CC: "\"Martin v. Löwis\"" <martin@v.loewis.de>, Simon Josefsson <jas@extundo.com>, Mark Davis <mark.davis@jtcsv.com>, idn@ops.ietf.org
Subject: Re: [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> <ilumzt47ezc.fsf@latte.josefsson.org> <42375C9E.8040001@v.loewis.de> <4237917D.9080507@vanderpoel.org> <6.1.2.0.2.20050316125429.04464370@mail.jefsey.com>
In-Reply-To: <6.1.2.0.2.20050316125429.04464370@mail.jefsey.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
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
Content-Transfer-Encoding: 8bit

JFC (Jefsey) Morfin wrote:
> At 02:53 16/03/2005, Erik van der Poel wrote:
> 
>> Martin v. Löwis wrote:
>>
>>> What is much more relevant is how further constraints in the registry
>>> (beyond those imposed by IDNA) get implemented. Only when that is
>>> sufficiently settled and deployed, considering *updates* to IDNA
>>> should start.
>>
>> I disagree. The IETF should not wait for any of the registries to do 
>> anything before publishing new drafts or RFCs. The registries are not 
>> the only other players here. We have application developers and zone 
>> administrators depending on our work too.
> 
> Fully true. But we are in a real world. If you propose anything again 
> without the support of the Registries you will have a lack of 
> understanding, adherence and support. Also what you will propose will be 
> less reviewed from different point of view and will have more risks to 
> have its own flaws. You will not be able to tell the Registries they 
> shared in the mistake they have to share in the fix. 

I agree, and I can see why you react in this way to my email, but please 
look again at Martin's email. If we followed Martin's advice, we would 
wait quite a long time before even *considering* updates to IDNA. I 
think it's reasonable to *consider* changes and even to write drafts 
*before* the registries deploy further constraints.

Of course, we must involve the registries in the draft review process.

> The first step is to permit the Registries to operate in this still 
> debated environement.

I'm afraid I don't understand. The registry operators *are* already 
permitted to operate their registries.

> I have asked responses about that and got no 
> answer.

I find it very difficult to respond to your emails because you often 
bring up topics that I don't understand and seem somewhat unrelated, 
such as "PAD". Also, some of your emails seem to talk about a 
revolution, which is very difficult to bring about, and hence unlikely. 
I have made such proposals myself (e.g. displaying the domain name from 
left to right instead of right to left), but others have pointed out 
that such ideas are more in the theoretical realm than the practical 
one, and so I have stopped talking about them.

If you want to achieve consensus, you have to come closer to the rest of 
the group.

Of course, you may claim that this group is itself far removed from the 
real world, but I don't see much evidence of that.

> What are the objections (and BTW were to find described the consquences 
> for a Registry) to Adam and Simon positions?

It is too early to write a description of the consequences for the 
registries, since we haven't even reached a rough consensus on the 
changes to the specs.

Erik