Re: Possible BofF question -- I18n

Nico Williams <nico@cryptonector.com> Sun, 03 June 2018 06:13 UTC

Return-Path: <nico@cryptonector.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 55FA6126B6E for <ietf@ietfa.amsl.com>; Sat, 2 Jun 2018 23:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 GKeVyJScMKtt for <ietf@ietfa.amsl.com>; Sat, 2 Jun 2018 23:13:54 -0700 (PDT)
Received: from homiemail-a128.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 1A3941267BB for <ietf@ietf.org>; Sat, 2 Jun 2018 23:13:54 -0700 (PDT)
Received: from homiemail-a128.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a128.g.dreamhost.com (Postfix) with ESMTP id B554F30030404; Sat, 2 Jun 2018 23:13:53 -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=ryLKkq+BrZbuqC HX2CvUq6WgHvM=; b=qV9Fj/Lr2givK5IPPatl279gGxu5tGfAXXxHrDziqBNgXl cXjqX1XQDSCMrKRYu4jmyB4mWbvIBAftrcay4i0yFjNdkzWMongIFbGeU/RpHOl/ LXmUgSjw5krzUX7eGE1BvKXa/SJm6ASykbE+UHa7cLqAB0ysvscvPXsDmUSpQ=
Received: from localhost (50-232-84-66-static.hfc.comcastbusiness.net [50.232.84.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a128.g.dreamhost.com (Postfix) with ESMTPSA id 2045A30030403; Sat, 2 Jun 2018 23:13:52 -0700 (PDT)
Date: Sun, 03 Jun 2018 01:13:51 -0500
From: Nico Williams <nico@cryptonector.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
Subject: Re: Possible BofF question -- I18n
Message-ID: <20180603061350.GM14446@localhost>
References: <0093E2CD-670E-47B6-A286-4FDEB140FAD9@frobbit.se> <20180531172228.GF14446@localhost> <383c2404-7beb-63e9-b2b2-e75fd1b174f1@mozilla.com> <20180601041949.GH14446@localhost> <A13FFF23-49BD-459D-8B5B-D3448154EEBC@frobbit.se> <20180601151053.GI14446@localhost> <2584adb9-1622-8b49-7236-ecc7dd374974@mozilla.com> <alpine.OSX.2.21.1806011219340.7621@ary.qy> <CAK3OfOgv33SJiPJ6ypo8k5hcpnjcJdRso6EXb9b12YNcdDgMUg@mail.gmail.com> <6c5d5618-74a5-dcc8-d818-89243a41f307@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6c5d5618-74a5-dcc8-d818-89243a41f307@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u3m85dv2_J9o59VpyT6qCuRJMYU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 03 Jun 2018 06:13:56 -0000

On Sat, Jun 02, 2018 at 03:54:54PM +1200, Brian E Carpenter wrote:
> I'm an ignoramus, but:
> On 02/06/2018 05:59, Nico Williams wrote:
> ...
> > Not everyone can pick up I18N expertise  quickly?  Sure, but we engineer
> > complex things, so i suspect many participants at the IETF can actually
> > pick up enough I18N expertise to be useful. I18N is not a dark art.
> 
> If a dark art is one that involves combinatorial degrees of complexity
> mixed with human perception, judgment and emotion, then I fear that I18N
> *is* a dark art. We can perhaps manage such complexity by limiting the
> scope of what we try to do in our protocols, but I for one would very
> much appreciate having an I18N directorate reviewing everything.

I disagree.  It's not a black art.  There are some corners where
reasonable people can and will disagree (should emoji be allowed in
domainnames?), and there will be some cases that require script-specific
expertise, and therefore a lot of time to sort out.  But I18N is not a
dark art at all.  If it were, then how would we get anything done in
that space?  The E in IETF stands for Engineering, not Dark Art.