Re: [Iasa20] employees and contractors in 6635bis

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 01 May 2019 01:03 UTC

Return-Path: <jmh@joelhalpern.com>
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 59F791201CE for <iasa20@ietfa.amsl.com>; Tue, 30 Apr 2019 18:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 z9TkmZ8mMOBx for <iasa20@ietfa.amsl.com>; Tue, 30 Apr 2019 18:03:34 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 B49341201CC for <iasa20@ietf.org>; Tue, 30 Apr 2019 18:03:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 44v0Wp4SJzz1Y4kw; Tue, 30 Apr 2019 18:03:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1556672614; bh=vY7wqEXIPWM5B4R+VZp2CzeH9Um+jgaRM4WnMEyldLI=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=dPp2F7Gx3GFdcpn40YNGvEx/jF17tyVdRamqskiuWJrVVWIJcvQR+c/HTkSKs/gZu jUOXtAYu3OuzqXQK0BYO3uvS2m1KBeCFx2isYsNNidKgNbNAMEjKiYliW9sL38OHEu Z5hzXSXW9WRK3xlJIZT6BnDVn8AxxGB29G4r/BMo=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 44v0Wp12lhz1Y4ks; Tue, 30 Apr 2019 18:03:33 -0700 (PDT)
To: Eric Rescorla <ekr@rtfm.com>
Cc: IASA 2 WG <iasa20@ietf.org>
References: <20190430224943.D666020132688F@ary.qy> <7d6c9ac4-d4b5-8e94-b555-29facb771d6e@cs.tcd.ie> <CABcZeBOdgy1R54W20XdXgLjeoCsEvrOaoMMG+S3HhOw9D-w_fg@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <bf38281a-0fe2-0e06-276f-cf926d3466d4@joelhalpern.com>
Date: Tue, 30 Apr 2019 21:03:33 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CABcZeBOdgy1R54W20XdXgLjeoCsEvrOaoMMG+S3HhOw9D-w_fg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/BIOSK_dulzbNnWRbsggtFHv7dVU>
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: Wed, 01 May 2019 01:03:36 -0000

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.

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
>