Re: [I18ndir] Will there be an I18N directorate meeting at IETF 108?

Nico Williams <nico@cryptonector.com> Wed, 24 June 2020 15:43 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 A680B3A0E15 for <i18ndir@ietfa.amsl.com>; Wed, 24 Jun 2020 08:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.753
X-Spam-Level:
X-Spam-Status: No, score=-0.753 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, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 QN-a2sdUt6YU for <i18ndir@ietfa.amsl.com>; Wed, 24 Jun 2020 08:43:21 -0700 (PDT)
Received: from anteater.elm.relay.mailchannels.net (anteater.elm.relay.mailchannels.net [23.83.212.3]) (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 B754A3A0E05 for <i18ndir@ietf.org>; Wed, 24 Jun 2020 08:43:20 -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 8550B921223; Wed, 24 Jun 2020 15:43:19 +0000 (UTC)
Received: from pdx1-sub0-mail-a31.g.dreamhost.com (100-96-21-80.trex.outbound.svc.cluster.local [100.96.21.80]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 964F29213BF; Wed, 24 Jun 2020 15:43:18 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a31.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); Wed, 24 Jun 2020 15:43:19 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Cooperative-Cure: 26a58a194038474b_1593013399072_3939041584
X-MC-Loop-Signature: 1593013399072:2977356180
X-MC-Ingress-Time: 1593013399071
Received: from pdx1-sub0-mail-a31.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a31.g.dreamhost.com (Postfix) with ESMTP id 521CF7E637; Wed, 24 Jun 2020 08:43:18 -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=5t+/vSrOKaROAy csDhzpocPdmyk=; b=Lvu5gjjbOoS/JUHsjBb633CxaAbf26tc6/MtWntpQFUuY3 kQL9C5/QGqReIYW9AQjvs1LQ3Umv23eXaHEnzjOzMY/BzIZvjEVjih4wv8exGOnL rrdq584KBjAIDdLc59GArDqvAPX5eAFNeQhuAudiB1VPCC8s9gSG4yf0j/6NU=
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-a31.g.dreamhost.com (Postfix) with ESMTPSA id 454557E644; Wed, 24 Jun 2020 08:43:16 -0700 (PDT)
Date: Wed, 24 Jun 2020 10:43:11 -0500
X-DH-BACKEND: pdx1-sub0-mail-a31
From: Nico Williams <nico@cryptonector.com>
To: John C Klensin <john-ietf@jck.com>
Cc: i18ndir@ietf.org
Message-ID: <20200624154309.GU3100@localhost>
References: <20200623160021.GO3100@localhost> <723F92393735E684C75471FA@PSB> <20200623191501.GP3100@localhost> <C2D29B21FB339FE6B5820D39@PSB> <20200624052654.GS3100@localhost> <B439664D0432EDABFEB98988@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <B439664D0432EDABFEB98988@PSB>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: 0
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduhedrudekjedgkeehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecuggftrfgrthhtvghrnhepffdtkeethfeuteeviefgfeegjeetjedvhfehgfdvtdefueejheelgeeuhffghffgnecukfhppedvgedrvdekrddutdekrddukeefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomh
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/54S50NiVV_biGoLhbBDjtrFi7Pg>
Subject: Re: [I18ndir] Will there be an I18N directorate meeting at IETF 108?
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: Wed, 24 Jun 2020 15:43:23 -0000

On Wed, Jun 24, 2020 at 02:13:13AM -0400, John C Klensin wrote:
> --On Wednesday, June 24, 2020 00:26 -0500 Nico Williams
> <nico@cryptonector.com> wrote:
> > On Wed, Jun 24, 2020 at 12:05:31AM -0400, John C Klensin wrote:
> >> --On Tuesday, June 23, 2020 14:15 -0500 Nico Williams

[...]

> > You suggested that I should "write an I-D that ...".  Yes,
> > well, I have. I've not submitted it _yet_, though earlier I
> > did link the GH repository where I keep the source and
> > rendered output.  I am, of course, willing to submit it --
> > indeed, I plan to.  The thought occurred, you see, that if
> > there was to be a meeting at IETF 108, then I might aim for
> > it, and if not, then maybe the next one.
> 
> Ok.  And, while it is just my personal opinion and based on
> several guesses (including, IIR, a quick look at the GH
> repository) you need to take it to either the Internet Area or
> the IRTF and not i18ndir.  That belief would be the case even if

I'm not so sure.  To begin with, we were asked to early-review an I-D
regarding I18N and NFSv4, and presumably we'll have to review again
later when it progresses, so the matter is germane _here_ and _now_.  We
might advise punting to IRTF -or not-, but it is certainly within our
purview to provide review and advice at this time.

(It shouldn't even be necessary that I submit an I-D to have that
thread: we have an I-D in front of us (D. Noveck's) that is a sufficient
vehicle for debate.  My submitting an I-D is probably a good idea, but
hardly required.)

> the directorate were active and functioning as a directorate
> because I would then also suggest that, with all of the
> documents we should have in the pipe (many now-expired I-Ds), we
> should not prioritize new network file system designs.  My
> opinion might change after I studied a posted I-D, of course.
> And YMMD and so might that of many others.

Your opinion is noted.  Until this group is reformed/disbanded/
whatever, I will continue to act as though it is a directorate.

> > Thus my question.  Mine was a simple, polite, and fair
> > question -- one with a simple answer, and surely someone must
> > know the answer to it: will this directorate meet "at" IETF
> > 108?
> 
> Ok.  Then maybe I (and Asmus) should not have responded at all,
> because only Pete and one or the other AD can make that
> decision.  My note was just my opinion about whether such a
> meeting would be necessary or desirable and the conditions that
> might make it so.

It would be fair of the chairs to ask the participants if they want a
meeting.  Your saying "no" is fair.  Asmus said, essentially, "if the
time slot is convenient" -- also fair.  I'm saying "yes".  Three
responses may not be enough to determine consensus, but then, I don't
think the chairs need consensus to call a meeting.

> As of now, I have seen no evidence that such a meeting is
> scheduled or anticipated.

This is correct.

> > [...]
> 
> See above and note that one of those co-chairs has been
> essentially non-responsive for a few months (with a really good
> reason for parts of that period) and the other indicated a
> rather long time ago that he had no time to put in on this, or
> other IETF, work.

Well, then the chair who indicated no-time/interest should step down or
be removed.  I'm willing to wait for the other chair.  And I'm willing
to wait to IETF 109 if that chair won't be available anytime soon (a
fair assumption given the circumstances).  I'm not in a hurry.  David
Noveck has a late 2020 milestone to aim for, but that's after IETF 109
anyways.

I am _not_ willing to agree that we de facto aren't a directorate, or
that the directorate should be disbanded, or whatever negative proposal
along those lines -- not yet.

> So, for this decision and others, I await responses from either
> the remaining co-chair, from the ADs to re-sort the leadership,
> or from the ADs to manage some sort of reorganization.

Indeed.  I do advise against disbanding this team.  I believe your
negative outlook is unwarranted.  More leadership is required, to be
sure, and the first step is to recognize that.  Only after we have
attempted to address the lack of leadership and/or energy should we
consider abandoning the project.  Especially considering that I am
bringing some energy right now.  I'm willing to trade energy on the IDNA
matter for energy on the filesystem matter.

Nico
--