Re: RFC Series Editor (RSE) Statement of Work

Bob Hinden <bob.hinden@gmail.com> Thu, 25 July 2019 22:49 UTC

Return-Path: <bob.hinden@gmail.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 58C861201D1 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2019 15:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 zYsmQ9lFCeHw for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2019 15:49:20 -0700 (PDT)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50EFC120242 for <ietf@ietf.org>; Thu, 25 Jul 2019 15:49:20 -0700 (PDT)
Received: by mail-wm1-x32a.google.com with SMTP id v19so46098552wmj.5 for <ietf@ietf.org>; Thu, 25 Jul 2019 15:49:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=VxYmnu26c/EIRrspUgLRdruRA3XYp6//iRa0jgYIE0g=; b=I51RHDbNBK/QAwAf3GDVTNmFb7TSfm2aabg6TqdMgwDrqO7Folm+IZ5KuUm3qo3u1q EggCEhNG9odNJ6sqqXnBDIEXbcQTHlRjuF2i5LvfLeEnl0GH6HPC5VgRCra/M10OYfk/ weENL+G3wN9depTuy9vsNICsFFrLlIhLANaNDy3b7jHgq8g8IxWuvRezXr/HdYLCYr+8 sqWlcfJ8jzrN0mU+cGSfYihFme0ajyGx256jyzl38ijuzm2kz068ei8nnlYOgf1+e4Nm MDG/M9FJoa0c6tavwL5HBsIbpaEk3HHD8kQBQ0JkVWq2lHItZzfI8l6xRI8JDLX1nfF/ KnkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=VxYmnu26c/EIRrspUgLRdruRA3XYp6//iRa0jgYIE0g=; b=R7CwPp3RaNNEZQ0kRLau3yhlDtXE66th3H2cfkwMn+fYtzQ3L65wyLCMvjalND5RdV TDnmQzVI2NKKBi0GMSV1DgldMtLw/90jDJstFEqo96WHQpSQGZGDvW37XJFUxaUnVJqF vluOZH/GM76mb4RjvhBih6v9pLbGh//chKym8wrDk5e9rmSipGKoaDqQQW1pL7ndI4rr dbF1c6j81Q1AG1uq6z+6EFnML/rRGmLSyWmoyVRUmNPiXCCWfN54f63c9PQaEBzpZOk7 yp5yB9PWpxudUb6b9lgRjfCFII75OWzDb9h3sInkMPoA7buB9SG0gL90h1zngoSVTUNr v/fg==
X-Gm-Message-State: APjAAAX+ektQxZBU0/QJStwzAm9Eh9wYbPCDSDuYRhJE9vdbCGnV2Tdf ux0sfabtugiGjSVy2ceearo=
X-Google-Smtp-Source: APXvYqxDHp6VbtolsQzbRloWX4RaVJx1CUSX/bV9SCXS88RgQ6F1mu7mIFdRhhnZeJYL5dy44XWgZw==
X-Received: by 2002:a1c:3883:: with SMTP id f125mr78260792wma.18.1564094958744; Thu, 25 Jul 2019 15:49:18 -0700 (PDT)
Received: from ?IPv6:2001:67c:1232:144:74d6:25e5:1e27:36d? ([2001:67c:1232:144:74d6:25e5:1e27:36d]) by smtp.gmail.com with ESMTPSA id r123sm47081827wme.7.2019.07.25.15.49.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jul 2019 15:49:17 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <90BEE571-76F4-4294-8DFE-CD89BCAF0529@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_021BDDAB-A01B-4EE8-A6D9-E0E9C8F87F9E"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: RFC Series Editor (RSE) Statement of Work
Date: Thu, 25 Jul 2019 18:49:14 -0400
In-Reply-To: <B027130E-8357-44C7-AAAF-FA11C249FD92@isi.edu>
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Carpenter <brian.e.carpenter@gmail.com>, RSOC <rsoc@iab.org>, IETF <ietf@ietf.org>
To: John Wroclawski <jtw@isi.edu>
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> <B027130E-8357-44C7-AAAF-FA11C249FD92@isi.edu>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n27EOLdHZ_gsW1GsAQbbHqC96Ws>
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: Thu, 25 Jul 2019 22:49:23 -0000

John,

> On Jul 25, 2019, at 3:51 PM, John Wroclawski <jtw@isi.edu> wrote:
> 
> 
>> On Jul 22, 2019, at 8:52 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> 
>> 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 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.
> 
> Walking in from the distant sidelines, I would like to +1, or perhaps +1000, this note.
> 
> It hadn’t crystalized for me until Brian said it, but I think he’s got the key point exactly.
> 
> The basic gestalt of a search committee process is to find the best person in the world for a job, whether or not that person would have otherwise applied, or even whether they had any idea beforehand that the job existed and they’d be good at it.
> 
> The basic mindset of an RFP process is to pick the best person that applies.
> 
> I think the IETF wants option one.
> 
> To address a couple of points raised in replies to Brian, a) search committees absolutely _do_ work from written descriptions of the job, its key objectives, and likely-desirable candidate qualifications, and b) senior/executive search committees do indeed do this type of thing successfully all the time, and c) absolutely there are a great number of details to work out about responsibilities, structuring, communications, etc. that are extremely important as well.
> 
> But the key point is, I think, the IETF wants option one.

I completely agree.  This should be treated as a search, not writing an RFP and see who applies.

Bob

> 
> Cheers, —john
> 
> 
>