Re: [Iasa20] Memo exploring options for IASA 2.0 models

Richard Barnes <rlb@ipv.sx> Thu, 15 February 2018 04:49 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 02C3F1270A3 for <iasa20@ietfa.amsl.com>; Wed, 14 Feb 2018 20:49:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 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_LOW=-0.7, URIBL_BLOCKED=0.001] 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 qzlBvOTH75B0 for <iasa20@ietfa.amsl.com>; Wed, 14 Feb 2018 20:49:09 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 7413B12025C for <iasa20@ietf.org>; Wed, 14 Feb 2018 20:49:08 -0800 (PST)
Received: by mail-wm0-x232.google.com with SMTP id x21so721584wmh.0 for <iasa20@ietf.org>; Wed, 14 Feb 2018 20:49:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lH7eRFOmvFy8rxmhZsveRDo3gthwZp+m28LneKDX3gw=; b=2BOoW+R1mZgbGSjYqKZe2UdpPaTamNxCxhOrWerrpnQE2mI7VUsyHUMFvfH4oVZ6M8 JqsejGclLNKJsbnEK9sgKMfWUiIq1aGYwhG/IOdCzlIKoZurKk3ULfKdqhhupF8hc4MI 42yJCPrVtoEnzJ0sirSuhYW2RF8JO/PeqzuZrWAeK20vfXeh6v/MD8pa1RRkos8d876l 1QpUdVmua7aPza+/CUym4FNR1BnairH+nex7z7irwFYSEVno0JScaledSPP3+mO6z8y/ qNKipWfAuqDQ5Nv1myF4JUCkL7JNInwzG6+6dCs9snSRaGIoJtg+rsyBZcOUR+fq6ESC G4rA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lH7eRFOmvFy8rxmhZsveRDo3gthwZp+m28LneKDX3gw=; b=loP2XUb/UywjO7dDRaRAu0NO59ro2p0XSOkPoLK/XCHhXrkPL29YHYfNO0fH/pFNzU BxS1T7oveJdWsfVd50WwOLpJ0ZlHJgLbJiHs7jqbfqIXGn+gB60mTQkat8PxRy8OIauW Lq66G7TbqEWjr3AIzfBOZD2E6QqHnZ01hkRITf8X8Ms4m1043osx14FcAQ6UZZlBpgYT lWlCp6ssKDoheGOtZdFygttnrZZJHN471aYP+4INyjun0preqMMZhrP5s0x05LXKd6nf INk815x5R+T40TacYUQ36dH5dclkH0raIYos9q+G6dCZb4p1/fH5d981fhgy8W/1BYk0 M7VQ==
X-Gm-Message-State: APf1xPBrsrhtjfktbhd66PgsYTNZKkjodvZxUDC5zBX5aEYW9psDoG/w qthb87EJdvxNTJCHrnPI+IGutpz12WVzOaNGaxTrijNmOj8=
X-Google-Smtp-Source: AH8x224kO9X33WPPzqSQ+nwwSkeYC9a7NPZdw5q23VaNHIIvBF6YyfjZhjsu7/VSVMbIbZtGaHrLMA1hG2RwHmjf9f8=
X-Received: by 10.28.11.147 with SMTP id 141mr853451wml.138.1518670146782; Wed, 14 Feb 2018 20:49:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.20.66 with HTTP; Wed, 14 Feb 2018 20:49:06 -0800 (PST)
In-Reply-To: <CABtrr-V88xYcRDNMDz8aH_6Jq-fvtDLMwpYxxXFxLZv-S25SSg@mail.gmail.com>
References: <4483006c-1652-7340-19f8-8d0579af8213@cdt.org> <CA+9kkMBK0YzWmVZqFnRuzKj_mTZeSHy4xhZSgrjjNr7NnO68DQ@mail.gmail.com> <CABtrr-V88xYcRDNMDz8aH_6Jq-fvtDLMwpYxxXFxLZv-S25SSg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Wed, 14 Feb 2018 23:49:06 -0500
Message-ID: <CAL02cgQu-zi_FySTsDX_HbPOt+FrFYypSvPLwY8QfnfffR3QrQ@mail.gmail.com>
To: Joseph Lorenzo Hall <joe@cdt.org>
Cc: Ted Hardie <ted.ietf@gmail.com>, iasa20@ietf.org
Content-Type: multipart/alternative; boundary="001a11440c0ea15e8b056538f28c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/vOe3oeJDGHdAO_ryFzPQqmfSF7Q>
Subject: Re: [Iasa20] Memo exploring options for IASA 2.0 models
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: Thu, 15 Feb 2018 04:49:12 -0000

I actually have the opposite suspicion, members != participants.  For those
not familiar with the terminology, "participants" in the IETF sense is
basically "whoever joins a mailing list or comes to a meeting", or
similarly "whoever is subject to the Note Well / relevant IPR RFCs"
[0][1].  The IETF has very open participation.

