Re: Supervision under previous admin relationships (was Re: RFC Series Editor (RSE) Statement of Work)

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 02 August 2019 16:48 UTC

Return-Path: <ajs@anvilwalrusden.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 636221206CF for <ietf@ietfa.amsl.com>; Fri, 2 Aug 2019 09:48:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=OUG6suTk; dkim=pass (1024-bit key) header.d=yitter.info header.b=KSvUvsSk
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 mICRKxs--I2v for <ietf@ietfa.amsl.com>; Fri, 2 Aug 2019 09:48:33 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DF331206C6 for <ietf@ietf.org>; Fri, 2 Aug 2019 09:48:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 8471CBCCC7 for <ietf@ietf.org>; Fri, 2 Aug 2019 16:48:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1564764512; bh=g77uWj9DIZVWzKiKIZq9rSkqWkR7Qof3c4L/i2Wg71w=; h=Date:From:To:Subject:References:In-Reply-To:From; b=OUG6suTkNm+ZbWQmjqgbtv8Nq7NCeGTwGmNjeEDjUGXhz9MVnLgPvAoTkQD2s0Xn6 vz4z8BXE3C2Fsk22L6JsNyI1s4EEauQRq0uXo7NOOXChSskIBmrYB+f/+6bdeKxY0x 5JXGOc7k5wRxmyVTZI3/VrhNikF46jVjVke+Kb/M=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jnJksC5MQwMM for <ietf@ietf.org>; Fri, 2 Aug 2019 16:48:31 +0000 (UTC)
Date: Fri, 02 Aug 2019 12:48:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1564764511; bh=g77uWj9DIZVWzKiKIZq9rSkqWkR7Qof3c4L/i2Wg71w=; h=Date:From:To:Subject:References:In-Reply-To:From; b=KSvUvsSksaRe4aKDHSr60/AS1lwteKdoYFak5xHhEW20bSJ2Da91/xYIF9DkvuvPA kQqWuwfzGXBLdwVEOuyww4oluKf9ZKykUloUr6vNztTvvS1mPMTFbUhivbr4tn70Cn lYx/RTKKY3Pj7tjBddLKFuLejyOA+kkend7mMFU4=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Supervision under previous admin relationships (was Re: RFC Series Editor (RSE) Statement of Work)
Message-ID: <20190802164828.whsvwy7ozbeyx57j@mx4.yitter.info>
References: <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> <m2d0hoskmk.wl-randy@psg.com> <20190801213032.m3nkmqioyuxhzed3@mx4.yitter.info> <162df5b9-a6fd-69f2-eb7d-36a89ec0afaa@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <162df5b9-a6fd-69f2-eb7d-36a89ec0afaa@comcast.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JL_PXrx8Uc0T8C1OaFiBzGfNlFU>
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: Fri, 02 Aug 2019 16:48:35 -0000

Hi,

Still employed by, still not speaking for ISOC.

On Thu, Aug 01, 2019 at 06:55:20PM -0400, Michael StJohns wrote:
> 
> So you're basically saying that what was in 4071 didn't reflect the actual
> legal landscape.  E.g. the authorities granted to the IAOC to
> manage/control/evaluate the IAD didn't really exist and there wasn't
> actually a formal agreement with ISOC to allow for the setting of
> performance goals or even hiring and firing?

I don't know how there could have been a "formal agreement" with ISOC
for this, since formally the IETF (and therefore the IAOC) was an
activity of ISOC.  It'd be like having a formal agreement between a
department of a corporation and the corporation itself.

Regardless, the basic idea was that ISOC was in fact responsive to the
IAOC's requests to the extent permitted by law, but the practicalities
of making the oversight work were much more convoluted than one would
like and resulted in these quite bizarre situations in which the
official version of what the employee received was not something to
which the nominal oversight body actually had access once that
official version was completed.  If one thinks about this for even a
second, it is obvious why: we all want our employment records to be
handled as confidential information by our employers, nobody on the
IAOC was under an NDA to ISOC, and only of them was an employee of
ISOC.  So there was no way to hand employment information for an
employee of ISOC to IAOC members, except of course the ISOC CEO.

I'm surprised any of this is news, since I think we went over it in
some detail during the iasa2 discussions.

> And I seem to remember in one of the message chains a comment that the 6635
> language that said "evaluate the RSE" got short shrift from ISOC as well? 
> So, from the ISOC's point of view, as the contract owner, at least part of
> 6635 did not reflect the actual legal landscape - correct?

I don't know about this.  The relationship among parties in a
contracting situation is quite different than the relationship among
parties in an employment situation.  In the case of the RSE, the
contract (which is available for anyone to inspect at
https://www.ietf.org/documents/232/RSE-2018-Independent-Contractor-24Oct17-Public.pdf)
makes it pretty clear that the Internet Society was acting at the
behest of the IAB and RSOC.
 
> Now you have me curious - what were the dates that the RSE and IAD
> contract(s) were assigned from the ISOC to the LLC and accepted by the
> individual contractors?

The IAD contract was never assigned from ISOC to the LLC, because the
IAD was always an employee.  But the IIAD contract was transferred
along with the RFC Editor contract and everything else associated with
this on 27 August 2018, according to
https://www.ietf.org/documents/181/IETF-ISOC-TSSA-Redacted.pdf.

The contractors didn't have a say in this assignment, since such
agreements contained an assignment clause permitting ISOC to assign as
it wanted.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com