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

Ted Hardie <ted.ietf@gmail.com> Thu, 15 February 2018 05:36 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 99A0D12D7FB for <iasa20@ietfa.amsl.com>; Wed, 14 Feb 2018 21:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 JJc1hMjQCzy3 for <iasa20@ietfa.amsl.com>; Wed, 14 Feb 2018 21:36:06 -0800 (PST)
Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::22d]) (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 B2EF512025C for <iasa20@ietf.org>; Wed, 14 Feb 2018 21:36:06 -0800 (PST)
Received: by mail-ot0-x22d.google.com with SMTP id w10so8924611ote.13 for <iasa20@ietf.org>; Wed, 14 Feb 2018 21:36:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/R/r0QEgVDskixp4GEvOcdOa6amNkNkmhqv7i8UN9kw=; b=CENJdXvm6Iza56EiYevxyKjLnlRZRkShIrFaqTt1MPmD++xt3jROluZs3Vj1c0wk96 M2S4ccHEZokqkMetKcmtUk/Qux5farXoXoChyDxIsVaIjkSVqB1H4McU+rPRHAAp3mPV faKqD0J0sztFRyj9KUmW7dsJ8GywktPh0m+fo5Ylo+S7CS7a7tdLKU/eFkpiDlAm/KwX 9w3gajrseSldILEKMpgi6d1fCuc2UUQPJYvzEXlnP0OLatAKMFIeViGKRnwAyKdmFO+G GkhW+V0fT8ByAUabfNy5sLLP4j0EQ9cmcAyKLWFUGF0FDSFX0Bn474uW8rnvAcfbvA/c o6Qg==
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=/R/r0QEgVDskixp4GEvOcdOa6amNkNkmhqv7i8UN9kw=; b=FLEcqIBV2vwhZ+MQS6LHkTws21dZtRqG0osBpxX1a+RQrWfDDMtpWrXBiGtVlXg4/T 20TOoKycQBFsb3lz8e2j0bWIZBCzidhIGzswubYI1+VOT0TmKIXyLwDT9GnrSEQSUUWa e2fz4n9zVt54qlp2L17oHAkIQj3eUVKW0W7FemwMYGMCmgyPTc+zKzDvAt7DZgCNXcGZ 1re0OMN0YbXxhWrc3qtE0ACDABPhTtVeZy71ERFrto0VC5UfOMbWkaruxxTyTdaap7P6 HiYYdCHRM01uRur0q24s7engK1lErWfg/H87NTbPsiWyPLniGGWuKb/HzChLKA9cRczh thKg==
X-Gm-Message-State: APf1xPDbWi2N//lEmiB3kV1rOqfAS8xhbmmyUINOnbI9ucTxW9TowuaY wrQ5w71GEP76L9KDn6GI/yuzOTcCGqDAGlUCJS6aCQ==
X-Google-Smtp-Source: AH8x227mEFvSJhIQQ4egbuHQf5kmMrKuQ7kWag+XoTjGcPG2S7zYwiMa63CgFSU8a/YwrFWcKMv0ftJYPssoEqFEBUQ=
X-Received: by 10.157.114.157 with SMTP id t29mr1089321otj.252.1518672965340; Wed, 14 Feb 2018 21:36:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.3.71 with HTTP; Wed, 14 Feb 2018 21:35:34 -0800 (PST)
In-Reply-To: <CAL02cgQu-zi_FySTsDX_HbPOt+FrFYypSvPLwY8QfnfffR3QrQ@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> <CAL02cgQu-zi_FySTsDX_HbPOt+FrFYypSvPLwY8QfnfffR3QrQ@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 14 Feb 2018 21:35:34 -0800
Message-ID: <CA+9kkMC_BjV4DdxNSk5LrgR0uU1vVF3YDyqobFYc7-t_idx60w@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Cc: Joseph Lorenzo Hall <joe@cdt.org>, iasa20@ietf.org
Content-Type: multipart/alternative; boundary="f403045d9562a112ee0565399a3d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/qHmkrN6h5CLoskE-ekBe_RD_7uE>
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 05:36:10 -0000

So, I can personally read it either way, which is why I asked for
clarification; it sounds like that means getting the lawyers to specify.  I
note that the text on the "Disregarded Entity" option says this: "Can have
members that are not ISOC members, although for tax purposes their dues
will be revenue to ISOC and ISOC will need to substantiate their
contributions." which seems to contemplate a form of membership that the
IETF has never had (we have contributions and participants, not dues and
members).

On Wed, Feb 14, 2018 at 8:49 PM, Richard Barnes <rlb@ipv.sx> wrote:

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

While I certainly can read the memo this way, that seems to me to mean that
"Can have members that are not ISOC members" is not actually a property we
care about, for the reasons Alissa pointed to in the minutes.  The
structures the hums support are those under the ISOC umbrella. I would
expect us, should we choose this option (or the other options where this is
feasible) to disallow members other than ISOC.  While ISOC's ability to
appoint the majority of the board would always let us avoid capture by a
different entity, there seems no good reason at hand to have other members
and a good bit of risk that it could slowly change the IETF into a
membership organization.

Just my own point of view, of course.


>
> 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.
>
>
I was honestly, expecting the pros and cons for these different structures
to be laid out a bit more in terms of the IETF's situation, so I may well
be missing something.  From my reading, though,  I see no advantage to
option (III); it seems mostly just to put ISOC into the role of validating
the contributions.  If there were specific advantages of that one that were
obvious to the design team, I'd appreciate your thoughts.

thanks,

Ted


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