Re: [I18ndir] Getting restarted and triage
John C Klensin <john-ietf@jck.com> Sat, 22 June 2019 05:36 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6310F12014E for <i18ndir@ietfa.amsl.com>; Fri, 21 Jun 2019 22:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5iRIm-Wp_b04 for <i18ndir@ietfa.amsl.com>; Fri, 21 Jun 2019 22:36:52 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65BCE12011F for <i18ndir@ietf.org>; Fri, 21 Jun 2019 22:36:52 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1heYhm-000EDL-2Z; Sat, 22 Jun 2019 01:36:50 -0400
Date: Sat, 22 Jun 2019 01:36:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Asmus Freytag <asmusf@ix.netcom.com>, i18ndir@ietf.org
Message-ID: <669C21A4FB5D51B515AEB66F@PSB>
In-Reply-To: <caa4c371-4199-17d9-a005-2ba1ca4f6a4b@ix.netcom.com>
References: <20190621224209.5A2B820162CB0E@ary.qy> <AF49257619901A2694737684@PSB> <caa4c371-4199-17d9-a005-2ba1ca4f6a4b@ix.netcom.com>
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
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/3Ec8qcAR18oaYdPD9a1DDFFgFBQ>
Subject: Re: [I18ndir] Getting restarted and triage
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jun 2019 05:36:54 -0000
--On Friday, June 21, 2019 19:34 -0700 Asmus Freytag <asmusf@ix.netcom.com> wrote: > John, > > some of us don't have the time to thrash to death things like > Patrik's draft over minute issues, like whether to consider > the single DISALLOWED character for Unicode 12.1 a technical > omission. Which absolutely no one, AFAICT, but especially not either Patrik or myself, has suggested. In more abbreviated form which I thought would be clear to everyone here, but let me spell it out a little more, all I have said about 12.1 is that (i) there are no changed in property values compared to 12.0, (ii) there is only one new code point, and (iii) that code point behaves exactly the way IDNA2008 assumes/ believes it should, i.e., the grapheme (and, because it is a CJK code point, its approximate interpretation) can be constructed under 12.0 (and earlier) by a code point sequence and the next code point therefore decomposes under NFC. Conclusions (i) and (ii) are the algorithmic review; (iii) is the new code point review. So, nothing to be done about that code point and, other than maybe adjusting some terminology, nothing that isn't already in draft-faltstrom-unicode12-00. What does need to be adjusted -- and needs to be adjusted whether we include 12.1 or not -- is the discussion of the basis for making decision when they need to be made. That has nothing to do with the new code point. See Patrik's note. > > If we can't find ways to remove this artificial friction, we > won't see more vigorous involvement. > > Notably, such hyperfocus on minutiae of little practical > impact is absent from successful projects in the i18n arena. If I understand what you are concerned about -- and, given that I believe that your complaint above is about a strawman that was not even in sight, I may not -- let me review why this (both my note and Patrik's) is important given the design of IDNA2008. As we know from IDNA2003 and the Unicode Standard itself, it is possible to define how to handle code points in a variety of contexts by simply making a list of all of the code point in Unicode and assigning properties (and, implicitly, appropriateness in various contexts, to each. The IETF concluded that choice was inappropriate for IDNs and IDN labels and that the best alternative (or, if you prefer, the least-bad one) was to construct a system based on a series of rules and an algorithm, one that had provisions for differences in short-string, language-independent, requirements of the DNS and requirements that are more typical of the broad range of Unicode applicability. Maybe that was the wrong decision or just one that was hopelessly naive and we should un-do it, but I've seen no proposal to do that and how to do so. If we are to stay with it, the algorithms and surrounding rule sets much be orderly and stay that way, and that --and, again, not any single code point in 12.1 or otherwise-- is what this is about. best, john
- [I18ndir] Getting restarted and triage Pete Resnick
- Re: [I18ndir] Getting restarted and triage John C Klensin
- Re: [I18ndir] Getting restarted and triage Marc Blanchet
- Re: [I18ndir] Getting restarted and triage John C Klensin
- Re: [I18ndir] Getting restarted and triage Asmus Freytag
- Re: [I18ndir] Getting restarted and triage John C Klensin
- Re: [I18ndir] Getting restarted and triage Asmus Freytag (c)
- Re: [I18ndir] Getting restarted and triage Patrik Fältström
- Re: [I18ndir] Getting restarted and triage Marc Blanchet
- Re: [I18ndir] Getting restarted and triage Pete Resnick
- Re: [I18ndir] Getting restarted and triage Barry Leiba
- Re: [I18ndir] Getting restarted and triage John C Klensin
- Re: [I18ndir] Getting restarted and triage John Levine
- [I18ndir] draft-faltstrom-unicode12 (was: Re: Get… John C Klensin
- Re: [I18ndir] Getting restarted and triage John C Klensin
- Re: [I18ndir] draft-faltstrom-unicode12 (was: Re:… Patrik Fältström
- Re: [I18ndir] Getting restarted and triage Asmus Freytag
- Re: [I18ndir] draft-faltstrom-unicode12 (was: Re:… John C Klensin
- Re: [I18ndir] Getting restarted and triage John C Klensin
- Re: [I18ndir] draft-faltstrom-unicode12 Asmus Freytag
- Re: [I18ndir] Getting restarted and triage John R Levine
- [I18ndir] Civility (Was: Getting restarted and tr… Pete Resnick
- Re: [I18ndir] Getting restarted and triage John C Klensin
- Re: [I18ndir] Getting restarted and triage Asmus Freytag (c)