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

John C Klensin <john@jck.com> Fri, 02 August 2019 18:43 UTC

Return-Path: <john@jck.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 E617F1207CE for <ietf@ietfa.amsl.com>; Fri, 2 Aug 2019 11:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 tzhWzh8J0_En for <ietf@ietfa.amsl.com>; Fri, 2 Aug 2019 11:43:21 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E383112019B for <ietf@ietf.org>; Fri, 2 Aug 2019 11:43:20 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1htcWN-000PRD-3N; Fri, 02 Aug 2019 14:43:19 -0400
Date: Fri, 02 Aug 2019 14:43:13 -0400
From: John C Klensin <john@jck.com>
To: Michael StJohns <mstjohns@comcast.net>, ietf@ietf.org
Subject: Re: Supervision under previous admin relationships (was Re: RFC Series Editor (RSE) Statement of Work)
Message-ID: <4CB3B217FA38E9562BA64FA2@PSB>
In-Reply-To: <162df5b9-a6fd-69f2-eb7d-36a89ec0afaa@comcast.net>
References: <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> <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>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hr5YqLnB3_xbDbRSJSqkCs1u1IY>
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 18:43:23 -0000


--On Thursday, August 1, 2019 18:55 -0400 Michael StJohns
<mstjohns@comcast.net> 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?
> 
> 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?

Michael,

Independent of the substance of Andrew's reply --which I think
is more relevant than this note going forward -- I think we (the
IETF and its penumbra) actually have a considerable history of
documents that read as charters or legal requirements that are
actually no better than aspirational statements of general
intent.  They include various group charters that have not been
the result of formal EITF consensus calls even if the community
was asked for comment, IPR policies that depend on assertions of
copyright ownership that various of us have been told by
competent specialist lawyers would never told up and patent
policies that don't have explicit agreement of relevant/
controlling parties, at least one procedural MOU that a party
that was then required to sign off on to make it valid wasn't
consulted about, and probably a few others.  We've dealt with a
few other issues by just ignoring them and hoping that problems
would not arise (and, so far, they haven't).    For many of
those issues, the IETF's assertion that everyone is
participating as an individual independent of any employer
affiliations when people are attending with employer support and
employment contracts that effectively say otherwise is a
particular source of vunerability (something we've been
repeatedly told by at least the previous generation of IETF
legal counsel).   IANAL, but my understanding is that as long as
everyone behaves to a reasonable approximations of good faith
and does not specifically challenge them, such aspirational
statements and guidelines are just fine.   

If there were specific challenges involving real lawyers and
specific claims of damage being caused by how we do business,
things could get far too interesting.

The transition to the IETF LLC arrangement probably helps, or
will evolve to help, with some of those issues but is irrelevant
to others.  It may actually complicate yet a few others,
including posing choices between higher overhead costs and
higher-risk or more complex arrangements in some cases.   As one
example from earlier in this set of threads, the question of
"should X be an employee or a contractor?", especially if we are
using more than 50% of X's time, can be a matter requiring
skills HR and employment law advice that is sensitive to
jurisdictional issues.  For an organization the size that ISOC
is now, that is a necessary overhead expense that is spread
across the organization.  If ISOC is willing to lend their
sources of that advice without charging the IETF LLC, that is
clearly a win.  But, should some future ISOC administration take
the position that the IETF wanted to be a semi-independent and
disregarded entity and therefore that such issues are the IETF
LLC's problem, we, and the LLC Board members at that time, could
be faced with more constraints on choices than we would probably
consider ideal.

If we don't like or want to accept that situation going forward,
I suggest that we have a great deal of housecleaning to do, an
activity that would go far beyond the current RSE issues...
perhaps to the point that we would consider them far from the
greatest of the problems that would need cleaning up.

That is not legal advice or even an attempt at a summary of
legal issues.  Anyone who accepts in in lieu of either is likely
to get what they paid for or somewhat less.  It is, perhaps, an
over-long restatement and application of the old principles
about free lunches and about the difficulties of doing business
with one's head in the sand.

best,
    john