IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Fri, 01 June 2018 04:03 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 50C16126DC2 for <ietf@ietfa.amsl.com>; Thu, 31 May 2018 21:03:42 -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 ge9IjIe86LID for <ietf@ietfa.amsl.com>; Thu, 31 May 2018 21:03:40 -0700 (PDT)
Received: from homiemail-a54.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 78E5A126CF6 for <ietf@ietf.org>; Thu, 31 May 2018 21:03:40 -0700 (PDT)
Received: from homiemail-a54.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTP id 134104800BB16; Thu, 31 May 2018 21:03:39 -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:content-transfer-encoding; s= cryptonector.com; bh=CDxDRWeWZDmZo4pu3r3k8iR479g=; b=Tye/qXaUMUb qZ+Au9CdI8ljf7vz73NqcxX8Rpd0Zj+2PFh+zJvuGMpLzhXrLKJ056atrAPHbm1c mO1yM90Qw2mmiX4Uay3RSk67ObfBg9skNkC0E1ZcJX7g2Wp84p36wqHGdXJ3D20Y 6/68/ijEAf685RTdP/cEDaeJmMRsaQ70=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTPSA id A2D5A4800BB15; Thu, 31 May 2018 21:03:38 -0700 (PDT)
Date: Thu, 31 May 2018 23:03:36 -0500
From: Nico Williams <nico@cryptonector.com>
To: Patrik Fältström <paf@frobbit.se>
Cc: John C Klensin <john-ietf@jck.com>, John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: Possible BofF question -- I18n (was: Re: Possible OBF question -- I18n)
Message-ID: <20180601040335.GG14446@localhost>
References: <20180530231127.17198276FEE3@ary.qy> <071E6235FE7B088A2B56A238@PSB> <0093E2CD-670E-47B6-A286-4FDEB140FAD9@frobbit.se> <20180531172228.GF14446@localhost> <09C80180-B772-492A-A1A6-B04C4ECDE8C9@frobbit.se>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
In-Reply-To: <09C80180-B772-492A-A1A6-B04C4ECDE8C9@frobbit.se>
User-Agent: Mutt/1.5.24 (2015-08-30)
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H46mbEJhocBJ73ZNc-fdk5vEhMk>
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 04:03:42 -0000

On Thu, May 31, 2018 at 09:31:45PM +0200, Patrik Fältström 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. Whatever that means. If I knew, I
> would say...

Who else will do I18N work on Internet protocols?  Either we give them
to other SDOs or we do the work.

Nico
--

v2.23.0 | Report a Bug | By Email