Re: [Iasa20] 6635bis

Joseph Lorenzo Hall <joe@cdt.org> Thu, 25 April 2019 18:19 UTC

Return-Path: <jhall@cdt.org>
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 5A3D9120074 for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 11:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 bJwInksPDK1i for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 11:19:43 -0700 (PDT)
Received: from mail-it1-x130.google.com (mail-it1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 30A15120291 for <iasa20@ietf.org>; Thu, 25 Apr 2019 11:19:35 -0700 (PDT)
Received: by mail-it1-x130.google.com with SMTP id y10so1701968itc.1 for <iasa20@ietf.org>; Thu, 25 Apr 2019 11:19:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=voE9au5E7vGP9+4lBEuYnQFD1r0pGeRDjVR9eKP/Z9A=; b=poYfiZskxgSVdxyVv8mVMQxxkLiD5j+Bs4/09M+823DuqgDoygb/xYfL8LKCzS8lY0 K3SnPQR5uBj3riPUIT43TSnadDc9+UHNwrx9lLrcltZzhzttqSPaZZr/R8OMgKgWLpoD hP7JfUzbbYk9xB2eiN7lw/mgAa/khNY/rfOEA=
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=voE9au5E7vGP9+4lBEuYnQFD1r0pGeRDjVR9eKP/Z9A=; b=jGICTG91F2NoY0rlu8jxUlZjjF549+a4/BCiV+1cKgZp5uJfsRYtQPO0Rcg9C7AlzG eeOvDa+ROSN+reGvlO33IH6ue1llxOSvZHojcHenh8lCvO4FWh+oPLYRG90IYwUC7JpM 8PcUd5UAy3WvU7p5VsreEzu3pSJQbbHewRg5SS34xqmXkqqky+Q+euw/F6AjO7UXEmHa SN1tW8Mvbc3aancIsRZPS6jXDr/BFtlP6wsmd0NjONbmowyaf0NYqHfw9TuuuhM+ITiK akTHmvJYToM80bqodBJViWDbpVzZBe4sZzvpKWSu8V2ZX1pGn0mA1iSh9TewOOyOQObK zrsg==
X-Gm-Message-State: APjAAAXu2WQnCjWjYvNKdikwGec0rLgm7y2Cm4BX3ccgRzAA00bcs7GP n6cTIPD+KVZfy7E/AIqoiQ1wuL8uzarycjxXko+cwQ==
X-Google-Smtp-Source: APXvYqxDG4CQ+QsFrQPiUsiIY2eUQQehIPwF44Da8OALb/C1ioRudBhZD2DSqbYByIZtQCr2ggFNsWE7fmqPHohPHHo=
X-Received: by 2002:a24:3d4a:: with SMTP id n71mr5237763itn.55.1556216374134; Thu, 25 Apr 2019 11:19:34 -0700 (PDT)
MIME-Version: 1.0
References: <CCCFB260-660F-4CB9-AA4F-60F8B88465CB@sn3rd.com>
In-Reply-To: <CCCFB260-660F-4CB9-AA4F-60F8B88465CB@sn3rd.com>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Thu, 25 Apr 2019 14:19:22 -0400
Message-ID: <CABtrr-WrS=P7UmF_FwgGG90LNPbksgY-MSLiF4fyhJMsLzyL9Q@mail.gmail.com>
To: Sean Turner <sean@sn3rd.com>
Cc: IASA 2 WG <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002c9ca105875edca3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/wXaVriuxAuCDczHcFFpsq-Sh6Q8>
Subject: Re: [Iasa20] 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, 25 Apr 2019 18:19:46 -0000

On Thu, Apr 25, 2019 at 2:14 PM Sean Turner <sean@sn3rd.com> wrote:

> Hi!  While I am not sending this message on behalf of the IETF
> Administration LLC, I have to admit that I am reading the IASA2.0 I-Ds with
> more interest as an LLC officer because I am somewhere nearer the front of
> the go-to-jail line if something goes terribly wrong ;)
>
> With this in mind, after reading many of the the IASA2.0-related I-Ds the
> simple IAOC to LLC terminology swap totally makes sense.  For
> draft-ietf-iasa2-rfc6635bis, I am wondering whether more should be done.
> Specifically, I am wondering whether the language about how the RSE
> services are delivered should be loosened or at least made internally
> consistent.  As I read it, draft-ietf-iasa2-rfc6635bis does include a
> reference to an “employment agreement or contracting plans, as appropriate”
> as it pertains to the RSOC working with the LLC concerning RSE services.
> But, the rest of the draft, at least to me, reads as if the LLC will
> contract these services out with no wiggle room for an employee to do them.
>
> The slant towards contracting made sense prior to forming the LLC, but now
> that the LLC has been formed these functions could be performed by an
> employee.  For any given role, the LLC might find it preferable to have the
> role filled by an employee versus a contractor for the purposes of being
> able to offer better benefits, to more easily comply with employment/tax
> law, or for other reasons. The original IASA model didn’t offer as much
> flexibility since hiring decisions were ultimately ISOC’s.  If the language
> in the draft was tweaked to accommodate both contractors and employees then
> this document would not, in mind at least, unnecessarily restrict the LLC.
>
> Before I submit a list of potential edits to this list for
> draft-ietf-iasa2-rfc6635bis, I just wanted to see whether these type of
> changes would even be palatable?


It seems important under the new model to ensure it could be a contractor
or an employee, so I'd think that's pretty palatable and wise.

best, Joe