Re: [Iasa20] employees and contractors in 6635bis

Eric Rescorla <ekr@rtfm.com> Wed, 01 May 2019 00:12 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 7E3D21203F6 for <iasa20@ietfa.amsl.com>; Tue, 30 Apr 2019 17:12:04 -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 waLU5wAnxvqm for <iasa20@ietfa.amsl.com>; Tue, 30 Apr 2019 17:12:02 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 3AC851200DE for <iasa20@ietf.org>; Tue, 30 Apr 2019 17:12:02 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id w12so2669896ljh.12 for <iasa20@ietf.org>; Tue, 30 Apr 2019 17:12:02 -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=w65qvNNZxYkNu17nfVgjCPzFp7U/4Xxyc3tQcaebEsQ=; b=nqXPEfMo0QQmY0J586b03NWVqMgfHjBf7DTCPGDGCWG1JG3AgesM5CV+n+YhmL3C7h z2JkbB9Qx+mbGXGB0Jsj0e/vNAE7Tyv9kg6CQGp4cNLYVF6Da/fM0gANm+z+o3bWWs0a fPHsnZBpOOMJjsQvPQejGJkyMElem4LcLcIWU8ZETrYEPnRs9aahPvQbQ94NZX6lZiPb EJwzqTQeywIzWlgPuqkZss2Fo17Q8+sV3pUBvsgVrjz+oMQqup4VedGtTCBlAs0AroKy bbxlmwLcqg6GZpuTeei4Xll2x6eMhXz387asS8QZYu92IE2mP4BtgBkjRYHeP3KP3YbO vAFw==
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=w65qvNNZxYkNu17nfVgjCPzFp7U/4Xxyc3tQcaebEsQ=; b=f0KASrGBWIzovdCdOUgAMcyI53njQgNm11ajX0tMu1olPFjFtMYtxhTatwxsJ7BxA2 3FtdVNik/8OKaBybGsB0z9FBZ5n5y+ZS5QBTGtBAkA3s/IQZf10YvrEwKqCEmCha5we9 yqIWaEbnT4NmxXbkqLVTcvr91xqTk63jy51F/mCw9jmnHb05/4Z1qsllRKAo6wCGUMT7 8aS+tnBo7LJE+g2GGkYRraMBXMboUR0drZGuaNHY9TtBODWtB86ggLM9YEb6J0fyZ2/E FSinDR9nfE4uTYtHj7fZggFfqK/85tyIftb60x0/k2Y+o7ZT5Bqq5dE/KZ/jHuJ9ZNU1 lj4g==
X-Gm-Message-State: APjAAAVbJWgJ2kbEq7p/F/QGoQvgFPGENIJfvaIhy7BuZAQ/1tH34DSp 3/lHQ/mQ+Z7GGuRzrCp1zXDK7Rl3BNi6igZj3QJL4w==
X-Google-Smtp-Source: APXvYqyEYo0zU7Gs5tVeiSUpHxPHL5wEUJ+23ACcN165Ao/pDUEDehDX1AdwcDXbMX8UvwHfXS7GdQo/ANv5ThioqNg=
X-Received: by 2002:a2e:9c89:: with SMTP id x9mr19194299lji.28.1556669520257; Tue, 30 Apr 2019 17:12:00 -0700 (PDT)
MIME-Version: 1.0
References: <20190430224943.D666020132688F@ary.qy> <7d6c9ac4-d4b5-8e94-b555-29facb771d6e@cs.tcd.ie>
In-Reply-To: <7d6c9ac4-d4b5-8e94-b555-29facb771d6e@cs.tcd.ie>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 30 Apr 2019 17:11:23 -0700
Message-ID: <CABcZeBOdgy1R54W20XdXgLjeoCsEvrOaoMMG+S3HhOw9D-w_fg@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: John Levine <johnl@taugh.com>, IASA 2 WG <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c9bd940587c85de0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/ctYJ2QSJeCvQxwx6rBGQpRsocHM>
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:12:05 -0000

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.

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.


> 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'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