Re: [Iasa20] employees and contractors in 6635bis

Alissa Cooper <alissa@cooperw.in> Thu, 02 May 2019 02:22 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D14FD120058 for <iasa20@ietfa.amsl.com>; Wed, 1 May 2019 19:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=HX45IHF9; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=sSvo5ugN
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 yHoi2DxNBFHy for <iasa20@ietfa.amsl.com>; Wed, 1 May 2019 19:22:38 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF645120033 for <iasa20@ietf.org>; Wed, 1 May 2019 19:22:37 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 306DA222E6; Wed, 1 May 2019 22:22:37 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 01 May 2019 22:22:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=Q fFepxIgPVJaJkhcqsE1i3oTXBVrgApYbZSzt5fAunU=; b=HX45IHF9crDMaoxaw E/rLXaxpd4UhluIaE9KVXH0spSnpMDl/X8VdUpRNertJ3SfBSpLLm2FOe7Rdj9Qu ld0VuKLgPJKkbLbZhQuxz23U0m4CLiV7h4zu6P82PjqRX1gL9N6A8kXBb+esxKZd fKmeIWs3X1rj444MxdV2i9tPEvXQ0fjlrGQNI38gnUY2hkui02FpdS7eaDkgNF7s AXSYdQSwD4Q4t1L6sCYQLd0kLsupeeg12CBsW0sKX40mr8Us/+vU8zw83sbr8aFC 1p16LlvpC7WtLzVgbhc2B6YU7Xh0aZciFZOaODZGSZ0b+4x2rd6GiEIOqfCsDnm4 77Wlw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=QfFepxIgPVJaJkhcqsE1i3oTXBVrgApYbZSzt5fAu nU=; b=sSvo5ugN+XqpLD6gLCeZfCtyPNUN2UXMah+wHQpVWtmErpImUDsjbX+l6 cfL/wm1hSK9LNOK7zq1jABvqz064WqCp2RY5hk8t8mINBQcpXZ2IKgy5TFC/VVGj sO+ledprMCDzN3CfLEBvVe9uetss96lFAEl6RgIlCCSr+wlZubVfqyNFLPPteJYw lritp5a1WjOGVo4vwXQSabsyLTCr2oiwsYiDowCfycrMLqLJoUH6s7cR3ORtGgM3 uncFHcCHiVBj/gZJoDGt6mNewKwoEkxJtv5jLoJVeM06u6FwTgrgXvtGInZtIRbn OVkpoiu3jf2PpIPf0hSq7r/p2JeGg==
X-ME-Sender: <xms:bFTKXHKTENEyWqMeUxbDa_PhD0GJunWZt6dzQovmTkg45bY2lEEkog>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrieekgdegkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculddqhedmnecujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdt jeenucfhrhhomheptehlihhsshgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvg hrfidrihhnqeenucffohhmrghinhepihhrshdrghhovhdpihgvthhfrdhorhhgnecukfhp pedujeefrdefkedruddujedrleegnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhish hsrgestghoohhpvghrfidrihhnnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:bFTKXMa0eE1q7S2KQV7MdhtjqaHRxkeH7B0J1tn8b0ecWaCOU7CfyA> <xmx:bFTKXFCX9hab-t5ehTJAUpfTP5h4yQOTAwssyaWCqd-zVQSegrmfxA> <xmx:bFTKXOXe6P9AWy2vsmsyhWN2WleveaasSANW95Aa3UR8Wh6COwhstA> <xmx:bVTKXJ2aPTChxJRd2s6WQk6G32YRqKs35M8klCz6X5UtIcMvQBf86A>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.94]) by mail.messagingengine.com (Postfix) with ESMTPA id EF0DDE4067; Wed, 1 May 2019 22:22:35 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <bf38281a-0fe2-0e06-276f-cf926d3466d4@joelhalpern.com>
Date: Wed, 01 May 2019 22:22:35 -0400
Cc: Eric Rescorla <ekr@rtfm.com>, IASA 2 WG <iasa20@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A5D48C2-9732-4B16-A2FE-D47C9F0F654A@cooperw.in>
References: <20190430224943.D666020132688F@ary.qy> <7d6c9ac4-d4b5-8e94-b555-29facb771d6e@cs.tcd.ie> <CABcZeBOdgy1R54W20XdXgLjeoCsEvrOaoMMG+S3HhOw9D-w_fg@mail.gmail.com> <bf38281a-0fe2-0e06-276f-cf926d3466d4@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/SIVBcEgRhysUOoVjnacQNDKWrlM>
Subject: Re: [Iasa20] employees and contractors in 6635bis
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2019 02:22:40 -0000


> On Apr 30, 2019, at 9:03 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> The ISOC, when I was on it, worked with the HR people at ISOC to make sure that we stayed well clear of accidentally turning the RSE into an employee.  While it introduced some complications, most of those were involved in understanding the rules.  Which are needed no matter what you do.

One aspect to note is that this is actually a different analysis in some ways for the LLC than it was for ISOC. One of the considerations involved in interpreting the IRS rules has to do with the extent to which services performed by the worker are seen as a key aspect of the regular business of the organization. ISOC has a much broader waterfront of “regular business” that it conducts compared to the IETF LLC, so arguing that the work performed by the RSE or certain individuals supporting the RPC could be harder for the LLC than it was for ISOC.

Alissa

> 
> Just for clarity, the reason for the care was that none of the RSE, ISOC, or the RSOC (or presumably the IAB whose policy direction the RSOC follows) wanted the RSE to be an employee.  Which is consistent with the wording in the RFC approved by the community.
> 
> Yours,
> Joel
> 
> On 4/30/19 8:11 PM, Eric Rescorla wrote:
> ....
>> Without taking a position on the nature of the RSE, I'm not sure
>> that you and John mean the same thing when you say "like an
>> employee". See, for instance:
>> https://www.irs.gov/newsroom/understanding-employee-vs-contractor-designation
>> Note that the questions here are not largely about how *we* think of
>> the role but rather about the structure of the work and of the relationship.
>> -Ekr
>> _______________________________________________
>> iasa20 mailing list
>> iasa20@ietf.org
>> https://www.ietf.org/mailman/listinfo/iasa20
> 
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20