IETF Logo Mail Archive

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

"Patrik Fältström " <paf@frobbit.se> Fri, 01 June 2018 15:13 UTC

Return-Path: <paf@frobbit.se>
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 F187D12D96D for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2018 08:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.622
X-Spam-Level:
X-Spam-Status: No, score=-1.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 cS2hY3eib2aX for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2018 08:13:57 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27A1A12D94B for <ietf@ietf.org>; Fri, 1 Jun 2018 08:13:57 -0700 (PDT)
Received: from [192.165.72.197] (unknown [192.165.72.197]) by mail.frobbit.se (Postfix) with ESMTPSA id ACD7B22E94; Fri, 1 Jun 2018 17:13:53 +0200 (CEST)
From: Patrik Fältström <paf@frobbit.se>
To: Nico Williams <nico@cryptonector.com>
Cc: Peter Saint-Andre <stpeter@mozilla.com>, 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)
Date: Fri, 01 Jun 2018 17:13:53 +0200
X-Mailer: MailMate (2.0BETAr6113)
Message-ID: <D49D88F0-3159-4913-BF95-755B88B70B2D@frobbit.se>
In-Reply-To: <20180601151053.GI14446@localhost>
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>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_95D4931F-9D44-4CE8-8137-06B593A4BC04_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o7qCTu-zPm8VymUwHu1I2phNw7o>
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 15:14:08 -0000

On 1 Jun 2018, at 17:10, Nico Williams wrote:

> Doesn't seem like the end of the world to me.  Maybe there is no sense of urgency to IDNA improvements.
>
> 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.

Exactly this was what happened, which made IDNA2008 updates at IANA be blocked. IAB have now asked me as  the appointed expert to move things again, which I will do now actually(!) and we'll see how many will show up this time. Last time exactly three people. Out of which I was one.

   Patrik

v2.23.0 | Report a Bug | By Email