Re: RFC Series Editor (RSE) Statement of Work

Michael StJohns <mstjohns@comcast.net> Mon, 29 July 2019 20:48 UTC

Return-Path: <mstjohns@comcast.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 2D93312008B for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2019 13:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 7a22Zl-ugOaY for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2019 13:48:09 -0700 (PDT)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (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 2B29B120074 for <ietf@ietf.org>; Mon, 29 Jul 2019 13:48:09 -0700 (PDT)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id sBXwho6H6c9cbsCYyh4zgH; Mon, 29 Jul 2019 20:48:08 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1564433288; bh=J7D7NkJcp/4rKGtf0vA0z12YnhfpiqDhSAgR6c5Vk6E=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=iZnL5Vz9zndvzTL8BT1ZSz6Q4PMuQuSbQSfpJxxfcEd2Y85sgxSO1jr5GA4xE1F4B kNYW2s3hnmtrppoFAAaMkLzcPbC/t5/Zi9my8l7FtVSTdrdw+9iAes9pghTOpFrBlZ Mxp7hCbfig34JzRBT6bGH0+I2Ire6goKSRH81L+IP+OJo2tdSLTm4LmaCGWBp72xfG h3A2yR5mXWx6UhxC362X6i3fcTXp2lgfbn6T0Ee1QKhXpwZ+rNCjzTk/ICobMSV1O9 UzNCbCOCt92iZvor3QM8PPlIzl+BXK2JqArOxdJYbA5BiDuiHBcNu3HPcIi83vEQ/y W9YsSHIkl8JLg==
Received: from [IPv6:2601:152:4400:437c:75b8:7e7e:f605:bffb] ([IPv6:2601:152:4400:437c:75b8:7e7e:f605:bffb]) by resomta-ch2-15v.sys.comcast.net with ESMTPSA id sCYxhGJlG28YJsCYxhucum; Mon, 29 Jul 2019 20:48:08 +0000
X-Xfinity-VMeta: sc=0;st=legit
Subject: Re: RFC Series Editor (RSE) Statement of Work
To: 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> <B027130E-8357-44C7-AAAF-FA11C249FD92@isi.edu> <F6C97564-6DD6-47A2-A9E6-5401F50BE4D5@cable.comcast.com> <ce36b799-80e3-7eaa-576b-c7137793f115@cs.tcd.ie> <21882.1564430860@localhost>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <8ce5bf75-7040-4b6c-32fc-0042cc6dbfc2@comcast.net>
Date: Mon, 29 Jul 2019 16:48:07 -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: <21882.1564430860@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PrmH7Utqt0K59g9mrZVaIk5-274>
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, 29 Jul 2019 20:48:11 -0000

On 7/29/2019 4:07 PM, Michael Richardson wrote:
> Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>      >> [JL] If this is the case, I wonder if it much matters to the community
>      >> whether the role is an employee (full or part time) or a contractor
>      >> (full or part time)?
>      
>      > For reasons stated earlier on the iasa2 list and as I stated at
>      > the plenary during open mic, I remain opposed to the idea of an
>      > employee-RSE. It does seem to keep being suggested, but that won't
>      > IMO make it a better idea;-)
>
> Are you opposed to the "clerical" issue of how the person is paid,
> or are you opposed to the person being hired by interview rather than RFP?
>
Practical:

1) The general LOE for the RSE according to RFC6635 is 20 hours a week.  
It's difficult to be just a part-time employee as a salaried worker for 
various reasons including benefits, and the general assumption that if 
you're working for company A, you're not working for company B.  Throw 
in the need to do full time weeks 3-5 times a year for the RSE (IETF and 
various retreats or other meetings) and that time has to be taken from 
other employers and you get into some messy situations.

2) The employing organization (e.g. the LLC) doesn't really have the 
size to be able to handle traditional employees.  Even the ED hire is 
going to be interesting.  Think about payroll, HR, benefits, etc.  Then 
think about the need for some manager.  You could make it the LLC under 
an "employee with a contract model" and assign them to the LLC to 
manage, but there would still be a lot of things to work out.  Then 
there's "advancement" or the lack thereof.   For Ray, we punted - he was 
really a contracted for employee by the IAOC of a larger company (ISOC) 
as far as I can tell.   And placing the RSE under the ED is pretty much 
a recipe for failure for oh so many reasons.

3) Stephen's other note (surprising to me) about life tenure after a 
period of time in certain companies.  I don't think we want to limit our 
selection to countries where this isn't the law.

Relational:

1) This is a senior person who really should be co-equal with the IAB 
and IESG.  Contracts at least allow for some specification of 
relationships between these three entities without screwing up supremacy 
issues in each of the entities bailiwick.   I would expect the next 
contract to be rather restrictive on who gets to give direction to the RSE.

2) We haven't any one who could actually be a manager respected (in 
terms of the ability to actually provide value add in managing someone 
who knows more about publishing than the putative manager) by a good 
candidate for the RSE position.

Obvious:

1) Publishing is not in any way a core competency of the IETF.