Re: [Iasa20] 6635bis

Ted Hardie <ted.ietf@gmail.com> Thu, 25 April 2019 19:00 UTC

Return-Path: <ted.ietf@gmail.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 01B05120689 for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 12:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=gmail.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 7saRXG-sU0BP for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 12:00:40 -0700 (PDT)
Received: from mail-it1-x12d.google.com (mail-it1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 E32DC12061E for <iasa20@ietf.org>; Thu, 25 Apr 2019 12:00:39 -0700 (PDT)
Received: by mail-it1-x12d.google.com with SMTP id e13so1875608itk.4 for <iasa20@ietf.org>; Thu, 25 Apr 2019 12:00:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ngv2F6BWn5sWhiTJnB+I3EsNa30FILeZLZVhfUWDC50=; b=JpP4fwZZ7rqNySKohFWdQOmcdKcaNZgd5p1a+gl0N+D7iQKitS9hlOP6QuK1fsUmEB TTBVYTdlTcJtRqIMAZnSGCFm3Vsm3NlsHUE+dj0PTfdMzQDIhTbpjn/QRnKRmTqy3VHV JwEwshe22N5hlEODkTeFnwvNfhY5cVHD1PijaPV+z4TlyacBz1F/KPzmBYUzDgKV4NDq 3X4Z4NhO/ZusOZpm9bnQUkwYlBmr6nw8I26noS8hezuQMja25mepkqLH9MFlbxqzBdXv oihQVF2I8FL09oXz8Ziu2slUo3ct/er+gG37ZS2PghB1vPk5/rZ9nZwu39kVAB47L5Cm 0CYQ==
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=ngv2F6BWn5sWhiTJnB+I3EsNa30FILeZLZVhfUWDC50=; b=GbvgekVAUEOuZMFTYz8nHplkechiva7yvqRQXrAOo/6LakvZEKktsTyClOU+4U/3rU NAIeX2Z7kpgNPv8HgPGYqA6YeAK9rhHmtlUJg16SJzHIVm1nn8tX0hLcG6bpzABC+sRW jD+NsPT8WxosxqlDisK/teEYxH2Zzv3hjArXRmYBJ82t9ukeJkytcXT0pQGElMCMDzsR /VacfXXQ0Gozo3C/ySViQpS3Di6YxKavMCkagLQLpz71o459K+u48gYpciJU4Kdi0dmQ odk/AAsnZ8rgzU4asd6bB+JLXmXQPQ/z/5vfLFe6RNFyR0cu1wsFvnqIKWQiv2zfvWYI g1CA==
X-Gm-Message-State: APjAAAXo0TV8Qjq73QaiOFLVUfRLVPwwvX5G3l8K/pMpFHzyGQc211cX Qmq3nPZ4FRVfibh/C/QN17pZ2wfBpyxPl4FrfP8=
X-Google-Smtp-Source: APXvYqyXtkq3BB+551lbseb//Li9fmp70rPMQ62esiwRfJ8fGqQsPOU/E8kkOiziBQJnywlolHxgjuxoGkyLz4ORXfk=
X-Received: by 2002:a24:5f8c:: with SMTP id r134mr5073724itb.110.1556218838707; Thu, 25 Apr 2019 12:00:38 -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: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 25 Apr 2019 15:00:11 -0400
Message-ID: <CA+9kkMDpCkC8cwD7W3PYzFtxOn84=x1X-u4qu2ABwoBtxQi_+A@mail.gmail.com>
To: Sean Turner <sean@sn3rd.com>
Cc: IASA 2 WG <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000012f22105875f6f4d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/a0GPhEUNTl4KkGxhRkS4yrIJwHU>
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 19:00:54 -0000

A comment in-line.

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.
>
> First, I really appreciate the LLC (or you as an individual) asking this
question of the community in this context; it's an important enough to get
community input on rather than deciding off-line.

Second, I do think that having both models be possible would be a useful
change.  I certainly don't want to remove the current model as a
possibility, but being able to have an employee relationship may make it
easier to be flexible in the future.

regards,

Ted



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