Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-04

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 07 June 2011 21:43 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D87C11E819F; Tue, 7 Jun 2011 14:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.382
X-Spam-Level:
X-Spam-Status: No, score=-102.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pZaeGIemDXVW; Tue, 7 Jun 2011 14:43:54 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3A58E11E8071; Tue, 7 Jun 2011 14:43:53 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p57LhjP3013927 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2011 14:43:45 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
Date: Tue, 07 Jun 2011 14:43:46 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
To: rontlv <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 21:43:55 -0000

On Jun 7, 2011, at 3:56 AM, rontlv wrote:

> The IANA registry is in
> http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml#idnabis-ta
> bles-properties
> I saw that in the beginning it has as reference RFC 5892 for the whole
> table. Will it stay this way after the change proposed in this draft and
> just the three individual values will change based on 1.1, 1.2 and 1.3? or
> are there no changes in the IANA registry at all. This is unclear to me
> according to the section 3 of your draft.
> 
> Section 5.1 of RFC5892 says "If non-backward-compatible changes or other
> problems arise during the
>   creation or designated expert review of the table of derived property
>   values, they should be flagged for the IESG." . My question was if the
> change is backward compatible. The 5892bis draft does not say it.

Ah, very good catch! My earlier comment about us listing this new RFC in the registry is, in fact, wrong.

When we wrote RFC 5892, we said:
   IANA has created a registry with the derived properties for the
   versions of Unicode released after (and including) version 5.2.  
That's one registry that has the properties for most current version of Unicode at any given time. Thus, the registry would be updated *even if* we didn't publish 5892bis. We are not updating either 5892, nor the registry, by publishing 5892bis. We are simply giving IETF consensus advice about what we think the expert reviewer who updates the registry should consider.

Our IANA considerations in 5892bis are:
   IANA is to update the derived property value registry according to
   RFC 5892 and property values as defined in The Unicode Standard
   version 6.0.
That might sound like they are initiating the registry update, but they really aren't: the update was already specified in 5892. We can change the IANA considerations to reflect that:
   IANA will update the derived property value registry according to
   RFC 5892 and property values as defined in The Unicode Standard
   version 6.0, regardless of the content of this RFC.

--Paul Hoffman