Re: [I18nrp] Additional input needed for i18nRP BOF

Adam Roach <adam@nostrum.com> Wed, 13 June 2018 21:59 UTC

Return-Path: <adam@nostrum.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 32474130DDE for <i18nrp@ietfa.amsl.com>; Wed, 13 Jun 2018 14:59:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 ArlxF7RXt-Tg for <i18nrp@ietfa.amsl.com>; Wed, 13 Jun 2018 14:59:06 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8AC2130E96 for <i18nrp@ietf.org>; Wed, 13 Jun 2018 14:59:06 -0700 (PDT)
Received: from Orochi.local ([196.52.19.218]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w5DLx3CT023280 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 13 Jun 2018 16:59:04 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [196.52.19.218] claimed to be Orochi.local
To: John C Klensin <john-ietf@jck.com>
Cc: Nico Williams <nico@cryptonector.com>, Peter Saint-Andre <stpeter@mozilla.com>, i18nrp@ietf.org
References: <4DA478C4C99396556E1B3EF1@PSB> <a31e91ff-c78c-6a7c-fe8c-70b9563312f7@nostrum.com> <8774afa2-4d3f-bc08-69af-f88e229f547a@mozilla.com> <07356789-b93f-b1a2-21d6-bef704b7c0b0@nostrum.com> <a6b7bf5c-3f37-e97b-7e44-c9e648bdbcef@mozilla.com> <ba6339f3-eb5f-4d14-51fb-256d6682f37e@nostrum.com> <c6d2a8d7-301b-c017-34ac-44da954c0b46@mozilla.com> <20180607031752.GS14446@localhost> <20180607033006.GT14446@localhost> <cff5d71d-d47f-d8b2-4c93-41b2c0c603c5@nostrum.com> <20180607034752.GV14446@localhost> <AE5C30EA35DC94399D43468E@PSB>
From: Adam Roach <adam@nostrum.com>
Message-ID: <68a10575-cd2a-243c-de51-c271d403fff2@nostrum.com>
Date: Wed, 13 Jun 2018 14:59:02 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <AE5C30EA35DC94399D43468E@PSB>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/4ASzBe73RraOzD_F0MB4sJ0Iy74>
Subject: Re: [I18nrp] Additional input needed for i18nRP BOF
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 13 Jun 2018 21:59:09 -0000

On 6/6/18 21:31, John C Klensin wrote:
> (2) It seems to me that, very crudely, there are two rather
> different types of documents of interest.   One, which seems to
> have been dominating the discussion, is a protocol or other spec
> for which i18n issues are incidental or only part of the story
> and that requires that they be checked for having been
> competently addressed.  The other is an actual i18n spec.  So,
> as an exercise for those designing solutions, consider
>     draft-klensin-idna-5892upd-unicode70
>     and
>     draft-klensin-idna-rfc5891bis
>
> and how the proposed solutions would work for them.

John --

After thinking through this issue a bit, I suspect the answer would look 
something like this:

Given the assertions that have been made about the likelihood of 
successfully creating a working group that would adopt and progress 
these documents, and given their nature, it seems that they would be 
reasonable candidates for AD sponsorship. In the context of the 
thumbnail sketch that has been building up on this list, I would expect 
that the sponsoring AD would work closely with the proposed i18n 
directorate to ensure that the proper level of review has taken place.

/a