Re: RFC Series Editor Resignation

Benjamin Kaduk <kaduk@mit.edu> Mon, 01 July 2019 22:43 UTC

Return-Path: <kaduk@mit.edu>
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 D17F31201BC for <ietf@ietfa.amsl.com>; Mon, 1 Jul 2019 15:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 KHs8f4k2FkIX for <ietf@ietfa.amsl.com>; Mon, 1 Jul 2019 15:43:11 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 A2764120242 for <ietf@ietf.org>; Mon, 1 Jul 2019 15:43:11 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x61Mh67B008494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 1 Jul 2019 18:43:08 -0400
Date: Mon, 01 Jul 2019 17:43:05 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Michael StJohns <mstjohns@comcast.net>
Cc: ietf@ietf.org
Subject: Re: RFC Series Editor Resignation
Message-ID: <20190701224305.GL13810@kduck.mit.edu>
References: <685B34F6-E0E2-4050-B9DD-615F475F62B7@encrypted.net> <6E58094ECC8D8344914996DAD28F1CCD18D3A5CF@dggemm526-mbx.china.huawei.com> <8CDEE96C-B1DA-4991-B8AA-A2455B705B77@mnt.se> <34F6E9B8-2BC2-46AC-8AF8-EFDA552D659D@tzi.org> <EA13A490-2636-459F-919B-8A72F4F45174@cable.comcast.com> <df5a6b6c-d444-7e72-dd6c-e2fa844195fa@comcast.net> <20190628214503.GC30882@kduck.mit.edu> <7e5167bf-8167-bf81-981f-662d6da6f1ab@comcast.net> <20190628232206.GC10013@kduck.mit.edu> <e7bf71c3-7842-8699-1f56-36ffa823da99@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <e7bf71c3-7842-8699-1f56-36ffa823da99@comcast.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IzNP8Z0FtW73ko6VZ5GLYnqtr38>
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: Mon, 01 Jul 2019 22:43:23 -0000

[with no hats]

On Sat, Jun 29, 2019 at 06:23:22PM -0400, Michael StJohns wrote:
> foreseeable result_ that was _completely avoidable_, but the result had 
> many many parents:
> 
> 1) The community for not more carefully constraining the IAB's assertion 
> of authority over the RFC process.
> 2) The IAB for delegation of said authority to the RSOC without 
> carefully constraining its exercise.
> 3) The IAB for not paying attention to the result of the RFC++ bof

I think you should say more about why you think the *IAB* did not pay
attention to the result of the RFC++ BoF.  Note that, as far as I can
recover the timeline of events here, the actions of the RSOC were the
triggering event.  Is there perhaps supposed to be some connection between
the BoF and the RSOC appointments of (4)?

> 4) The IAB for replacing the majority of the RSOC post the RFC++ bof 
> without input from the RSE, and in apparent violation of one of the 
> guiding principles of the RSOC - that of maintaining continuity from 
> year to year.
> 5) The community for not yelling a lot louder and longer when (4) happened.
> 6) The community, IAB and RSOC for not appreciating the value of a world 
> class professional editor/publisher to the continued excellence of the 
> RFC series, and for not expressing that appreciation in the form of 
> professional deference and independence rather than what appears to have 
> been more of a "you contractor, me boss"* model.
> 7) The RSOC for ... well - you know.
> 8) The LLC for not paying better attention to the relationship between 
> contractor and contractee.
> 
> I'm sure there are others.

Me, too, but that's a great start.

> 
> 
> Mike
> 
> *About a year ago, shortly after the RFC++ bof, I had a conversation 
> with one of the I* who I will not name about the disconnect between what 
> I though the RFC editor job was and what I was seeing the I* push.  The 
> phrase "she's just a contractor" is a direct quote from that conversation.

Wow, that seems pretty concerning, though I don't know if it would have (to
me) without the benefit of hindsight.

-Ben
(still no hats)