IETF Logo Mail Archive

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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 01 June 2018 17:39 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 5A51E12D96B for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2018 10:39:35 -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 NLe1nF-b3NPR for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2018 10:39:33 -0700 (PDT)
Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (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 5C9CF12DA02 for <ietf@ietf.org>; Fri, 1 Jun 2018 10:39:33 -0700 (PDT)
Received: by mail-yb0-x22c.google.com with SMTP id x6-v6so809322ybl.12 for <ietf@ietf.org>; Fri, 01 Jun 2018 10:39:33 -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=VURRtZO9ZWEMwH9OSfWKwcVGr22Cnd272u2mQlzxCH8=; b=HrHaJOs2Jm3zyiUmevR8UxIqsQW/r3yRASq0DmEBq1L1X/35W6M3vHCuxgE317Niio YkFHG2Uh3RuUpyGBlkXPTpJsdjvMdTh12Z6p5/dDk2ECJB6aow38VU5MCt/pb5Oj3kUI RIMl33V8EhZcEyUs8IXN6DxZH1odUvoC5/lcJ4ugMkuLHAtK4AiKm/BuxXVY3D4Wqd5T JyDbUEJuXE0BItsjqchuIDjeh0dwpsLwymrit0gYbFYGEItqNro9t7gYFn87lInD9dk8 bVoCSYAAV1EgOt8xfhJE7InGoCsshyxPLMnNghM3l7lr0Bj31zA4gLIWUpb1Bs8etxQL /6yg==
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=VURRtZO9ZWEMwH9OSfWKwcVGr22Cnd272u2mQlzxCH8=; b=ZbxMKybUbjVU8fzVC0E4LyKT8wr9dlWdtXQyqs4kLI+aq3WRr/ScuQnBP6uF+CPAzf psbwv/njcmEhb+V9qb1U/GnW7PKxAH6ilmJU7f5eB1F0Y/M/aoOyYpSbPZ24nVGXNiG3 DQ+99SLnGCjKwS9NfDRtZwi9PTTG4dD/7zSUAnekXsAQKFPYDb44ww06eH0V5QhA+wgI zdDdF84FSXRaXV9GtPtq5MQeL691nAHJfnb/KFzup2812ucvLPegcG1NSGYQIzGnxnuD B+zZ1xfJaVQk3b8q+m4W00rjavaxBrZlgG/UBmOrf+5s+GwB0fGSxvtnePSj9Koa6l5N FkYQ==
X-Gm-Message-State: APt69E0TyjC26Ca/m9H/bmFXSX/Ik1B5aByWjI/FLxjXY6DLHceJt1Cu N6jdVw/qffcqgCEAwtbDDgmzWS14B25yBqIkEiw=
X-Google-Smtp-Source: ADUXVKIGrzphhBqDa6Bz9lwoVpUv04sFIXzhLx0Tgq75GsiTtpcE1SpRhZZgrJEjhiQUkOe6QjjDGkd/G8QzgGAJBfU=
X-Received: by 2002:a25:a2d0:: with SMTP id c16-v6mr3305236ybn.235.1527874772445; Fri, 01 Jun 2018 10:39:32 -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>
In-Reply-To: <712a0de5-dd4e-9fa7-4cfd-fc7a80144805@mozilla.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 01 Jun 2018 12:39:19 -0500
Message-ID: <CAKKJt-ft1w-OY5otdD+3JdF+JRbEZvYkLAUXbT1OFJ30_FkHDA@mail.gmail.com>
Subject: Re: Possible BofF question -- I18n (was: Re: Possible OBF question -- I18n)
To: Peter Saint-Andre <stpeter@mozilla.com>
Cc: John Levine <johnl@taugh.com>, IETF list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000012ae06056d98110c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FY2ERvZ9n6-4NKywTa0kfaYr4Ik>
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 17:39:36 -0000

FWIW ...

On Fri, Jun 1, 2018 at 11:43 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.
>
> >  It'd be OK if IESG review were to flag drafts and
> > ask whether they should say something about I18N.
>

This does happen now during IESG Evaluation. I believe Alexey is the most
likely AD to ask about i18n, but other ADs also ask, even ADs outside ART.

We typically don't see each other's AD Evaluations, so I don't know what
happens before IESG Evaluation.


> We might want authors to think about internationalization before IESG
> review.
>

Yes, please do.

There are very few things that the IESG wants to be the first people to
think about, and especially not when balloting on a document!

Spencer, speaking as 1/15th of the balloting IESG, most telechats

v2.23.0 | Report a Bug | By Email