By contrast, given that this memo was written by lawyers, I expect that
they meant "members" in the legal sense, who are the parties that legally
control the entity (e.g., the shareholders in a for-profit corporation)
[2][3].  So saying that "ISOC must be the sole member" just means that ISOC
legally retains control of the entity, as one would expect with a
subsidiary entity.  That control is manifested, for example, in their right
to replace all or a majority of the board.

Note, however, that even if ISOC retains ultimate legal control, there are
still differences among options (II), (III), and (IV) (using the memo's
numbering).  In options (II) and (III), ISOC's control is attenuated
compared to option (IV), since basically the only right they have is to
appoint the board; they couldn't, say, direct specific contracting or
personnel decisions.

--Richard

[0] https://www6.ietf.org/tao.html
[1] https://www.ietf.org/about/participate/
[2] http://info.legalzoom.com/definition-llc-member-4425.html
[3]
https://www.legalzoom.com/knowledge/nonprofit/topic/non-profit-membership

On Wed, Feb 14, 2018 at 11:09 PM, Joseph Lorenzo Hall <joe@cdt.org> wrote:

> I'm not sure, we should clarify. I believe the type 1 SO here is the same
> as that for PIR, so I suspect it's what we would call participants.
>
> On Wed, Feb 14, 2018 at 19:34 Ted Hardie <ted.ietf@gmail.com> wrote:
>
>> Hi Joe,
>>
>> Thanks for forwarding this.  I do have one clarifying question.  In the
>> section on the Type 1 supporting organization, it says "Can have members
>> that are not ISOC members." but also says "ISOC must serve as the sole
>> member of the corporation with the right to appoint at least a
>> majority of the directors."  ISOC is the sole member of PIR, and I had
>> made the assumption that it would be the sole member of a new Type 1
>> supporting organization, should that be the path selected.  This, however,
>> seems to contemplate members beyond ISOC, and I'm unsure who or what those
>> could be in our context.   Or does the first usage simply mean what we
>> would call participants in the IETF context, saying that the participants
>> in the supporting organization do not also need to be considered "members"
>> of ISOC?
>>
>> thanks,
>>
>> Ted
>>
>>
>>
>> On Wed, Feb 14, 2018 at 3:29 PM, Joseph Lorenzo Hall <joe@cdt.org> wrote:
>>
>>> Greetings,
>>>
>>> I am writing on behalf of the IASA 2.0 Design Team to update you on
>>> progress since Singapore.
>>>
>>> The Design Team and Alissa, Sean Turner, and Richard Barnes (ISOC Board
>>> members) asked ISOC's tax law counsel at the law firm Morgan Lewis to
>>> examine the options we are considering in a new IASA 2.0 structure, in
>>> terms of governance, finances, and administrative complexity.
>>>
>>> The response memo is attached, covering the spectrum of options from the
>>> status quo to increasingly independent models. The memo covers four
>>> options:
>>>
>>> 1. Substantial independence: an independent 501(c)(3) org;
>>> 2. Significant independence: a 501(c)(3) Type 1 Supporting Org;
>>> 3. Weak independence: an LLC that is a "disregarded entity"; and,
>>> 4. Status quo: continuing as an activity of ISOC.
>>>
>>> Note that the design team has some additional questions that we hope to
>>> clarify including the implications of the public support test, board
>>> composition and control, and potential costs (sunk/ongoing) of a
>>> transition to each model. We'd like to hear from all of you as to your
>>> thoughts, either in terms of clarification or if this analysis affects
>>> which model you prefer.
>>>
>>> If questions emerge around particular themes we can work with ISOC on
>>> clarifications.
>>>
>>> thank you,
>>>
>>> Joe (writing on behalf of the DT)
>>>
>>> --
>>> Joseph Lorenzo Hall
>>> Chief Technologist, Center for Democracy & Technology [
>>> https://www.cdt.org]
>>> 1401 K ST NW STE 200, Washington DC 20005
>>> <https://maps.google.com/?q=1401+K+ST+NW+STE+200,+Washington+DC+20005&entry=gmail&source=g>
>>> -3497
>>> e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
>>> Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871
>>>
>>>
>>> _______________________________________________
>>> iasa20 mailing list
>>> iasa20@ietf.org
>>> https://www.ietf.org/mailman/listinfo/iasa20
>>>
>>> --
> Joseph Lorenzo Hall
> Chief Technologist, Center for Democracy & Technology [https://www.cdt.org
> ]
> 1401 K ST NW STE 200, Washington DC 20005-3497
> e: joe@cdt.org, p: 202.407.8825 <(202)%20407-8825>, pgp:
> https://josephhall.org/gpg-key
> Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871
>
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>
>