Re: [Iasa20] IASA 2.0 outcome properties
Jari Arkko <jari.arkko@piuha.net> Fri, 21 April 2017 13:47 UTC
Return-Path: <jari.arkko@piuha.net>
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 56B231205F1 for <iasa20@ietfa.amsl.com>; Fri, 21 Apr 2017 06:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 4Yn7OPEz-r5w for <iasa20@ietfa.amsl.com>; Fri, 21 Apr 2017 06:47:12 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id 1D3631242EA for <iasa20@ietf.org>; Fri, 21 Apr 2017 06:47:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 397AF2CEF7; Fri, 21 Apr 2017 16:47:10 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLBTCQ-9k_nG; Fri, 21 Apr 2017 16:47:09 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTP id A520A2CEA0; Fri, 21 Apr 2017 16:47:09 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_8EE98BD8-13AA-4547-85FA-B33E3B556365"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <ac959891-8992-f87c-d730-e815a7542a72@cs.tcd.ie>
Date: Fri, 21 Apr 2017 15:47:09 +0200
Cc: iasa20@ietf.org
Message-Id: <911CBAD8-5F5C-4E05-ACCB-64C8F45A1661@piuha.net>
References: <42E39015-D0B6-4464-8792-9F3A7089975F@cooperw.in> <d3b3bdd0-5da1-7893-e162-7a7a61cd0a0a@cs.tcd.ie> <258772C5-ED70-4AE2-8BDD-2DF149239B30@cooperw.in> <ac959891-8992-f87c-d730-e815a7542a72@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/4HlYdCYd_eclSmcMF8AqrsRkvqs>
Subject: Re: [Iasa20] IASA 2.0 outcome properties
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 21 Apr 2017 13:47:14 -0000
> So I still think your current wording goes too much > towards specific solutions - and extrapolating from one instance > (IAOC managing IAD) to handling 20 folks the same way seems to me > to be only one specific solution. And I also continue to think > that that specific solution ends up with (or significantly moves > us towards) what I would call the major downside of incorporation > and membership. I think we can keep incorporation & membership and supervision of workers doing things for IETF as separate items, I don’t think they are connected at that level. We could have an interesting discussion, I think, about the numbers, how many people need to be involved or for what purpose. Or exactly what the structure is for arranging their oversight. But I think we reasonably need to conclude that if people do work for IETF’s benefit, then there needs to be some oversight. Regardless of whether those workers get paid by IETF or ISOC. (And I wouldn’t say there is no oversight today, but I do believe that it can be significantly improved.) Also I’m not sure the employee / employee of ISOC / contractor distinction is all that important. Think legal services, for instance, regardless of how we’ve organised it today (contracted), it is easy to imagine we might have had a different structure. But no matter what the structure is, I think it would be clear that the IAOC should be ultimately in charge of the oversight of the people doing work for that function. Jari
- [Iasa20] IASA 2.0 outcome properties Alissa Cooper
- Re: [Iasa20] IASA 2.0 outcome properties Ted Hardie
- Re: [Iasa20] IASA 2.0 outcome properties Stephen Farrell
- Re: [Iasa20] IASA 2.0 outcome properties Randy Bush
- Re: [Iasa20] IASA 2.0 outcome properties Brian E Carpenter
- Re: [Iasa20] IASA 2.0 outcome properties Alissa Cooper
- Re: [Iasa20] IASA 2.0 outcome properties Stephen Farrell
- Re: [Iasa20] IASA 2.0 outcome properties Alissa Cooper
- Re: [Iasa20] IASA 2.0 outcome properties Jari Arkko
- Re: [Iasa20] IASA 2.0 outcome properties Alissa Cooper
- Re: [Iasa20] IASA 2.0 outcome properties Alissa Cooper
- Re: [Iasa20] IASA 2.0 outcome properties Alissa Cooper
- Re: [Iasa20] IASA 2.0 outcome properties Brian E Carpenter
- Re: [Iasa20] IASA 2.0 outcome properties Jari Arkko
- Re: [Iasa20] IASA 2.0 outcome properties Eggert, Lars
- Re: [Iasa20] IASA 2.0 outcome properties Brian E Carpenter
- Re: [Iasa20] IASA 2.0 outcome properties Stephen Farrell
- Re: [Iasa20] IASA 2.0 outcome properties Livingood, Jason
- Re: [Iasa20] IASA 2.0 outcome properties Michael Richardson
- Re: [Iasa20] IASA 2.0 outcome properties Alissa Cooper