Re: [I18nrp] charter -01
"Phillips, Addison" <addison@lab126.com> Tue, 14 August 2018 05:00 UTC
Return-Path: <prvs=757acceba=addison@lab126.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 32CB0130E41
for <i18nrp@ietfa.amsl.com>; Mon, 13 Aug 2018 22:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.19
X-Spam-Level:
X-Spam-Status: No, score=-4.19 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3,
T_FILL_THIS_FORM_SHORT=0.01] 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 ThkI0EI_h9o9 for <i18nrp@ietfa.amsl.com>;
Mon, 13 Aug 2018 22:00:08 -0700 (PDT)
Received: from smtp-fw-33001.amazon.com (smtp-fw-33001.amazon.com
[207.171.190.10]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 51C37130E2D
for <i18nrp@ietf.org>; Mon, 13 Aug 2018 22:00:08 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.53,236,1531785600"; d="scan'208";a="749100717"
Received: from sea3-co-svc-lb6-vlan2.sea.amazon.com (HELO
email-inbound-relay-2b-1171e197.us-west-2.amazon.com) ([10.47.22.34])
by smtp-border-fw-out-33001.sea14.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA;
14 Aug 2018 04:58:54 +0000
Received: from EX13MTAUWB001.ant.amazon.com
(pdx1-ws-svc-p6-lb9-vlan2.pdx.amazon.com [10.236.137.194])
by email-inbound-relay-2b-1171e197.us-west-2.amazon.com (8.14.7/8.14.7) with
ESMTP id w7E4wJlt032280
(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL);
Tue, 14 Aug 2018 04:58:19 GMT
Received: from EX13D08UWB004.ant.amazon.com (10.43.161.232) by
EX13MTAUWB001.ant.amazon.com (10.43.161.207) with Microsoft SMTP Server (TLS)
id 15.0.1367.3; Tue, 14 Aug 2018 04:58:19 +0000
Received: from EX13D08UWB002.ant.amazon.com (10.43.161.168) by
EX13D08UWB004.ant.amazon.com (10.43.161.232) with Microsoft SMTP Server (TLS)
id 15.0.1367.3; Tue, 14 Aug 2018 04:58:19 +0000
Received: from EX13D08UWB002.ant.amazon.com ([10.43.161.168]) by
EX13D08UWB002.ant.amazon.com ([10.43.161.168]) with mapi id 15.00.1367.000;
Tue, 14 Aug 2018 04:58:19 +0000
From: "Phillips, Addison" <addison@lab126.com>
To: Peter Saint-Andre <stpeter@mozilla.com>, i18nrp <i18nrp@ietf.org>
Thread-Topic: [I18nrp] charter -01
Thread-Index: AQHUM09m3sa0mDFYYUmhhpzVBYYcUaS+psbw
Date: Tue, 14 Aug 2018 04:58:18 +0000
Message-ID: <b701b4237cb9487ca67645ff1ba48855@EX13D08UWB002.ant.amazon.com>
References: <ae88331d-0404-9a64-4faf-eee2989d0204@mozilla.com>
In-Reply-To: <ae88331d-0404-9a64-4faf-eee2989d0204@mozilla.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.160.33]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/gRw_4wY2e51ywshcOouEPo8ohoE>
Subject: Re: [I18nrp] charter -01
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: Tue, 14 Aug 2018 05:00:10 -0000
Hi Peter, I like this evolution. A few comments. The liaison text is a little curious. It says that liaising isn't "directly" in scope. Is that because the (almost certainly necessary) liaising with folks like the UTC, W3C (especially I18N WG :-)), ECMA, etc. will formally exist elsewhere? Maybe the charter should more strongly acknowledge the need for coordination while keeping the existing formal mechanisms intact. I'd suggest something like: -- While formal liaison mechanisms with other standards organizations (such as the Unicode Consortium) are not part of the directorate's charter, there is expected to be occasional coordination with the wider internationalization community that includes these other standard's bodies. -- I do like how you handled the "Reviews internet drafts..." text. I do think the more WGs and ADs get the need for early and systematic review, the better the results will be. At W3C we've struggled with getting the right mechanism for early and consistent visibility into specs: I'm never sure if that dragon is well-slain or not. I'd be concerned with the "finding out in a timely manner" problem. I like that your text doesn't seek to require signoff or impose other intrinsically onerous mechanisms right in the charter, but experience suggests that best intentions are insufficient. Regards, Addison Addison Phillips Principal SDE, I18N Architect (Amazon) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture. > -----Original Message----- > From: i18nRP [mailto:i18nrp-bounces@ietf.org] On Behalf Of Peter Saint-Andre > Sent: Tuesday, August 14, 2018 5:48 AM > To: i18nrp <i18nrp@ietf.org> > Subject: [I18nrp] charter -01 > > The proposed charter I sent on August 9 could be considered version -00. > Here is -01 based on feedback received so far... > > ### > > Internationalization Directorate (i18ndir) Charter > > 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 technologies such as 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 6532), > 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 has the following responsibilities: > > * Reviews Internet-Drafts and provides guidance to specification authors and > working groups that re-use or ought to re-use IETF internationalization > technologies or that otherwise touch on internationalization issues. > > * Works together on solutions to narrowly scoped problems that arise with IETF > internationalization technologies (while deferring larger initiatives to separate > working groups, if needed). > > * Advises Area Directors and other IETF stakeholders (including other > directorates and review teams, such as the Security Directorate and ART Area > Review Team) with regard to internationalization. > > * Maintains an effective team by organizing its work processes, documenting > recommended solutions to common internationalization issues, recruiting new > team members, and training team members and IETF participants. > > 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 i18ndir@ietf.org. > The list archives are available at > https://www.ietf.org/mail-archive/i18ndir/secdir/current/maillist.html. > > ###
- [I18nrp] charter -01 Peter Saint-Andre
- Re: [I18nrp] charter -01 Phillips, Addison
- Re: [I18nrp] charter -01 Patrik Fältström
- Re: [I18nrp] charter -01 Hollenbeck, Scott
- Re: [I18nrp] charter -01 Spencer Dawkins at IETF
- Re: [I18nrp] charter -01 Nico Williams
- Re: [I18nrp] charter -01 Patrik Fältström
- Re: [I18nrp] charter -01 Asmus Freytag
- Re: [I18nrp] charter -01 Jiankang Yao
- Re: [I18nrp] charter -01 Hollenbeck, Scott
- [I18nrp] Time to take a half-step back? (was: Re:… John C Klensin
- [I18nrp] Internationalization and Localization (w… John C Klensin
- Re: [I18nrp] Internationalization and Localizatio… Jiankang Yao
- Re: [I18nrp] charter -01 Peter Saint-Andre
- Re: [I18nrp] Time to take a half-step back? (was:… Spencer Dawkins at IETF
- Re: [I18nrp] Time to take a half-step back? (was:… Peter Saint-Andre