Re: [Gen-art] LC review: draft-ietf-idnabis-bidi-06.txt

Harald Alvestrand <harald@alvestrand.no> Wed, 06 January 2010 13:58 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: idna-update@alvestrand.no
Delivered-To: idna-update@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id EE53B39E255; Wed, 6 Jan 2010 14:58:32 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qe9OLXnugE2H; Wed, 6 Jan 2010 14:58:32 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 08C1939E165; Wed, 6 Jan 2010 14:58:32 +0100 (CET)
Message-ID: <4B449721.5040800@alvestrand.no>
Date: Wed, 06 Jan 2010 14:58:57 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
Subject: Re: [Gen-art] LC review: draft-ietf-idnabis-bidi-06.txt
References: <200910052014.n95KEaw08697@birdie.sybase.com> <9FA605F57343CEF5EFABE247@PST.JCK.COM> <E98EDF5B-8AB4-4828-B4FE-2C7F9D5B9642@google.com> <7244A8D31696F4C508337CDF@PST.JCK.COM> <0A140D60-175C-4C0A-A9F8-61149443DE60@google.com> <4ACB0A60.5000608@it.aoyama.ac.jp> <9D15BAAF-8A34-43DC-9D1D-31EC0FFEA574@google.com> <E273732873CBDA2E83A98E88@PST.JCK.COM>
In-Reply-To: <E273732873CBDA2E83A98E88@PST.JCK.COM>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: erikv@google.com, "\"Martin J. Dürs", idna-update@alvestrand.no, Kenneth Whistler <kenw@sybase.com>, "t\"" <duerst@it.aoyama.ac.jp>, Vint Cerf <vint@google.com>
X-BeenThere: idna-update@alvestrand.no
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IDNA update work <idna-update.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=unsubscribe>
List-Archive: <http://www.alvestrand.no/pipermail/idna-update>
List-Post: <mailto:idna-update@alvestrand.no>
List-Help: <mailto:idna-update-request@alvestrand.no?subject=help>
List-Subscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2010 13:58:33 -0000

John C Klensin wrote:
> --On Tuesday, October 06, 2009 07:07 -0400 Vint Cerf
> <vint@google.com> wrote:
>
>   
>> Martin,
>>
>> in that case, let's see whether we have consensus around
>> simply explaining
>> that not all CS are permitted by BiDi and that both tables and
>> bidi rules are needed
>> to implement IDNA2008 as intended.
>>     
>
> To keep this in perspective, there are several other categories
> in the lists in Bidi from which only a very small number of
> characters are permitted by Tables.    In the case of CS, the
> "small number" is zero but, unless the readers understand that
> they need to go to Tables for specific permitted character
> information, they might be equally confused.
>
> So, IMO, the correct statement is something like "not all
> characters from the listed categories are permitted by BiDi
> and... as intended".    I don't think CS is special in that
> regard.
>   
I am now integrating changes suggested during Last Call review so that a 
new version can be emitted as soon as the IESG says "no other issues".

In response to this issue, I have added the following statement to the 
introduction:

The other normative documents in the IDNA2008 document
set establish criteria for valid labels, including listing the permitted
characters. This document establishes
additional validity criteria for labels in scripts normally written
from right to left.

I think that's what the document was saying all along, but it doesn't 
hurt to be over-explicit, especially given the reactions to "CS" that 
we've seen on the list.

Is that clear enough?
>     john
>
>
>
>
> _______________________________________________
> Idna-update mailing list
> Idna-update@alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update
>
>