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

Joseph Lorenzo Hall <joe@cdt.org> Thu, 15 February 2018 04:10 UTC

Return-Path: <jhall@cdt.org>
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 8C08C1270AE for <iasa20@ietfa.amsl.com>; Wed, 14 Feb 2018 20:10:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=cdt.org
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 1LzYt4bsmZtw for <iasa20@ietfa.amsl.com>; Wed, 14 Feb 2018 20:09:58 -0800 (PST)
Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::22c]) (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 00A011270A3 for <iasa20@ietf.org>; Wed, 14 Feb 2018 20:09:57 -0800 (PST)
Received: by mail-ua0-x22c.google.com with SMTP id n1so15067448uaa.2 for <iasa20@ietf.org>; Wed, 14 Feb 2018 20:09:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ESVuJDftTzqkIuRNIUfTzmfgVc++qBaBvfM9oIaqRNY=; b=qN5FDGbKvBYUZFTfUO8t8eRMKxnvShcbhwXMI8Pu/nPF4iEDuNE20Y09C1craDWRhJ HrYWcedi5Ow8SZ1uTogR2kWBxxEO7n37tSlEn2s4OaRzNx04hIGMj/QfLqT+Vn0rPiGs HcHTplcSY9dhm9kzwpkGGrAGcJDU2nS91ynrU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ESVuJDftTzqkIuRNIUfTzmfgVc++qBaBvfM9oIaqRNY=; b=Wbr7KSWQ+KIIxEEnXtfS7fO0OVhoZzAsdSOA0RDi8kUk4cbRr62/kZeZrZOfByFhnZ /eH6v5+KLEWITb4bUSMVLayMlXyvLS69khRmddIft4MyQgDwYcN0STJKf802KHRStpm0 9vxnBCoH9SxEXr2clHLWTRUEh+Q5LjiA8H/a30sQ2RyJtcTeBBRcglEv8/ydIcFb8VR8 kn1oL62LWR9OMg6QB/sTW3bNdlXmAGcFIq9jBClM492tcBrvG6bdyUIFAoJidQcjIoiC VlZNl9owpXiVQkBtf7zVnyX118I8UDTxYKBMd6MSuMbwgCwMYJ+97F4PzwJ9wqWZHJPi 41Zw==
X-Gm-Message-State: APf1xPB1fYXzibQXlrtr/IMScChfhjpZqg63Mrh9Zc5YMebE80uqNoeQ 6YPrOBeCz+VLIWsMhcPs4oyFh+HkkxRvLMjram8v5g==
X-Google-Smtp-Source: AH8x226Q9OeTJbVQtb4I0A7UyIZKEa9DN7HcUi3fV3eEBhZgBKxn7zv/wIArQMxlMwLhLVQbalnd4u1TMsikHChxmUo=
X-Received: by 10.176.4.40 with SMTP id 37mr1195351uav.128.1518667796542; Wed, 14 Feb 2018 20:09:56 -0800 (PST)
MIME-Version: 1.0
References: <4483006c-1652-7340-19f8-8d0579af8213@cdt.org> <CA+9kkMBK0YzWmVZqFnRuzKj_mTZeSHy4xhZSgrjjNr7NnO68DQ@mail.gmail.com>
In-Reply-To: <CA+9kkMBK0YzWmVZqFnRuzKj_mTZeSHy4xhZSgrjjNr7NnO68DQ@mail.gmail.com>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Thu, 15 Feb 2018 04:09:45 +0000
Message-ID: <CABtrr-V88xYcRDNMDz8aH_6Jq-fvtDLMwpYxxXFxLZv-S25SSg@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: iasa20@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c06b7168b9491056538661f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/pr2oXDGb3rQX2xUjsbiBTbPl1og>
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:10:01 -0000

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, pgp: https://josephhall.org/gpg-key
Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871