[Iasa20] 6635bis

Sean Turner <sean@sn3rd.com> Thu, 25 April 2019 18:14 UTC

Return-Path: <sean@sn3rd.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 5CEB912006F for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 11:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=sn3rd.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 HRTumnbiiqAi for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 11:14:36 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 52085120033 for <iasa20@ietf.org>; Thu, 25 Apr 2019 11:14:36 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id p19so304923qkm.10 for <iasa20@ietf.org>; Thu, 25 Apr 2019 11:14:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=KrScFqQQ/Q4tRC77yXX+azaEOI2DA2pCZUPG5W09mYw=; b=M9PyxlVr9IpWzG28m4fb82J8V2ygLaW2ZTB+mO2YVtfm+8sicZcuJXP0NOTVQVcN3F RDFlx28mmD8oWPYdJmpE9ejwCMXocZjSMW1A5SFwEl98cBbswYxJwfQSHXw1uUZWlsep 9eNx9rJ6JbfJJFfuk9g5VEEwnzI90PXtKw7lA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=KrScFqQQ/Q4tRC77yXX+azaEOI2DA2pCZUPG5W09mYw=; b=YS/U7RUgSFsypJyPEyw7DMqf8ml2I1T1xrW0GhzuxaajOmn9LCtZxpiYgKmRmjV7XE 2CnGF7HlJtVz/0KCmROACAXC1sQJCbBy310JjesTokdKp60ajbNiohHh5YFaMAe7A92p BrQ1ayCwlxU7Uauoh1i2lzZxCn5/e7NqUjzLnb9UTutxrGNXCvHKy3inTJFj9U3DIJNr RD2nttR/QDaUCK9+g1hFX2ghw0xE/4+ds8pSqr0f8Ty6V5hipEq2BsFn29Uqj/+lQjsM 3S5RMqMQgqfF9tJZwqOptP0eoz23JOhSz0cMoJnnZG+aTP3GX27ebfyqXhfngx4/mPdO 62pw==
X-Gm-Message-State: APjAAAXKLl7C85OgJKy3cIYyK2PlyrWtrPbm6cD3A1p+oBF+2ba1iK4G hKFV+4Ku5w/oUSTdoywFdrtZkRPKtrM=
X-Google-Smtp-Source: APXvYqwl9tEvZfZABJYIt3FApY41dS//Gj/FS+UEAlKwTqpWpMIEQR5MQHvNyq5uojpOBi/QnUAaEg==
X-Received: by 2002:a37:4c8e:: with SMTP id z136mr30088816qka.149.1556216075272; Thu, 25 Apr 2019 11:14:35 -0700 (PDT)
Received: from sn3rd.lan ([75.102.131.36]) by smtp.gmail.com with ESMTPSA id e6sm10861374qtr.56.2019.04.25.11.14.34 for <iasa20@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Apr 2019 11:14:34 -0700 (PDT)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Message-Id: <CCCFB260-660F-4CB9-AA4F-60F8B88465CB@sn3rd.com>
Date: Thu, 25 Apr 2019 14:14:30 -0400
To: iasa20@ietf.org
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/dWy-8ui6TV2uovXTNotgpc2051w>
Subject: [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:14:39 -0000

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.