Re: Gen-ART LC review of draft-faltstrom-5892bis-04
John C Klensin <john-ietf@jck.com> Wed, 08 June 2011 01:24 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E732B11E8154; Tue, 7 Jun 2011 18:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 4t287JLDcAfZ; Tue, 7 Jun 2011 18:24:25 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 2703B11E80FE; Tue, 7 Jun 2011 18:24:25 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QU7VI-0003I2-K4; Tue, 07 Jun 2011 21:24:16 -0400
Date: Tue, 07 Jun 2011 21:24:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, rontlv <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
Message-ID: <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM>
In-Reply-To: <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> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 01:24:26 -0000
--On Tuesday, June 07, 2011 14:43 -0700 Paul Hoffman <paul.hoffman@vpnc.org> wrote: >> 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, I think this is an improvement but there is one issue about which we have slightly different impressions. I hope the difference can be resolved without needing yet more tedious arguments about documentation. Indeed, if such arguments are required, I'd prefer that we just forget about it. Anyway, your comments above about "most current version" imply to me that IANA should keep derived property tables for the most current version only. My expectation when 5982 was completed was that IANA was expected to keep derived property tables, clearly identified by version, for each and every Unicode version from 5.2 forward. In other words, the tables for the [most] current version would be added to, not replace, whatever previous version tables were around. The reasons for this, in terms of systems and implementations in various stages of development, implementation, and deployment, seem obvious... but maybe it was too obvious to some of us at the time to get the wording exactly right. john
- Gen-ART LC review of draft-faltstrom-5892bis-04 Roni Even
- Re: Gen-ART LC review of draft-faltstrom-5892bis-… Paul Hoffman
- RE: Gen-ART LC review of draft-faltstrom-5892bis-… rontlv
- Re: Gen-ART LC review of draft-faltstrom-5892bis-… Paul Hoffman
- RE: Gen-ART LC review of draft-faltstrom-5892bis-… rontlv
- Re: Gen-ART LC review of draft-faltstrom-5892bis-… Paul Hoffman
- Re: Gen-ART LC review of draft-faltstrom-5892bis-… John C Klensin
- Re: Gen-ART LC review of draft-faltstrom-5892bis-… Paul Hoffman
- Re: Gen-ART LC review of draft-faltstrom-5892bis-… Alexey Melnikov
- Re: Gen-ART LC review of draft-faltstrom-5892bis-… Alexey Melnikov
- Re: Gen-ART LC review of draft-faltstrom-5892bis-… John C Klensin
- Contents of the IDNA Derived Properties registry … John C Klensin
- Re: Contents of the IDNA Derived Properties regis… Russ Housley
- Re: Gen-ART LC review of draft-faltstrom-5892bis-… Vint Cerf