Re: [I18nrp] charter -01
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 15 August 2018 16:01 UTC
Return-Path: <spencerdawkins.ietf@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 3F4B4130FEE
for <i18nrp@ietfa.amsl.com>; Wed, 15 Aug 2018 09:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, 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 3pdLyoBWQMa1 for <i18nrp@ietfa.amsl.com>;
Wed, 15 Aug 2018 09:01:45 -0700 (PDT)
Received: from mail-yw1-xc2d.google.com (mail-yw1-xc2d.google.com
[IPv6:2607:f8b0:4864:20::c2d])
(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 87F74130FED
for <i18nrp@ietf.org>; Wed, 15 Aug 2018 09:01:45 -0700 (PDT)
Received: by mail-yw1-xc2d.google.com with SMTP id c135-v6so1185670ywa.0
for <i18nrp@ietf.org>; Wed, 15 Aug 2018 09:01:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=Iz4NW1zDCEs0H2YHE766ov9yWG8UvlznbrXIjqgdcXY=;
b=JUmeXTfxaloljPoeQRzanBNruOCmeRgJ0BpcEvObXGunl6rr3ZajF7evwZ4PYVgT9z
/a0p+GMoqL9hMqsy+XeIt3ZRRvrSoGMlJIk8VuvQso1uCXbHGGq8mZKzjwrG/t1o9MLD
j/s1N9XB7NCqWybjwE35Vy+Ll8WgK2W1FOrxLuvBHH5jMoqrIPwEhOHVyhK1lMmP8Ipq
/S0D1BtTAbwmJOCdLsgL/ZgTshFdZzu/LBumMUZrF2ziWFN2GVPmZZJsy7+6c5qeGyRi
4GHeNeiZYu34PHdkHvqZs7I3BDt9R7M/BKERu80EHEpgD+/t/SvSokXjwTIxxq58O28h
WTxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=Iz4NW1zDCEs0H2YHE766ov9yWG8UvlznbrXIjqgdcXY=;
b=EUw+snQzfH1skqvWBW2WfAHeIspqwGX30qLDmp0Js4ismGmGJhkVIW+LYxg+ZWiflC
/4BIJyuEzxJ+nr9PuoTZ9RxLZxo1Ka4wa/dzjXX229Vkr3/JgGC3UyqpfajkscY3ds+I
7OK24j8A2vVE16k9KEBH0Bv5e8a/GRWJcOttK7WwB7CU4ir6Vo+Xa2LqYYMYkZcA5Ozt
6dlXflvkQQBXCQS2PRfqDTj4qY6HEc+Q9IHIsNnvEwvkv7NvjxpSGxCNAfBNqqioHwdR
9soBLT5lDURsfV8mSOGKJFDxLMJarlkuJfMapg4EWwlPpjP3CjkzVhPoLjwYFB9BbKv2
zgEw==
X-Gm-Message-State: AOUpUlF9qFmdl3xGtLV6QoCHgBMAVfTTOukGsFz558WQV6x3sZamX9oF
+YTcUj18LV9fIz0AsDz25NQZ+5er+8SHRRuRDpU/v62f
X-Google-Smtp-Source: AA+uWPxqlfDnCPuRmzBb+LHwP8Y2P6x9PJ9X/uc/9RnaFOZZRCkxBGLUS9NWKSrtm6LaOXagoJDQ6GRrqGiD8wHMz0U=
X-Received: by 2002:a0d:e846:: with SMTP id
r67-v6mr15281894ywe.19.1534348904451;
Wed, 15 Aug 2018 09:01:44 -0700 (PDT)
MIME-Version: 1.0
References: <ae88331d-0404-9a64-4faf-eee2989d0204@mozilla.com>
<b701b4237cb9487ca67645ff1ba48855@EX13D08UWB002.ant.amazon.com>
In-Reply-To: <b701b4237cb9487ca67645ff1ba48855@EX13D08UWB002.ant.amazon.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 15 Aug 2018 11:01:32 -0500
Message-ID: <CAKKJt-dEu_F9uhbeRVPbtR+LaH07zJnWVFoBsiVq=hx2qa5SZA@mail.gmail.com>
To: addison@lab126.com
Cc: Peter Saint-Andre <stpeter@mozilla.com>, i18nrp@ietf.org
Content-Type: multipart/alternative; boundary="000000000000696bd305737b7179"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/cz8YFoqVikIZHVRaMHSmlNIoSMk>
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: Wed, 15 Aug 2018 16:01:53 -0000
FWIW, On Tue, Aug 14, 2018 at 12:00 AM Phillips, Addison <addison@lab126.com> wrote: > 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. > This is only my opinion, but I was on the IAB for three years and was the first IAB prime for the IAB's liaison oversight program ( https://www.iab.org/activities/programs/iab-liaison-coordination-program/), when we set it up in about 2011, so I hope it's not super-wrong. We/the IETF relies a lot on informal interaction with other SDOs. There are other SDOs that the IAB maintains formal liaison relationships with, listed at https://www.ietf.org/about/liaisons/, but those tend to be SDOs that we have a lot of interaction with, and/or who require a formal liaison relationship to get anything done. Basically, if an individual IETF participant can send email to another SDO, and get a useful response, that's the preferred path. The directorate itself can figure out when that's necessary, and whether the responses coming back are useful, with no other process needed. If that doesn't work in your situation, that's a good conversation to have with the IAB. I'd start with Mark Nottingham, who is the IAB liaison oversight program prime now, but just sending an e-mail to the IAB and asking them for help/guidance should work just fine. It's also useful to note that some SDOs and external bodies have liaisons to the IETF, with no corresponding IETF liaison in the other direction, so IETF participants can be as informal as is helpful, even if the responses coming back have to be approved at plenary meetings before they come back.
- [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