Re: [Iasa20] 6635bis

Richard Barnes <rlb@ipv.sx> Thu, 25 April 2019 18:22 UTC

Return-Path: <rlb@ipv.sx>
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 E1BCA1200F9 for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 11:22:46 -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=ipv-sx.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 Vw2o2KqeVcwT for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 11:22:45 -0700 (PDT)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 24519120074 for <iasa20@ietf.org>; Thu, 25 Apr 2019 11:22:45 -0700 (PDT)
Received: by mail-ot1-x32e.google.com with SMTP id d24so348477otl.11 for <iasa20@ietf.org>; Thu, 25 Apr 2019 11:22:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UJscLJkk7kMy2G5/x8mNQxRvh4N6Eua/xUKG7PA4U7E=; b=qju9DQjjC/MpYeso37yoL7Mlr4oY8nGzOG6l0c3lj5ZzshOYPjkZjhfMiqGRF0SNPm iIB6ra3XpuDRDyxbmvXx/7HjwqeQRz4+h128OhVQAW4xZhL29RnUQYik6tjsqo6z0AD3 pD1Bywukl9OUE1Q6UWvBGyd5cl7ABCbX+pvgajO+9je+WJQuHrRfP2jdkckGxHEdQqMp 56H7GQo4vnU2gHcHNv80LoZCN2ClHTfA0pxb6CXEciPzDEmTVQRsEaDxKi9s8YERiImH L6gaasfF/Vuqcs9QprwWsCbus7jEU4QE3vcLicfd8MBurgTA0mTrEDDI2NFSOQgzKiJg EOXA==
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=UJscLJkk7kMy2G5/x8mNQxRvh4N6Eua/xUKG7PA4U7E=; b=C9eIE6z3WukdU0T7S06KpNeVUJgjjdBk/ITFHBXWzYpFaoNIw3T1Dg5KYFa+LcVfga O+1Sa/rGAiHcdeBmfwZHTCMfl5fjzyUhxs2Nj14fq3eSIIAh4AmONyS/ZeGewKSXcUDr 3RbSskkzY6wk9BFTH1I2sKa7EPpSVG/PnJvAbxrMNyX5MdULjezLi8g1U8jPpYcw7GG7 NlArLR3Rg0F+9nqOZDpszSQWE6UFQIzeiczizaYTHUF5Ge8T1bxFU4Izh/gtkvI5goGk 9SCYS6yAKZZPW6kLxf1ZzolQQuR8xSbHWmxeG0Wadb2yhmiixSRvBW1aTzf3IFjJlq7L FATg==
X-Gm-Message-State: APjAAAWWjQLwj5E3mHLXvyEUc9N5psbPI7mmszp3Us4xjiHDEnNpK/Xf nPNR27OiWU5F2OBnXCxXkEo6Dtt+oGGOwebNcNph4w==
X-Google-Smtp-Source: APXvYqwL8Bg4iobSTCSCQxnrECAGor9rVQ2G41X2F0326EsVOlJGacO1gVAtVGqci0CNwLGlF3GOtQHtpq54Tc5cGcM=
X-Received: by 2002:a05:6830:12d6:: with SMTP id a22mr23190335otq.331.1556216564402; Thu, 25 Apr 2019 11:22:44 -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: Richard Barnes <rlb@ipv.sx>
Date: Thu, 25 Apr 2019 14:22:19 -0400
Message-ID: <CAL02cgS-QzkfDrYyLRD_T8beNZ2Zg_c1F4jnZDCSk=Wf67qnSA@mail.gmail.com>
To: Sean Turner <sean@sn3rd.com>
Cc: IASA 2 WG <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000083e15205875ee7c8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/mKdfEhD53b3Ke22pMAZrtjHknxg>
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:22:47 -0000

Overall, this approach seems sensible to me.  The point of this document is
to describe the roles involved, and to minimize surprise with regard to how
the LLC arranges for those roles to be executed.  It should allow the LLC
flexibility where there's not a compelling need for constraint.  The
difference between employee and contractor does not seem salient in terms
of getting this work done.

--Richard

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?
>
> Cheers,
>
> spt
>
> PS - I am sending this message right before some family-related activities
> so I might be slow to respond.
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>