Re: Possible BofF question -- I18n (was: Re: Possible OBF question -- I18n)

Nico Williams <nico@cryptonector.com> Sat, 02 June 2018 00: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 C22BF12420B for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2018 17:13:45 -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 qRe_hOPQLgaY for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2018 17:13:44 -0700 (PDT)
Received: from homiemail-a86.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 ADF78120047 for <ietf@ietf.org>; Fri, 1 Jun 2018 17:13:44 -0700 (PDT)
Received: from homiemail-a86.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTP id 63E37900012A; Fri, 1 Jun 2018 17:13:42 -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=ypKh2yy4KXgu4h CAt1XeO7njXzQ=; b=y4qnfothlAy+VjeeiIrwnq1NvZhrSiYR44Bda2v+AJAU2c E3zCWNcv+GP7fBdppslrZqISj9Uq5RUV19FPbA5BKxV2JwNtvpWzNjNTGQpTUUB1 n8gYH/RTVhtPl7abCLdDhVSV764mQuc2uMxkCncGE4qghFHAVJrmOlaY8nfso=
Received: from localhost (unknown [12.31.71.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTPSA id 8FA879000106; Fri, 1 Jun 2018 17:13:40 -0700 (PDT)
Date: Fri, 01 Jun 2018 19:13:36 -0500
From: Nico Williams <nico@cryptonector.com>
To: Peter Saint-Andre <stpeter@mozilla.com>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, John Levine <johnl@taugh.com>, IETF list <ietf@ietf.org>
Subject: Re: Possible BofF question -- I18n (was: Re: Possible OBF question -- I18n)
Message-ID: <20180602001334.GK14446@localhost>
References: <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> <712a0de5-dd4e-9fa7-4cfd-fc7a80144805@mozilla.com> <CAK3OfOigxL6A1eX0ZDAezpKqcS=FAMAzZ3ULkz297qT8pCdzsQ@mail.gmail.com> <CAKKJt-f1Tc59ndnwo4PEXPMpp_SvM5OPWyCGqk9ypORKj0wtHQ@mail.gmail.com> <49910207-f473-50b1-ee44-21b7fe781eef@mozilla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <49910207-f473-50b1-ee44-21b7fe781eef@mozilla.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NRmWcMstwKKqLV3MDkjxRLPXMjI>
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: Sat, 02 Jun 2018 00:13:46 -0000

On Fri, Jun 01, 2018 at 02:48:31PM -0600, Peter Saint-Andre wrote:
> AFAIK we've never had an i18n directorate. Some ADs (Alexey is great at
> this) flag documents in IETF LC or IESG review that could use i18n help.
> Sometimes the authors reach out and ask for early review / assistance,
> either on their own or prodded by a WG chair or AD (this happens for
> many things outside of i18n, of course). Formalizing this has potential
> to improve outcomes without necessarily requiring an
> Internationalization Considerations section in every RFC (although IMHO
> we could include that during the I-D phase and remove it if there's
> nothing actionable, as we do for IANA considerations). However, as you
> note, there are plenty of protocols that don't include human-readable
> text so the i18n considerations would be a no-op.

Sure, +1 to that.

But it'd be best if authors (and WGs) had to think about I18N before
IESG review.

One good place to push I18N is at WG (re)charter time.  That's because
it might then be obvious whether or not any of the WGs work items will
have I18N issues.  For example, TCP/IP has no I18N issues.  But SSHv2
does, as do NFSv4, HTTP, and many others.  Generally the protocols
needing I18N help are application protocols.

Nico
--