Re: [Iasa20] nomcom appointees to option 2 or option 3 entities

Alissa Cooper <alissa@cooperw.in> Wed, 14 March 2018 14:27 UTC

Return-Path: <alissa@cooperw.in>
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 B84DE1270FC for <iasa20@ietfa.amsl.com>; Wed, 14 Mar 2018 07:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level:
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=Akjh2Jeu; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=IHYKyhnt
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 YNGlDE3Xwv2u for <iasa20@ietfa.amsl.com>; Wed, 14 Mar 2018 07:27:14 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E23812D0C3 for <iasa20@ietf.org>; Wed, 14 Mar 2018 07:26:47 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id D2871212A3; Wed, 14 Mar 2018 10:26:46 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Wed, 14 Mar 2018 10:26:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=ZJ/tHh2C1quLtXm9q5y2KeWjdLTmJ dPOk20JApxyqqw=; b=Akjh2JeudKDnzoMWRQc2NKv3FmfJEvxaemxuBH75ZM/Tp o5lIitzgtN8COrOeqclhuzgE/5a05PQbGLPA17s1q4bZpk7A4AywC1+M/oEWlJNH B/eGQp4gEYJWi0kBKN3p3hGpPOhKDzNPCMq9uNNI0/S3YxprmEWGH4jv5pMiK1UR ho1xJkOi+Ir5/KV3RqbqqQxJk0D0XsSDlPBxL6ylmkSlgT29dvony1c03EmESZU3 WxXmBJIPXCNNqgF6X1TSXF0HLQYJD1SxIO4DXSzfKpsCSn9cJKq1XVV8tlWJn9lq JwvU3Fj9UthA4r1ZvdIghaDqjwXM1w3BBxuGwFeEw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ZJ/tHh 2C1quLtXm9q5y2KeWjdLTmJdPOk20JApxyqqw=; b=IHYKyhntJqE91vsawL1s97 HA8PLgmtg+0FOR5oi7LgmuHIvv6tz75GXQ/nPwmMzKRdOOtEP8Xl0VDq79Apc+eY VMLawF9wEJXMQE0Otm+YiAEXnLFUVVHkmxN/4f/HrWP5e+a5b/M4y9wZyWaOwFk9 ypsW9u9syzkvP450Wu3CwiDnO0o5e6zPMjxsbBuJC+yNztlHl+MuPSCsKzfvCDlR 60zoV6BOJEt/MFVAXXdDxmdYDs3DaCLC0tmkoQYkmxjNGfrds7rgWF3tr+DZjzZn znK1RwhDfGiWiV1vYVdlsdgqzHS8+KZLJizF/oOCCI2CJ4+FEnlWNifY9feTQG9Q ==
X-ME-Sender: <xms:JjGpWrujm_mLrA103O1Z17FKG1enmsdjQGB5snPRgrcGWyI9mDnyWA>
Received: from [10.19.234.248] (unknown [128.107.241.171]) by mail.messagingengine.com (Postfix) with ESMTPA id 1E3FB24317; Wed, 14 Mar 2018 10:26:45 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <29374.1521036259@obiwan.sandelman.ca>
Date: Wed, 14 Mar 2018 10:26:44 -0400
Cc: iasa20@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FDAD5F9-A69C-4546-A0B7-7F95BA2E504D@cooperw.in>
References: <E596FE5B-A6F9-481D-B2BA-07401B416E79@cooperw.in> <05C67DDF-29B1-433E-886A-EC9C2134BC39@cooperw.in> <1DFB2924-5C37-49A9-BF01-2A458B22E7CC@cooperw.in> <29374.1521036259@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/DUOLuTgkvz2m6hiqVQEuAx6g0U0>
Subject: Re: [Iasa20] nomcom appointees to option 2 or option 3 entities
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: Wed, 14 Mar 2018 14:27:16 -0000

> On Mar 14, 2018, at 10:04 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Alissa Cooper <alissa@cooperw.in> wrote:
>> 2. For option 2 and option 3, we’d like to understand what kinds of
>> provisions could be included in an operating agreement between ISOC and
>> the IETF entity regarding board appointments and control, assuming we
>> want to maximize the IETF’s ability to determine the composition of the
>> board.
> 
>    ac> Awaiting the lawyers on this.
> 
>> Under option 2 (the Type I supporting organization), it would be
>> possible for ISOC to delegate the authority to appoint board members of
>> the IETF administrative organization to a subcommittee of the ISOC
>> Board. So, for example, it would be possible for ISOC to delegate this
>> authority to a subcommittee consisting of the four IAB-appointed board
>> members, and for that arrangement to be documented in an operating
>> agreement between ISOC and the IETF administrative organization. The
>> IRS may raise a question about this but the attorneys did not consider
>> it to be a serious risk. Under option 2 it would not be possible for
>> ISOC to delegate this authority outside of the board (e.g., to the IAB
>> or the IETF nomcom).
> 
>> Under option 3 (the LLC as a disregarded entity of ISOC), it would be
>> possible for ISOC to delegate the authority to appoint board members of
>> the IETF administrative organization to a subcommittee of the ISOC
>> Board or to a non-board body such as the IAB. This arrangement could be
>> documented in an operating agreement between ISOC and the IETF
>> administrative entity, and that agreement would also need to make clear
>> that ISOC retains all economic interest in the LLC.
> 
> So in option 3, we can do the same thing as option 2 (sub-cmte of ISOC
> board), but we can *also* delegate to an entity "such as" the IAB.
> (I knew I like option 3 better...)
> 
> Does "such as" include the IESG or the Nomcom directly?

Yes, this need not be the IAB. My understanding is that this authority can be delegated to other bodies so long as they have a documented charter and membership.

Alissa


> Given that IAOC appointees have to be confirmed by the IESG under the current
> setup, it seems that the new entity should also be confirmed by the IESG.
> 
> Or is the IAB special because the ISOC board confirms the IAB nominations?
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
>