Re: [I18nrp] proposed charter for an Internationalization Directorate

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 09 August 2018 20:45 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2C49130E0E for <i18nrp@ietfa.amsl.com>; Thu, 9 Aug 2018 13:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 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, T_FILL_THIS_FORM_SHORT=0.01, 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 TWAZLfMdfLaD for <i18nrp@ietfa.amsl.com>; Thu, 9 Aug 2018 13:45:55 -0700 (PDT)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (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 DD575130ED6 for <i18nrp@ietf.org>; Thu, 9 Aug 2018 13:45:54 -0700 (PDT)
Received: by mail-pf1-x435.google.com with SMTP id k21-v6so3384713pff.11 for <i18nrp@ietf.org>; Thu, 09 Aug 2018 13:45:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=K2Pj/eImqBsxDW+/1wAELRZDb7GB93If2RzzDXpx8Hw=; b=KDfyYN2tRhiPrqdmPTnIDojW1YOiEI8bwI200vH9wmcIVLwDhhvHF46WSpmvEWOjZ3 ENP/KogD4bY8Ppk1k6rqQJ32Rx+JOlNEGj6WnAgZYCJOVtBsl3DF0LTuC2U4+qtaKfH7 y+UNp1UexbZNQ80ZBBMVA7xmzbl+N/zsFvURS+ubcSdY/hv0Wi0ZaFUjNqNJHUP8ezFF S3AFLExyOkIH4NUtKtyOEtx25BNq+kjMSTW8fs/LbdjVejLuBxCe+8pA1jENnl8N2UEQ uVPHkz+kFSlBcPSb6Hmnuk2RboJJIV9nmiLhXhASdnGPVuGuWJLUlzwolLPO7lZw8rAk 3HcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=K2Pj/eImqBsxDW+/1wAELRZDb7GB93If2RzzDXpx8Hw=; b=G3/VIJ7GQHblURWnaNAgVZm4q/L3ImxCc3ik30aNPixBtw9wElvyqT/R4KExt3n3aC DpysMIP5uDPAIhIZk0tULUAQs0cZ1ZsU7ZQy4yPJ0L05MS3I59SB4sE5Gcjk4t7JfRY2 jvi9Wlqm+otkogbsh+cMoGQtfFdPNTX5PfRDXx1ugIb9B98rT4Gros9qJ0ekWaBHw0Gh NewWTYNygKamZZyFTueY/GyD5cjsQd2R//WKHfC8oMDBGVUmkhOmK6Hj0N7sEMVNsDik +EIvDu9aaM38G+cogywdyUuu5FMKddftYqvDlY+a6nGvBVeIFaB5ZC2RjtkzmWtOc/EX IQXQ==
X-Gm-Message-State: AOUpUlH+UPeGzXFkXRMxAAnPAXtCtW14N3TfPGTViE1dRvcZ12XG8e+9 zfmwg41qxbhWMFQT/WkoRbIOXFMS
X-Google-Smtp-Source: AA+uWPw/AlJ5s9S7h7gw2iJVtAWUYXzNTD1WJrO7cM52jWaYx+rANs3QyqisJQrAVMQI1qD5pqR3gA==
X-Received: by 2002:a62:5dd7:: with SMTP id n84-v6mr3942533pfj.68.1533847554021; Thu, 09 Aug 2018 13:45:54 -0700 (PDT)
Received: from [192.168.178.30] (227.24.255.123.static.snap.net.nz. [123.255.24.227]) by smtp.gmail.com with ESMTPSA id a7-v6sm7349479pgv.51.2018.08.09.13.45.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Aug 2018 13:45:52 -0700 (PDT)
To: Peter Saint-Andre <stpeter@mozilla.com>
References: <cb1cfca9-321d-6718-07f5-12325b80e2c9@mozilla.com>
Cc: i18nrp@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <1ea2aaaf-5d77-92db-def8-22926d399424@gmail.com>
Date: Fri, 10 Aug 2018 08:45:59 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <cb1cfca9-321d-6718-07f5-12325b80e2c9@mozilla.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/mn_4rKnfuvK_wGxpIP0njJskBA4>
Subject: Re: [I18nrp] proposed charter for an Internationalization Directorate
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2018 20:45:57 -0000

Peter,

A good start IMHO.

"The directorate reviews selected Internet-Drafts..."
doesn't really tell the reader which drafts will be selected.

Should you also include a few words about how the directorate
interacts with the existing review process and in particular
with ARTART reviews? That's where I18N defects have their last
chance to be picked up.

Will the directorate be willing to do early reviews on request
from a WG?

Regards
   Brian Carpenter

"Looks like a disaster; why wasn’t I invited?" - Eeyore (2018)

On 10/08/2018 04:29, Peter Saint-Andre wrote:
> As we have discussed on this list and at IETF 102, to date
> internationalization (i18n) reviews at the IETF have been dependent upon
> the occasional attention and uncoordinated involvement of particular
> individuals. We have identified several problems with the status quo: we
> don't reliably identify documents needing review, we often identify
> issues only late in the standardization process, we have a small and
> static set of reviewers, the reviewers have not been organized to
> function as a team, and we are not training new reviewers or educating
> specification authors in a systematic fashion. In addition, we have not
> succeeded in fixing smaller problems with existing i18n technologies (an
> activity that can be seen as a particular kind of review or as bordering
> on a study group or expert team).
> 
> By my reading, we have broad agreement that an Internationalization
> Directorate, if properly scoped and managed, could help to improve the
> i18n aspects of IETF specifications. Therefore I have written the
> following draft charter, and I would like to request feedback from folks
> on this list.
> 
> Thanks!
> 
> Peter
> 
> ###
> 
> Internationalization Directorate (i18ndir)
> 
> The Internationalization Directorate is a specialized advisory group
> that assists the Area Directors of the Applications and Real-Time Area
> with regard to internationalization, in accordance with RFC 2418.
> 
> In support of a global Internet, the IETF has long worked on
> internationalization of the Internet through various technologies,
> including but not limited to text encodings (RFC 20, RFC 3629, RFC
> 5198), character sets (RFC 2277), language tags (RFC 5646), URIs (RFC
> 3986), domain names (RFC 5890), email addresses (RFC 6530) and headers
> (RFC 5335), HTTP headers (RFC 7231, RFC 8187), and usernames and
> passwords (RFC 8265). Because the appropriate use of these technologies
> in any particular Internet protocol is not always clear-cut,
> specifications developed within the IETF often need to be reviewed by
> individuals with competence in internationalization. Another sort of
> review is required for adjustments to the underlying technologies
> themselves, for instance handling issues with internationalized domain
> names that arise because of updates to the Unicode standard.
> 
> The directorate consists of experienced members of the IETF and the
> broader technical and language communities who have competence in
> internationalization. The directorate reviews selected Internet-Drafts
> with respect to common internationalization issues, provides guidance to
> specification authors and working groups that re-use or ought to re-use
> the aforementioned IETF technologies, works together on solutions to
> narrowly scoped problems that arise with those technologies (while
> deferring larger initiatives to separate working groups, if needed), and
> advises Area Directors and other IETF stakeholders with regard to
> internationalization. The directorate itself is responsible for
> organizing its work processes, documenting recommended solutions to
> common internationalization issues, and maintaining an effective team
> through appropriate recruiting and training initiatives. However,
> liaison activities with other standards development organizations (such
> as the Unicode Consortium) are not directly in scope for the
> directorate. In short, the internationalization directorate acts as a
> consultative group of experts offering expertise and guidelines with
> respect to internationalization within the IETF.
> 
> The directorate can be contacted by sending e-mail to [TBD] and the list
> archives are available at [TBD].
> 
> ###
> 
> 
> 
> _______________________________________________
> i18nRP mailing list
> i18nRP@ietf.org
> https://www.ietf.org/mailman/listinfo/i18nrp
>