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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 01 June 2018 20:16 UTC

Return-Path: <spencerdawkins.ietf@gmail.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 AD9F312D94A for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2018 13:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qvOY39ZVPT0d for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2018 13:16:56 -0700 (PDT)
Received: from mail-yb0-x22a.google.com (mail-yb0-x22a.google.com [IPv6:2607:f8b0:4002:c09::22a]) (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 65BF01205F0 for <ietf@ietf.org>; Fri, 1 Jun 2018 13:16:56 -0700 (PDT)
Received: by mail-yb0-x22a.google.com with SMTP id m137-v6so6819845ybm.6 for <ietf@ietf.org>; Fri, 01 Jun 2018 13:16:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=meR+LPAPr3EdBdmOqs4R8BTIAh2aYbLsl3fzEYPKB4Y=; b=MmpTDZi7ZONoDxJADY4BXkbdIr8nCdRe3otqpo1iURXTf1k6NNnrwMEq/XEs9GCIdy Ei8fDDw0CWHZsnllAFmSZ+wdrXp9hdbCf9IrZsbDr4APQOOM21+ciXdlTFY7ooiDgguc knZtmlM4RMgkHqSYljJAnrzKOToaFme5RxeJnDbZBovv3mP6QBE7wDB7SlGSFwgfcCpp nakNL/DTzjKYSUDy/qDQBgsLWiPuLyVg+DOwFrRR9KjNjdCXF+vBBfSm7q5i5ppLuw8+ FQiTkvxfO5BavrGZkQv4BAttW+dZSZgc4bgYh5+o2kuNik9mwyVBbh+SZ6KX+YryIQIB umkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=meR+LPAPr3EdBdmOqs4R8BTIAh2aYbLsl3fzEYPKB4Y=; b=jj+Z4ZBj77l59dfMTC7epmw8A0+wtwZnrk2t7h/kJCujz5zA2X1Bxaie6KyjYmKpIS wLOyMn3r04uWMAAttm7RIq+jxUNq3pLgOUo9dVRwyCMfh8EKixppZXLDnGV6+ruwSRke 6hNND28lgqPFBs9T1hzls+W5bN0c4BdyDpgHlDM1pL6TGh7vWNopl7p2GWYQQxiDDCcm QF+4ud73YLFnwPGZDtjLrYCTDzqsGFlWxn/WWjIZHhEhnZ4ff0O+9lfdzeCuzY0gun9F 5DVW+IXH/hG7akaGVxnQ0+CjoD4V/DwS/CT+i1WavQGAZKCq697fvV4zio1rnwXGWBGn 1aWQ==
X-Gm-Message-State: ALKqPwd+JR6xKQxlNc+fiQBr/F/PXgyxSDf7PhrBLkV8Rxiu1JHWRpn+ QV2FeL2MmEnK9Nw1asN8T5HvIMEBY3JwUAkTmyWPqA==
X-Google-Smtp-Source: ADUXVKIGb8wMOA6lrdLzzZyiYRGigXfKd+d4OGXv7H/yyq/9swGuvHNC6lpmZ42cdBCCgQKwm+e2Kku6Mfx7Oen/zVM=
X-Received: by 2002:a25:9083:: with SMTP id t3-v6mr6808761ybl.71.1527884215285; Fri, 01 Jun 2018 13:16:55 -0700 (PDT)
MIME-Version: 1.0
References: <20180530231127.17198276FEE3@ary.qy> <071E6235FE7B088A2B56A238@PSB> <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> <712a0de5-dd4e-9fa7-4cfd-fc7a80144805@mozilla.com> <CAK3OfOigxL6A1eX0ZDAezpKqcS=FAMAzZ3ULkz297qT8pCdzsQ@mail.gmail.com>
In-Reply-To: <CAK3OfOigxL6A1eX0ZDAezpKqcS=FAMAzZ3ULkz297qT8pCdzsQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 01 Jun 2018 15:16:42 -0500
Message-ID: <CAKKJt-f1Tc59ndnwo4PEXPMpp_SvM5OPWyCGqk9ypORKj0wtHQ@mail.gmail.com>
Subject: Re: Possible BofF question -- I18n (was: Re: Possible OBF question -- I18n)
To: Nico Williams <nico@cryptonector.com>
Cc: Peter Saint-Andre <stpeter@mozilla.com>, John Levine <johnl@taugh.com>, IETF list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e8fde7056d9a43f5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YTiozQ3MjBVRk2X30b9ZRX03pxA>
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: Fri, 01 Jun 2018 20:16:59 -0000

I'm confused about something here.

On Fri, Jun 1, 2018 at 1:33 PM Nico Williams <nico@cryptonector.com> wrote:

> On Fri, Jun 1, 2018 at 11:42 AM Peter Saint-Andre <stpeter@mozilla.com>
> wrote:
>
>> On 6/1/18 10:27 AM, John R Levine wrote:
>> > On Fri, 1 Jun 2018, Peter Saint-Andre wrote:
>> >>> Require that documents have I18N Considerations sections, require
>> review
>> >>> by an I18N directorate, and you'll see how quickly participants who
>> used
>> >>> to not give a damn about I18 will come around, learn what they have
>> to,
>> >>> and get their I18N work done.  Suddenly the I18N directorate will be
>> in
>> >>> demand.
>> >>
>> >> This is worth considering...
>> >
>> > I don't think it's a very good idea.  It'll just lead to useless
>> > pro-forma language.
>>
>> Quite possibly.
>
>
> We have the IESG and directorates to make sure these sections are not pro
> forma.
>

I'm not seeing an obvious directorate that would review docs for i18n
considerations at https://datatracker.ietf.org/dir/.

To be fair, that's the list of active directorates, but searching for "ietf
internationalization directorate review" didn't turn up an obvious closed
directory.

What I do know, is that the IAB had an Internationalization program, but
that concluded in March 2017, and IAB programs don't have any particular
role in document approval beyond program members (who may or may not be IAB
members) responding to Last Call announcements as individuals. Details at
https://www.iab.org/activities/programs/concluded-programs/internationalization-program/
.

Transport guys don't internationalize a lot, because most of our headers
aren't intended for human consumption, and it's very possible that I'm
missing something - so, I'm just trying to stay synchronized with this
important conversation.

Thanks,