RSE Series Editor (Redux)

Sarah B <sbanks@encrypted.net> Wed, 19 June 2019 18:23 UTC

Return-Path: <sbanks@encrypted.net>
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 47B9F120879 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2019 11:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 8ae_kKO3zXox for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2019 11:23:00 -0700 (PDT)
Received: from aws.hosed.org (aws.hosed.org [50.16.104.137]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8A4E12083E for <ietf@ietf.org>; Wed, 19 Jun 2019 11:22:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by aws.hosed.org (Postfix) with ESMTP id C21CF8007B for <ietf@ietf.org>; Wed, 19 Jun 2019 14:22:43 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at aws.hosed.org
Received: from aws.hosed.org ([127.0.0.1]) by localhost (aws.hosed.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kodJAwEJND4j for <ietf@ietf.org>; Wed, 19 Jun 2019 14:22:43 -0400 (EDT)
Received: from [192.168.1.211] (corelight.static.monkeybrains.net [208.90.215.182]) by aws.hosed.org (Postfix) with ESMTPSA id 7D4C980062 for <ietf@ietf.org>; Wed, 19 Jun 2019 14:22:43 -0400 (EDT)
From: Sarah B <sbanks@encrypted.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Subject: RSE Series Editor (Redux)
Message-Id: <8448A66F-7E6B-4BA1-92AF-82FD777EE525@encrypted.net>
Date: Wed, 19 Jun 2019 11:22:42 -0700
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Haad4WB7w5fXDweboeNsjKOmnbM>
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 18:23:10 -0000

Hi,
	I started a second thread, mostly so that when I replied, you'd understand that I'm trying to broadly reply to the points I feel need addressing, and not to 1 specific person. I also agree with a previous comment that the IAB has delegated the RSE responsibility to the RSOC and the RSOC doesn't need to be micromanaged in that process, as there are ample feedback loops (there are 2 IAB members, 1 IESG member, the interim director on the RSOC directly, and we communicate with the IAB and LLC as well), but it's my style to be as transparent as I can be.


Contract extension concerns
---
	As Alexander and Ted pointed out, the language of the contract states that contract runs in blocks of 2 years, and be extended twice, before mandatorily going out to bid again. It's also worth pointing out that since Heather started as RSE, the RSOC did run through the contract process with her one full time (she was RSE, the RSOC recommended that we extend and the contract did extend 2 more times, for a total of 6 years) - and then the RSE function went out to bid again. Heather/Spherical Cow Consulting bid, and Heather is now RSE again. What happened here is mostly no different; she was awarded the contract the second time around, and with the first term of 2 years coming to an end, the RSOC recommended to re-up that contract for another 2 years. That would have brought us to 4 years. The difference here is that the RSOC decided proactively to recommend to put the contract out to bid again. Let me address the RSOC's thinking in "why", and share with you a tidbit about Heather.

	When I joined the RSOC in 2014, Heather introduced herself to me, and shared an overview of what she does, how she fits into the RSOC, and shared general information. She also, that very first meeting, raised her concerns over being the only bidder on the contract; what happens if she didn't bid again? What happens if she's the only bidder? What happens when she's ready to retire? Heather was proactively thinking ahead about succession planning and what was best for the RSE role and the community as a whole, even though she was fully committed to the job, she was looking to make sure the transition was as easy as it could be, for both the new RSE and the community, down the road. That was 5 years ago, and I think that says a lot about Heather's character and her professionalism and her commitment to the role. As I've pointed out, we did indeed go through a second RFP process wherein Heather was awarded the contract. However, we didn't receive any other bids for the role, and that was a concern to both Heather as an RSE, and the RSOC. I hope the reason why is obvious.. what happens if she were (quite unlikely, knock on wood) to be hit by the proverbial bus? What would we do? Fast forward to the end of 2018/current, where the RSOC has been largely reseated, and the new members on the RSOC are heading that we only had 1 bidder. There were the typical questions around the process, how did we do it, where did we post it, how long, did we advertise in the right places, with the right text, etc. The RSOC came to the conclusion that 1. we wanted to recommend to rebid the RFP earlier, which would not preclude Heather from bidding as well, specifically to address and alleviate those concerns and 2. that the rebid expressly had NOTHING to do with Heather's performance, and was not a comment on her. We certainly understood that bidding early could be construed in a way we didn't intend, and we did our best to communicate that it was not the RSOC's intention to do anything other than address the "single bidder" concern. It should be pointed out that the RSOC is empowered to make a recommendation; we do not award the contract, but my understanding is it would be in the purview of the LLC to put it out to bid early, if it decided to do so. 

Odds & Ends
---
	I too am concerned at the amount of speculation, but I also understand that this seems to be troubling to the community as a whole, something I personally have a lot of sympathy for. To John's point, the RSOC is seated (and reseated) at the pleasure of the IAB (RFC6635, Section 3.1, 3.1.1). The RSOC does NOT award the contract; does NOT formally extend the contract - remember, the RSOC makes recommendations with regards to the contract(s). We are required to oversee the RSE and ensure the Series is run in an open and transparent manner, and includes feedback from the community. Speaking for myself, while we are appointed to the RSOC by the IAB, and can be removed at any time by the IAB, I certainly feel we are accountable to the community, just like the IAB is, or the IESG is, or any of the rest of us are as participants; we certainly have a duty to include the community and protect the community interests. Speaking for myself, not as RSOC chair, I strongly reject any notion that we are NOT accountable to the community. That's part of why the IAB and the RSOC decided to send the note yesterday, and we're following up today. I will answer any question that I can. I will point out though, that the RSOC was specifically signalling that the attempt to rebid was NOT a comment on Heather's performance at all. 

Thanks,
Sarah