Re: [Iasa20] employees and contractors in 6635bis

Eric Rescorla <ekr@rtfm.com> Wed, 01 May 2019 00:51 UTC

Return-Path: <ekr@rtfm.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 9F72C1201CF for <iasa20@ietfa.amsl.com>; Tue, 30 Apr 2019 17:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 kw-H963ohHdu for <iasa20@ietfa.amsl.com>; Tue, 30 Apr 2019 17:51:30 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BDB21201CC for <iasa20@ietf.org>; Tue, 30 Apr 2019 17:51:30 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id h18so12072374lfj.11 for <iasa20@ietf.org>; Tue, 30 Apr 2019 17:51:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sJpuYq2IXBoItvMQ5oqQCfB+ELJ2ntYabrQswWEgop8=; b=KM6teKBXbJmhttZiha3iDyGwxE0Wb6PjBeYuD+51w6T8ZaFfHqPQq0aQV+IoQmB+ik dGu7pPNszyN6Kf9bfui0seImTVsF8xbxuTR2mSgZHCRdGrRJIwPYs4c4puXuEyfc6xJ7 liHWEqWMv9j/rIOZWrsohzqpwxQkm2dws3voGehSSQ+bv/Cj9bvNgDA7y+Bw7Y9Aceqz SjUIAcHE7HlkdHDx3kX5ZO4Q271GfBtZ2d2PwVVgIFjVWl+dNFeJC7OOTHbdf6eXSiJK VRfiYCFr4OIIHLQQn3Oit8CEqwpa22R+SP3iL1c2FzoVtJbmP3wR/56Ajd2sOONK5mx5 Xnpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sJpuYq2IXBoItvMQ5oqQCfB+ELJ2ntYabrQswWEgop8=; b=UcZ2cuMY70QgaQaQJRu7X5vpTYelctvA+bWJaiQ8yPsfIo602iaSAh9xbr839xhw/J ZxMK3Vf9r4WTY8Q78s5thM1MlD948N7vOB1N2EsCF7cK/2TjBqZxvgX2gqoa8l5cNxZn e3wjO6dPjtHBMhowmL1BW7Cuaj1zPJ1ozpXhdA8KmKrXOmrd2KLxXerTN0ioFZ9LVF3L G6lOy0RfXHsKhy3YPRHzMg3VwlrG6tAqDtm8NETgllyHRSS3S4Ci8732nQ+XFW/u2J4h K9JL2T0F5RxkqVoJTpsvtWfQr6F+PQJ/TqlcEUxjwmUkkOtIt5ZuAbSQVQXOmX7fPJah OBBA==
X-Gm-Message-State: APjAAAXJ73Zv8PJQkLYmkW1mOMT/aA+b1uEkcV3c9n/gZP8ASucg0Pi3 2FpNR8jEkFx0T06Z48sulZqfvf2mH8gvhN8woZCnOg==
X-Google-Smtp-Source: APXvYqwhfqX+HgdUIz4KpelXgZ8uulo8MZkv8ds3g6JuCW0A4snly/fyEY4UuRFikLmaLYro8lIhVRFMrL19yT0Wi78=
X-Received: by 2002:ac2:53b2:: with SMTP id j18mr1046503lfh.78.1556671888215; Tue, 30 Apr 2019 17:51:28 -0700 (PDT)
MIME-Version: 1.0
References: <20190430224943.D666020132688F@ary.qy> <7d6c9ac4-d4b5-8e94-b555-29facb771d6e@cs.tcd.ie> <CABcZeBOdgy1R54W20XdXgLjeoCsEvrOaoMMG+S3HhOw9D-w_fg@mail.gmail.com> <4c8b07c5-41ae-34a5-38c0-6175cf2506c2@cs.tcd.ie>
In-Reply-To: <4c8b07c5-41ae-34a5-38c0-6175cf2506c2@cs.tcd.ie>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 30 Apr 2019 17:50:51 -0700
Message-ID: <CABcZeBPh6dnXGMrnR1ZdHU9Te6uC=39mYPxPaw7N0HV-6sAjOQ@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: IASA 2 WG <iasa20@ietf.org>, John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary="000000000000ede5ec0587c8eaaf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/j4kEa7rNgO2jTFx3DPfZIs0hgcg>
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 00:51:33 -0000

On Tue, Apr 30, 2019 at 5:34 PM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> (Sorry, ignore the last mail, hit send too soon.)
>
> Hiya,
>
> On 01/05/2019 01:11, Eric Rescorla wrote:
> > On Tue, Apr 30, 2019 at 4:02 PM Stephen Farrell <
> stephen.farrell@cs.tcd.ie>
> > wrote:
> >
> >>
> >> Hiya,
> >>
> >> On 30/04/2019 23:49, John Levine wrote:
> >>> In article <3e8222ce-45dd-41c2-71cd-1adf99760238@cs.tcd.ie> you write:
> >>>> ISTM that the fixed-term with re-appointment model for
> >>>> the RSE role inherently means not filling that role by
> >>>> hiring an LLC employee.
> >>>>
> >>>> Where am I wrong in the above?
> >>>
> >>> It depends where the employee is.
> >>
> >> Yes. As I explicitly said in my mail.
> >>
> >> My point being that we don't want to constrain selection of
> >> an RSE based on geographic variations in employment law. For
> >> this role, that could be a significant constraint.
> >>
> >
> > This seems like an argument for giving the LLC *more* latitude here,
> > because as this discussion has shown, there are places where it's
> > advantageous to have people with whom you have a long-term
> > engagement be a contractor and others where it's advantageous
> > to have them be an employee.
>
> I interpret things differently. The contractor arrangement seems
> to me to fit the RSE role regardless of geography.


But this is precisely the point that John, Richard, and I have
been making, namely that it's actually *not* clear that the contractor
arrangement is a good fit for the RSE role in certain jurisdictions.


In contrast
> employee arrangements seem like a total misfit for at least
> countries like Ireland (perhaps most of the EU?). And I do not
> want the LLC to have fictional flexibility that really represents
> a cumbersome constraint when it comes to RSE selection.
>

In what way is this flexibility a constraint.

> So, I'm not sure I follow your argument here, which seems to be that
> > you think we ought to constrain the LLC in this respect.
>
> I do think we ought do that. Sorry if I've not explained it
> sufficiently well.
>
>

Yes, I get that, but it doesn't seem to follow in any way from the
arguments you are advancing.


>> Here in the US, if you hire a person as a contractor but the the
> >>> nature of the job is more like an employee (the so called IRS 20
> >>> questions), the person can file an SS-8 form with the IRS to ask to be
> >>> reclassified as an employee.  If the IRS agrees, the employer has to
> >>> pay unemployment and social security and medicare taxes for the
> >>> employee, retroactive to when they were hired.  It can be a
> >>> significant financial risk for the employer.
> >>
> >> Yes. But the RSE role has not been "more like an employee"
> >> at all.
> >>
> >
> > Without taking a position on the nature of the RSE,
>
> I believe the IETF has a position on that. (Not that the IETF is
> the only entity who may care about the RSE role etc...)
>

Sorry, what I mean to say is that I am not taking a position on
whether the IRS would judge that the RSE was actually an
employee.

-Ekr