IETF Logo Mail Archive

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

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Thu, 07 January 2010 01:27 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 DA81739E1BD for <idna-update@alvestrand.no>; Thu, 7 Jan 2010 02:27:30 +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 bLdTPLXDYj3C for <idna-update@alvestrand.no>; Thu, 7 Jan 2010 02:27:27 +0100 (CET)
X-Greylist: from auto-whitelisted by SQLgrey-1.6.8
Received: from scmailgw02.scop.aoyama.ac.jp (scmailgw02.scop.aoyama.ac.jp [133.2.251.42]) by eikenes.alvestrand.no (Postfix) with ESMTPS id C6BDB39E3BD for <idna-update@alvestrand.no>; Thu, 7 Jan 2010 02:27:26 +0100 (CET)
Received: from scmse02.scbb.aoyama.ac.jp (scmse02.scbb.aoyama.ac.jp [133.2.253.159]) by scmailgw02.scop.aoyama.ac.jp (secret/secret) with SMTP id o071RlSr004822 for <idna-update@alvestrand.no>; Thu, 7 Jan 2010 10:27:47 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 674f_dca592fc_fb2b_11de_b7ad_001d096c5782; Thu, 07 Jan 2010 10:27:47 +0900
Received: from [IPv6:::1] ([133.2.210.1]:41537) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S12BE405> for <idna-update@alvestrand.no> from <duerst@it.aoyama.ac.jp>; Thu, 7 Jan 2010 10:27:45 +0900
Message-ID: <4B453891.2020105@it.aoyama.ac.jp>
Date: Thu, 07 Jan 2010 10:27:45 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1) Gecko/20090902 Eudora/3.0b3
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
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> <4B449721.5040800@alvestrand.no>
In-Reply-To: <4B449721.5040800@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: Vint Cerf <vint@google.com>, erikv@google.com, John C Klensin <klensin@jck.com>, Kenneth Whistler <kenw@sybase.com>, idna-update@alvestrand.no
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: Thu, 07 Jan 2010 01:27:31 -0000

Fine with me.   Regards,   Martin.

On 2010/01/06 22:58, Harald Alvestrand wrote:
> 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
>>
>
>

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

v2.23.0 | Report a Bug | By Email