Re: [I18nrp] Additional input needed for i18nRP BOF
Nico Williams <nico@cryptonector.com> Thu, 07 June 2018 03:44 UTC
Return-Path: <nico@cryptonector.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 39F1C130E2E
for <i18nrp@ietfa.amsl.com>; Wed, 6 Jun 2018 20:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001,
RCVD_IN_MSPIKE_H2=-0.795] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=cryptonector.com
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 qU28lgdDxUAv for <i18nrp@ietfa.amsl.com>;
Wed, 6 Jun 2018 20:44:54 -0700 (PDT)
Received: from homiemail-a27.g.dreamhost.com (homie-sub4.mail.dreamhost.com
[69.163.253.135])
(using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 9FE4E130E2A
for <i18nrp@ietf.org>; Wed, 6 Jun 2018 20:44:54 -0700 (PDT)
Received: from homiemail-a27.g.dreamhost.com (localhost [127.0.0.1])
by homiemail-a27.g.dreamhost.com (Postfix) with ESMTP id A0E78A009A84;
Wed, 6 Jun 2018 20:44:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date
:from:to:cc:subject:message-id:references:mime-version
:content-type:in-reply-to; s=cryptonector.com; bh=7QCJAVXkPtQHLV
AQ0/ZlB4uMZog=; b=QUZ9TLqH+GyjbwF2eW/kpxMmU8XJPKhRHPkeYW536tIpC7
kRp+qZymWG7UlaTv/uWrZ+QnQ5nHqarYf9gO+Z/zVRKous2gZB0c8t4A99fnHsEr
zFLFJIuVoiINyRrn73vP2hSq260mLqEMBVCCptDCkdDwKLkwiXjMzJvNQpSDQ=
Received: from localhost (unknown [8.2.105.17])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
(Authenticated sender: nico@cryptonector.com)
by homiemail-a27.g.dreamhost.com (Postfix) with ESMTPSA id C2658A009A82;
Wed, 6 Jun 2018 20:44:50 -0700 (PDT)
Date: Wed, 6 Jun 2018 22:44:48 -0500
From: Nico Williams <nico@cryptonector.com>
To: Adam Roach <adam@nostrum.com>
Cc: Peter Saint-Andre <stpeter@mozilla.com>,
John C Klensin <john-ietf@jck.com>, i18nrp@ietf.org
Message-ID: <20180607034447.GU14446@localhost>
References: <CE6F76BB323F1555D6B217A5@PSB>
<9ecf8b7a-d086-1c56-03fb-6773aed332c6@nostrum.com>
<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>
<20180607024527.GR14446@localhost>
<f1564b90-ef93-0fe9-382b-f06e79d879fe@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f1564b90-ef93-0fe9-382b-f06e79d879fe@nostrum.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/iOaQRo2t7Bws1N6kbpyj9kZX9DI>
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: Thu, 07 Jun 2018 03:44:57 -0000
On Wed, Jun 06, 2018 at 10:29:26PM -0500, Adam Roach wrote: > >Regardless of what the answer to that is, it might be possible to start > >small and scale up. Starting small means triaging more demurely. At > >any rate, starting small is probably the only realistic way to get > >started. But there's no point starting small if we can't scale up, so > >we do need to have some idea of how big to scale, and how. > > This sounds reasonable, and is pretty much what I had in mind when I said > "volunteers who are willing and able to educate themselves into being > experts". I say this while agreeing with John about the complexities and > subtleties of this topic. That's fair. Directorate members' I18N expertise might vary, with some better able to review email- or DNS-related I-Ds, and others better able to review filesystem- or web-related I-Ds. I18N is a fairly big topic, and I wouldn't expect every directorate member's expertise to be sufficient to review every comer. Also, John notes that reasonable people can and do disagree regarding various I18N issues, so we can probably expect some of that from the directorate. I hope directorate members can recognize and acknowledge which aspects are more objective and which more subjective. Still, I believe a lot of I18N issues are basic and can be dealt with objectively at this point, so a directorate should be helpful. Nico --
- Re: [I18nrp] Additional input needed for i18nRP B… John R. Levine
- Re: [I18nrp] Additional input needed for i18nRP B… John C Klensin
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- [I18nrp] Additional input needed for i18nRP BOF Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Eliot Lear (elear)
- Re: [I18nrp] Additional input needed for i18nRP B… John C Klensin
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… John C Klensin
- Re: [I18nrp] Additional input needed for i18nRP B… Brian E Carpenter
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Benjamin Kaduk
- Re: [I18nrp] Additional input needed for i18nRP B… John C Klensin
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… John C Klensin
- Re: [I18nrp] Additional input needed for i18nRP B… Nico Williams
- Re: [I18nrp] Additional input needed for i18nRP B… Nico Williams
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Nico Williams
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Nico Williams
- Re: [I18nrp] Additional input needed for i18nRP B… Nico Williams
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Larry Masinter
- Re: [I18nrp] Additional input needed for i18nRP B… Larry Masinter