IETF Logo Mail Archive

Re: Possible BofF question -- I18n

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 01 June 2018 04:39 UTC

Return-Path: <brian.e.carpenter@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 029DE126DEE for <ietf@ietfa.amsl.com>; Thu, 31 May 2018 21:39:52 -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, FREEMAIL_FROM=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 OcjvQlvwekLJ for <ietf@ietfa.amsl.com>; Thu, 31 May 2018 21:39:50 -0700 (PDT)
Received: from mail-pl0-x230.google.com (mail-pl0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) (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 1ED37126C0F for <ietf@ietf.org>; Thu, 31 May 2018 21:39:50 -0700 (PDT)
Received: by mail-pl0-x230.google.com with SMTP id c11-v6so14556114plr.5 for <ietf@ietf.org>; Thu, 31 May 2018 21:39:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=RTQhKQDFarbluALSAayMshCESsG0/Z3VQrhSIQG+TbA=; b=LIVIt+bnHQelp89pwDsa911OaW+0Df7VMN9YDdJIPdHog95KyBaODEe2+wKCZEG2m5 wZlKauHpPwRXcTXQi5xV1Uys3c/f+zer4LwBB2ugJN3y40VdtEBDXwKEelIXwCuuwCTb t5niBUEd0McYi5qgd6M0dQGN/M6BUogmABWx7hWTh1ct0MBDwDH5et0g5ADHkbZiF8kg knXUvU6lu+2pFonqdnnmzsaos9jH2SvS9hf/JOC085CsStdUW0YJdOPUd1zN4SRP8bIR 9h21nbP4hiknuyRr4pyIso7LQQYmozRVQjRO0bM0xZJCmcOX6oaIhnRZAy+OFpXjk2Nk /98A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=RTQhKQDFarbluALSAayMshCESsG0/Z3VQrhSIQG+TbA=; b=Hi/8bbUMICtunYl455Fpc9MDzz3jzjuQI6kDPDFIdxb059fDsYFH0S/DRzg1VBs3px W1AY42ZEO59v+gNasKO+RqViEB3aJFuyXArqNsPquzDSiA3BPqfzLpgabfsn7KlKV0mR iF/Pw1nB+uDOqqrSKr9W/YBUT+6oHdxok5T6YkPZUYUJ77GUMlmSob09L3ptywHTeH2h ljR/AsQgHSllnwdZRACl1u67BToMgQmLV6Zcnwx3LriqD52zTN86zzlexpcZVAsXY9ht tQcnq/iOzXabLLJjV3LCUgRMksCgq3RVZ22Y4b8bbqtUUZ/gJYuhew75pyEjmppq0ChE fJWw==
X-Gm-Message-State: ALKqPwfNjyzmuGsqkyzy4iljd05gXIpIDvWfdvJDLS5Ga22nBS8afJQt 2IPUWaTbFVuBU1VrfZ1xiG/kcA==
X-Google-Smtp-Source: ADUXVKLzXuCB8Lio4oubIEUAPPCLtypEkxMF9ZOJrq5kYQA8qwYgjGV/VOmusLVK2SP/eEE0T7eoQw==
X-Received: by 2002:a17:902:28ab:: with SMTP id f40-v6mr9692464plb.208.1527827989443; Thu, 31 May 2018 21:39:49 -0700 (PDT)
Received: from [192.168.178.21] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id c8-v6sm17605246pgu.19.2018.05.31.21.39.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 May 2018 21:39:48 -0700 (PDT)
Subject: Re: Possible BofF question -- I18n
To: Nico Williams <nico@cryptonector.com>, Patrik Fältstr öm <paf@frobbit.se>
Cc: John C Klensin <john-ietf@jck.com>, John Levine <johnl@taugh.com>, ietf@ietf.org
References: <20180530231127.17198276FEE3@ary.qy> <071E6235FE7B088A2B56A238@PSB> <0093E2CD-670E-47B6-A286-4FDEB140FAD9@frobbit.se> <20180531172228.GF14446@localhost> <09C80180-B772-492A-A1A6-B04C4ECDE8C9@frobbit.se> <20180601040335.GG14446@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <aba54f94-4d12-191e-39cf-e96805f3fe63@gmail.com>
Date: Fri, 01 Jun 2018 16:39:53 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <20180601040335.GG14446@localhost>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_c13kHTDRqd0w2atnFq0iQyJLs0>
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:39:52 -0000

As an ignoramus on these matters, I've been keeping quiet, but...
On 01/06/2018 16:03, Nico Williams wrote:
> 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).

I really don't understand how that can be true for protocols that
are developed or maintained in the IETF, that are of no interest to
the W3C, and require some sensible handling of I18N issues. To my mind
that certainly includes any protocol that involves text strings of
interest to humans, including names of interest to humans.

>> 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.

Exactly. And the PRECIS work made it clear to me that a simple sprinkling
of pixie dust is not enough. I think John is quite right to ring the alarm
bell.

We did a tutorial 8 IETFs ago:
https://www.ietf.org/about/participate/tutorials/technical/precis-i18n/

Since then?

    Brian

v2.23.0 | Report a Bug | By Email