Re: [I18nrp] editorial comments on draft-faltstrom-unicode11-04.txt
John C Klensin <john-ietf@jck.com> Thu, 11 October 2018 01:15 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id E9D47130DEA;
Wed, 10 Oct 2018 18:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001]
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 yywl9sQnBIS9; Wed, 10 Oct 2018 18:15:47 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.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 82EF7130DDC;
Wed, 10 Oct 2018 18:15:47 -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 1gAPZn-0003eo-Nr; Wed, 10 Oct 2018 21:15:43 -0400
Date: Wed, 10 Oct 2018 21:15:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Gabriel Montenegro <g.e.montenegro@hotmail.com>
cc: paf@netnod.se, art@ietf.org, i18nrp@ietf.org, iab@iab.org
Message-ID: <A83D675604CE3DCFE1378DD2@PSB>
In-Reply-To: <YQBPR0101MB152313406359D7FECFFA3F00C1E00@YQBPR0101MB1523.CANPRD01.PROD.OUTLOOK.COM>
References: <YQBPR0101MB152313406359D7FECFFA3F00C1E00@YQBPR0101MB1523.CANPRD01.PROD.OUTLOOK.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/i18nrp/fnaTRIxiriquERE7Xgsrfk-xFro>
Subject: Re: [I18nrp] editorial comments on draft-faltstrom-unicode11-04.txt
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>,
<mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>,
<mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 01:15:49 -0000
I assume Patrik has not answered because, being sensible, he is likely sleeping. In the interest of saving a bit of time, I've responded to the more substantive of your comments/questions below... --On Wednesday, October 10, 2018 19:12 +0000 Gabriel Montenegro <g.e.montenegro@hotmail.com> wrote: >... > Points out that IDNA2008 "is specified in a series of > documents (see Section Section 3.1). " That still leaves > unanswered what a reasonable overview is for those of us who > are absolute IDNA newbs. So may I suggest something like "is > specified in a series of documents (see Section Section 3.1), > but for an overview see XXXX." [I suppose rfc5894 is the > proper overview doc here?] Almost. You will find that RFC 5894 is hard or impossible to understand without some of the material in 5890, which I would recommend at least looking through first. The combination is still not a tutorial. There are several of those around, but, unfortunately, a large fraction of them contain serious errors or are, however unintentionally, a little misleading. Some day, some of us will have time. >... > Can't parse: "that registry operators to based on the IDNA2008 > specification create additional rules...". Perhaps you meant > "that led registry operators to (based on the IDNA2008 > specification) create additional rules..."? You might find part of the note I posted earlier today (about the same time as yours) helpful in regard to what is going on in that section (although I agree that the current text in the I-D needs work). best, john
- [I18nrp] editorial comments on draft-faltstrom-un… Gabriel Montenegro
- Re: [I18nrp] editorial comments on draft-faltstro… John C Klensin
- Re: [I18nrp] editorial comments on draft-faltstro… Patrik Fältström