[I18ndir] Do we need an I18N WG? (Re: I-D on filesystem I18N)

Nico Williams <nico@cryptonector.com> Tue, 07 July 2020 19:35 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A88D63A09E4 for <i18ndir@ietfa.amsl.com>; Tue, 7 Jul 2020 12:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 7rH5gpY-Ioko for <i18ndir@ietfa.amsl.com>; Tue, 7 Jul 2020 12:35:24 -0700 (PDT)
Received: from bee.dogwood.relay.mailchannels.net (bee.dogwood.relay.mailchannels.net [23.83.211.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FF983A09DB for <i18ndir@ietf.org>; Tue, 7 Jul 2020 12:35:24 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id BF8C7402D80; Tue, 7 Jul 2020 19:35:22 +0000 (UTC)
Received: from pdx1-sub0-mail-a38.g.dreamhost.com (100-96-5-119.trex.outbound.svc.cluster.local [100.96.5.119]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 1C993400AF2; Tue, 7 Jul 2020 19:35:22 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a38.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.8); Tue, 07 Jul 2020 19:35:22 +0000
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Cellar-Society: 5ed3766b5319090a_1594150522640_3561582336
X-MC-Loop-Signature: 1594150522639:2674389694
X-MC-Ingress-Time: 1594150522639
Received: from pdx1-sub0-mail-a38.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a38.g.dreamhost.com (Postfix) with ESMTP id C03DFB474C; Tue, 7 Jul 2020 12:35:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=30nS3xeIOT8tYR YHa2zJCVHWodY=; b=YRdMr6MyRE8qZmUvPyP4oyzGy1R8mti5RhGH+EP8NIfo+i 1sM5YAOjKz+ChOTvSFXZfyVT/aCkAwPPh7psYnOnbqwaeND67+3bQ3xAgkympJIQ TKU0XFVE+FmJunJJ9vvShoKgbOp1+dJR+Lsl8n+GMmXyNb7p7eTAgoj5Mr7jc=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a38.g.dreamhost.com (Postfix) with ESMTPSA id 19531B4758; Tue, 7 Jul 2020 12:35:19 -0700 (PDT)
Date: Tue, 07 Jul 2020 14:35:16 -0500
X-DH-BACKEND: pdx1-sub0-mail-a38
From: Nico Williams <nico@cryptonector.com>
To: John C Klensin <john-ietf@jck.com>
Cc: Patrik Fältström <patrik@frobbit.se>, i18ndir@ietf.org
Message-ID: <20200707193515.GS3100@localhost>
References: <20200706225139.GJ3100@localhost> <B8BC0F0A-94AB-4BEF-8A5F-449049E28D8F@frobbit.se> <20200707070456.GK3100@localhost> <B0FAFBAF9EA570CCFB2575CF@PSB> <5F12E7F0-75AC-42A0-8138-771071A86F68@frobbit.se> <5956450816F54A60A5C9C5D1@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5956450816F54A60A5C9C5D1@PSB>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduiedrudehgddufeefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqeenucggtffrrghtthgvrhhnpefftdektefhueetveeigfefgeejteejvdfhhefgvddtfeeujeehleeguefhgffhgfenucfkphepvdegrddvkedruddtkedrudekfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopehlohgtrghlhhhoshhtpdhinhgvthepvdegrddvkedruddtkedrudekfedprhgvthhurhhnqdhprghthheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqedpmhgrihhlfhhrohhmpehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmpdhnrhgtphhtthhopehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhm
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/RphEDLjVwSusy1OK6DxdVDdQgQ0>
Subject: [I18ndir] Do we need an I18N WG? (Re: I-D on filesystem I18N)
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2020 19:35:27 -0000

On Tue, Jul 07, 2020 at 03:16:13PM -0400, John C Klensin wrote:
> At least most such reviews are almost certainly going to have to
> come from this directorate list because, whatever the strengths
> and weaknesses of this group, it probably includes almost
> everyone who has been active in the IETF on i18n work and who
> has a reasonable claim to broad expertise on at least some i18n
> topics (I can identify a few exceptions, but don't expect them
> to be active any time soon).  And, as we have repeatedly
> discovered working together, i18n documents (at least) get much
> better with active collaboration and discussion, not just
> reviews thrown over the wall.
> 
> However, with regard to doing that sort of collaboration
> (independent of a few reviews of documents from assorted IETF
> WGs), the directorate seems to be both disfunctional and lacking
> any form of leadership or guidance.   And, if we can't get
> enough collaboration (or some form of aggressive push-back), I
> think the experience with RFC 8753 and with 5891bis strongly
> suggests that more work on any of those documents may be a waste
> of effort.

If we're failing to review I-Ds, is that because

 - assignees are failing to do them,
 - the chairs are failing to assign reviewers,

or because

 - we're talking about I-Ds that come from within this group and we're
   not providing enough energy to see them progress?

If it's the last case, note that we're not a WG, but if we're expected
(or want to) have our own documents, then maybe we should be a WG rather
than a directorate, or at least maybe we ought to meet.

IMO we should replace the I18N directorate with an I18N WG.  The main
difference is that we could have milestones involving publication of
RFCs, and we could be expected to have regular and even interim
meetings, and perhaps we could continue to function as a directorate
responsible for reviewing other WGs' I-Ds that have or should have I18N
considerations.  If we don't have the energy for a WG, then at the very
least we should meet as a directorate once or twice a year.

Regarding energy, I would say that energy can be harnessed by having a
meeting at all, or at least that having meetings would better allow us
to gauge level of energy.

(Note: it's too late to schedule a BoF about creating an I18N WG at IETF 108.)

Nico
--