Re: RFC Series Editor Resignation

John C Klensin <john-ietf@jck.com> Wed, 19 June 2019 16:12 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC581200F4 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2019 09:12:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 obuGCHXZRYlv for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2019 09:12:28 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3123120096 for <ietf@ietf.org>; Wed, 19 Jun 2019 09:12:28 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hddCE-0002A0-8I; Wed, 19 Jun 2019 12:12:26 -0400
Date: Wed, 19 Jun 2019 12:12:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <mellon@fugue.com>
cc: Stewart Bryant <stewart.bryant@gmail.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: RFC Series Editor Resignation
Message-ID: <EF2AEF6E9F0D8336837AFCC3@PSB>
In-Reply-To: <851A68D3-1C1B-494E-BFE4-41A036171976@fugue.com>
References: <685B34F6-E0E2-4050-B9DD-615F475F62B7@encrypted.net> <e9d747d0-a708-7bfa-f090-d0454344e782@levkowetz.com> <cc4c0ed5-dd1b-9eda-a294-e8e7c53ccb09@gmail.com> <AF9E74FB410E2F020188A5B9@PSB> <851A68D3-1C1B-494E-BFE4-41A036171976@fugue.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EgNzaud73AHu6fNaNghPKVjwQQc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2019 16:12:30 -0000


--On Wednesday, June 19, 2019 11:55 -0400 Ted Lemon
<mellon@fugue.com> wrote:

> The amount of speculation going on here is impressive. FWIW,
> my main reaction to this is that I'm really sorry to hear
> that Heather is going. She's been wonderful.

Agreed.  And I find her departure very upsetting.  I am
concerned about, but not speculating about, what led to that and
arguing that it is reasonable for the community to ask questions
rather than simply trusting that some combination of the RSOC,
IAB, and IETF LLC will sort things out, especially if they plan
to do that in secret.  I have no idea whether they plan to do
that in secret (or at all) but felt a need to respond to
Stewart's note that I took as suggesting that the community
should stay out of this.  I also find the 2.5 year story -- not
speculation, but something I believe both Sarah and Christian
have been explicit about -- to be troubling and believe that the
community is entitled to inquire about it even if the only
result is to improve how things are handled in tee future..

> I don't know if there is any debugging required here, but I
> do know that no part of the debugging process can happen on
> this mailing list. I won't ask you to stop, because you
> won't.

Well, my plan had been to make that one commend and then shut
up, at least until we heard from from the RSOC or IAB.  So I am
responding to your note, just as I responded to Stewart's, and
not the substantive issue.  And, again, no speculation there.
If I have misunderstood either your comments of Stewart's,
please correct me (on-list or off, as you prefer).

Both my earlier note and this one are about questions of
accountability and transparency, especially wrt management
practices, not speculation about what happened or why.   So,
while your complaint may be legitimate (and, from reading parts
of the thread, I think it probably is), please go pick on
someone else.

> So perhaps we can have a drinking game. One shot of espresso
> every time someone speculates wildly. Two shots every time
> someone gets the length of the term wrong. Every time you post
> you have to drink a shot. 

No comment.

best,
   john