Re: RFC Series Editor (RSE) Statement of Work

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 22 July 2019 23:07 UTC

Return-Path: <jmh@joelhalpern.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 68367120048 for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2019 16:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 SFyJnacVMo9r for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2019 16:07:27 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 89E32120045 for <ietf@ietf.org>; Mon, 22 Jul 2019 16:07:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 45sy1W3Yx6zqkLV; Mon, 22 Jul 2019 16:07:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1563836847; bh=0xEV4OLRab3AtGS5ogwX/loKcTUGHJMafLpgo/Svh+A=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=UZRrJox5qn11yOSDujHcjk5mE5FQBnIfZF20j3TVdWzQxNR0kBDy8YJ5y/U+47667 qJEFD1O3Rjx2Kd5hmtIVn3KBTy4AN8msv0jRS6RU8cZKTqwtgWDI+Et2jgK4LhcOWv kK+vICwKERXxdKksR1NaloQTepjgd0KR8pta9JVM=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [IPv6:2001:67c:1232:144:493d:9d79:adad:a13c] (unknown [IPv6:2001:67c:1232:144:493d:9d79:adad:a13c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 45sy1V53pszqkLS; Mon, 22 Jul 2019 16:07:26 -0700 (PDT)
Subject: Re: RFC Series Editor (RSE) Statement of Work
To: Jari Arkko <jari.arkko@piuha.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF discussion list <ietf@ietf.org>
References: <9817BB4B-D828-4128-A70C-A8B966E6642F@encrypted.net> <CAL02cgRcGF80R_h5it_u7eGQrMjavpZ6_noEKb5vY5i1HqJYaA@mail.gmail.com> <7e82f47a-6a1d-8d3e-b183-e5159a071481@gmail.com> <9f7e969e-0374-2f9f-4ec6-e2d85a2fb819@gmail.com> <09F3525C-6789-4AEE-BA22-DD06B7AB7E30@piuha.net>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <c757419b-9353-8350-4142-03ba84bb7130@joelhalpern.com>
Date: Mon, 22 Jul 2019 19:07:23 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <09F3525C-6789-4AEE-BA22-DD06B7AB7E30@piuha.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ArtWNQwZQK8Ciw7UPrPzp_2xp5w>
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, 22 Jul 2019 23:07:30 -0000

As far as I know, the RSE search has never been principally (or at all) 
a financially based selection.
The bids were evaluated based on the apparent likelihood of the person 
successfully performing the needed job.  And if at all possible, doing 
more than we asked for.

I don't know why anyone thinks that the RSE search was price based.  The 
negotiation of salary is left to the IAD (ED) AFTER the selection.  (In 
fact, it is because that negotiation needs to take place, and could 
fail, that there is latitude in the request from the IAB to the IAD / ED 
/ IAOC / LLC.)

Yours,
Joel

On 7/22/2019 6:57 PM, Jari Arkko wrote:
> First, big +1 to mentioning Joyce more often :-)
> 
> Second, to the substance of Brian’s comments. My personal comments, only of course:
> 
>> The RFC Series Editor has always been treated as a senior colleague, and part of our community leadership; never as a hired hand, because it isn't the sort of job that can easily be measured or priced. Obviously, as a practical matter, the RSE has to be paid for their time and expenses, but it really doesn't matter whether that's as an employee, an individual contractor, or via their existing employer. That's basically a clerical matter, once the right person has been identified.
> 
> I fully agree!
> 
> (With a small caveat of relevant RFCs being flexible enough to allow that. But RFCs can be changed.)
> 
>> Obviously there will be a finite budget limit that the search committee will bear in mind. But we aren't trying to find the cheapest RSE; we're trying to find the best one.
> 
> I agree with you.
> 
>> I now think that the notion of a pre-defined statement of work and a competitive bidding process is *completely* inappropriate. What we should do, IMHO, is identify the right person by a search process with a well-informed search committee, and then leave IETF LLC to figure out any necessary employment or contractual details later.
> 
> I agree that a RSE is a very high level leader. But I’m not sure it directly follows that no statement of work or definition of role should exist. Usually when there’s a role to be filled somewhere in the world, even for a high level leader, there is some definition of what’s the scope and the expectations. But perhaps you meant to have an argument that the current RFC and/or SOW are far too focused on details and should emphasise the leadership aspect and not the details. And should clearly leave room for the selected leader to drive into a direction that she or he will eventually find the best direction. I’d be much easier convinced of that.
> 
> I have a similar reservation about appropriateness of “competitive bidding process”. I fully agree that making a search primarily a competition (and particularly, a finance-based competition) for any leadership position is a bad idea. But whether you’re looking for a CEO, Area Director, or the RSE there’s at least some possibility of alternative choices. If competition is the only thing in the search team’s mind, that would be bad. But they need to be aware of the potential out there when they are doing a search.
> 
> Jari
> 
>