IETF Logo Mail Archive

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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 31 May 2018 20:53 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 0FC6D131753 for <ietf@ietfa.amsl.com>; Thu, 31 May 2018 13:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 zj87owEmi835 for <ietf@ietfa.amsl.com>; Thu, 31 May 2018 13:53:47 -0700 (PDT)
Received: from mail-yb0-x22e.google.com (mail-yb0-x22e.google.com [IPv6:2607:f8b0:4002:c09::22e]) (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 9FDC612D9FF for <ietf@ietf.org>; Thu, 31 May 2018 13:53:47 -0700 (PDT)
Received: by mail-yb0-x22e.google.com with SMTP id o14-v6so8045007ybq.3 for <ietf@ietf.org>; Thu, 31 May 2018 13:53:47 -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=5mXGmY3SzQDdjJz8sHEPDKBfP2+7AcSGiWtDMcpFimg=; b=KoAydpqkWUzb9y6UFOAnHeEUbJgvrjKQ1MTJGw95z6Dj+1JI4Cu+2Tp1KS8ABl4Qy/ f8dHhL5bU3wcxWEwk3DuJzazrEU+HtOCooD0NLNcGEKouzmP85BGGnNrsoITMQ5TRBMf S3ktWDSxmEIh+sa6AfBJfjb5StMftO4PkNW4YV9XLZTvMKG++DYqSNsX0ZhEQdeR014I WifJo5XKXSPpZUTjG7yppdOIGGg04LeAByVavzVgAdPVf1nUHIRH5hBhITCQDeM12D3V HsdinYlzjNRUGge8iZQEaBbB88ZVna/PMuy1pbdT4GkmXF0PjzcLzV8y2bICtpSAsEaQ DP2w==
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=5mXGmY3SzQDdjJz8sHEPDKBfP2+7AcSGiWtDMcpFimg=; b=a5VKxICbQVxcqD3z9RWXeTt2QJr/wO50yDsdxB16y3fnRRZLy4SG8fcPTT6lt9m2e7 ZmKY1u1Z7Nu8nrOH3YXozKXNrPmsTbJZiMRqygJDHsTeaqez7LsD7iqLPjPl+5y43tGH SgrhGQHoblbq2wgSbpZ7uUnaxhNcCNOi/1RNh5jt1BT5zV6t6lVbuL6mLnlYlInu9yjP zk6fVrPRXV7Ay6cFnC14kMbsOtrmk8mrFbqLvPugnTFlQFDGw5xYm9KZjSfDvvFCTJzu gFAB13SKLeGZ3h+fKtLlDE3mehu9L9AMImIvjcNvvc0rp0dDy41SZ8Uad8gRbN/KqWOo uDRA==
X-Gm-Message-State: ALKqPwdd+teK99AtdJY6jBsQfkVCfzRVrfagx8jrj549bGnkWm9cpe5y Cj+DN/jdkCUPyRC2kQrlnHu6UZP5XgliseWA08E=
X-Google-Smtp-Source: ADUXVKJGB4MLx6GyNQqCdFRTh4So1cmSG/da/6H9Bj0niKLuvFqHN+FNPXqRulX71wxtGi1Utpd7mcQex/cWqSosz+w=
X-Received: by 2002:a25:ac9c:: with SMTP id x28-v6mr4738922ybi.44.1527800026583; Thu, 31 May 2018 13:53:46 -0700 (PDT)
MIME-Version: 1.0
References: <20180530231127.17198276FEE3@ary.qy> <071E6235FE7B088A2B56A238@PSB> <0093E2CD-670E-47B6-A286-4FDEB140FAD9@frobbit.se> <20180531172228.GF14446@localhost> <09C80180-B772-492A-A1A6-B04C4ECDE8C9@frobbit.se>
In-Reply-To: <09C80180-B772-492A-A1A6-B04C4ECDE8C9@frobbit.se>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 31 May 2018 15:53:34 -0500
Message-ID: <CAKKJt-f0OWUPeJYh=1-F+BiAC6GBxZu+Jid_doa7OibmRGB9jA@mail.gmail.com>
Subject: Re: Possible BofF question -- I18n (was: Re: Possible OBF question -- I18n)
To: Patrik Fältström <paf@frobbit.se>
Cc: Nico Williams <nico@cryptonector.com>, John C Klensin <john-ietf@jck.com>, John Levine <johnl@taugh.com>, IETF list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000df55cc056d86a91e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rbknSA0sTyusqzuxEomi33u-Xx8>
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: Thu, 31 May 2018 20:53:50 -0000

On Thu, May 31, 2018 at 2:34 PM Patrik Fältström <paf@frobbit.se> wrote:

> On 31 May 2018, at 19:22, Nico Williams wrote:
>
> > Certainly, in the context of Internet protocols, the IETF is the place
> to do I18N work.  Can there be any doubt?
>
> From my personal view, a crystal clear "NO" (part from coordination with
> W3C of course).
>
> But that is something I think IETF should ask itself and decide that is
> the case, and act accordingly.
>

I've read through this thread carefully enough to say that if a BOF
description in this space showed up in
https://trac.tools.ietf.org/bof/trac/wiki, I'd most likely encourage the
IESG to approve it.

I'm not ready to convince myself that this is a TSV BOF and I should
sponsor it, but we do have 13 ADs who aren't TSV ADs ...

Do the right thing.

Spencer

v2.23.0 | Report a Bug | By Email