Re: RFC Series Editor (RSE) Statement of Work

Benjamin Kaduk <kaduk@mit.edu> Mon, 05 August 2019 20:18 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 D697012012A for <ietf@ietfa.amsl.com>; Mon, 5 Aug 2019 13:18:27 -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 fUGJ81xcEdRm for <ietf@ietfa.amsl.com>; Mon, 5 Aug 2019 13:18:26 -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 3B453120105 for <ietf@ietf.org>; Mon, 5 Aug 2019 13:18:25 -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 x75KIK3X014695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 5 Aug 2019 16:18:22 -0400
Date: Mon, 05 Aug 2019 15:18:19 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Michael StJohns <mstjohns@comcast.net>
Cc: ietf@ietf.org
Subject: Re: RFC Series Editor (RSE) Statement of Work
Message-ID: <20190805201819.GU1006@kduck.mit.edu>
References: <F6C97564-6DD6-47A2-A9E6-5401F50BE4D5@cable.comcast.com> <ce36b799-80e3-7eaa-576b-c7137793f115@cs.tcd.ie> <21882.1564430860@localhost> <8ce5bf75-7040-4b6c-32fc-0042cc6dbfc2@comcast.net> <848781BF-6AF6-4DB2-A845-6A6449B36FBF@cooperw.in> <92dd887b-7c32-134d-4f12-ad8ff75da791@comcast.net> <C5DB2EEF-E075-47CA-87D5-699B594C2D9B@cooperw.in> <b33673ed-5a17-4552-a395-1244c85c969f@comcast.net> <20190801211318.GC1006@kduck.mit.edu> <fa25224b-fba9-a11c-7ffa-3252c85039ba@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <fa25224b-fba9-a11c-7ffa-3252c85039ba@comcast.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/e_LEBGXAuPE_DWqqa0OfNbl_ZgE>
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, 05 Aug 2019 20:18:28 -0000

On Thu, Aug 01, 2019 at 06:46:49PM -0400, Michael StJohns wrote:
> On 8/1/2019 5:13 PM, Benjamin Kaduk wrote:
> > Hi Mike,
> >
> > On Thu, Aug 01, 2019 at 04:16:07PM -0400, Michael StJohns wrote:
> >> Hi Alissa -
> >>
> >> Pruned - other comments in line.
> > Also pruning...
> >
> >> On 7/31/2019 2:34 PM, Alissa Cooper wrote:
> >>> By contrast, Portia was not an employee of ISOC. She was a contractor to ISOC before the IETF LLC was created, and is now a contractor to the IETF LLC, under your definition of “contractor/consultant.”
> >> Given that Portia is acting or interim (I don't actually remember which
> >> at this point), I don't know that her contractor status matters all that
> >> much or means anything for the future RSE or even for the future IAD.
> >>
> >> What's a lot more interesting is what you (singular and I*) see as the
> >> target relationship for the to-be-hired permanent IAD - contract with
> >> LLC, employee of the LLC, contract with the IAD's employing
> >> organization, something else?
> > As a potentially implicated party, do you see "I*" as just referring to
> > IETF LLC, or to the IESG, IAB, and potentially other bodies whose names
> > start with I?
> >
> > Thanks,
> >
> > Ben
> 
> Heh.
> 
> I know there was an RFP for the IAD, I don't know if that RFP listed a 
> preferred form of engagement or if that was left blank. If you know what 
> the preferred form as was listed in the RFP is, I'd be happy to accept 
> that as an answer.  If it was left blank, I'm wondering whether the 
> current I* leadership (LLC, IAB, IESG) has an idea of where they want to 
> go with respect to adding overhead positions (e.g. employee or 
> contractor or some other form of engagement) and why that form?  If the 
> best candidates prefer another form of engagement, are we prepared to go 
> in that direction?

Speaking just for myself, I do not have an idea about whether employee or
contractor or other is better.  It's not really clear to me that I should
(with my IESG hat on, as opposed to as a member of the community), either
-- the IESG is generally seen as the technical management group for the
IETF and I don't really have a reason to think that this sort of HR-like
activity falls under that scope.  It seems more like something that the
IETF LLC Board is designed for, and I have plenty on my plate already.
That said, if I become convinced that it is something under the scope of
the IESG, I will of course attempt to inform myself and form an opinion to
the best of my ability, but I don't consider myself very qualified to do so
at the moment.

-Ben

> The change to the LLC may have left a number of assumptions hanging...
> 
> Thanks - Mike
> 
>