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

Ted Hardie <ted.ietf@gmail.com> Thu, 15 February 2018 00:34 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 202C2126D74 for <iasa20@ietfa.amsl.com>; Wed, 14 Feb 2018 16:34:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 NU1U-k99xMKl for <iasa20@ietfa.amsl.com>; Wed, 14 Feb 2018 16:34:13 -0800 (PST)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 013A1126CF9 for <iasa20@ietf.org>; Wed, 14 Feb 2018 16:34:13 -0800 (PST)
Received: by mail-oi0-x230.google.com with SMTP id u6so17901110oiv.9 for <iasa20@ietf.org>; Wed, 14 Feb 2018 16:34:12 -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=f93KlK+KxlKsjAjJN0yyJHnxvOQwbYSN+MvmhJ6fXaU=; b=hWwvvUjotEW/7pfw66NntTnD7OCqjnZ0qLbpPDo5Px/9HZdHADQ3DZ6beMFzATjeSW JOHsEq69nIMw6YDm7611v05Fz0/4SKWS8zjhWYLBn50piCQdoBPZXKvTl/z1cBIcQCAQ TGsexyxMl0nPABNITV+/IEHARTlLo+z1Jbadq9vOYUMCKXKjfqG+LM6EUs9jdCr6UwBR 8JGpGNMrfSw1N7Mi/lk0zArleZI5D6usGVZhHL+we4X/rZa4cw4xdj1yVYTSkZGmSgc/ aZ55TpkhKQ8CicKKpASKXnnSLA01CJpl2378xkTuZf49YyVE2XfO310R0gzyMW5hOB7o 6cgg==
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=f93KlK+KxlKsjAjJN0yyJHnxvOQwbYSN+MvmhJ6fXaU=; b=f/l1/jYDDI18hGpsixr2/mkhngji219BkVXG6DfARlPGXOyJjhGM2O3dQajmd5OIK2 Iw0d20Upe+p9lZOx3x0GMtR9rdsZjQbsML7dCh9iMpNpf6RBPPhJNrMXjzNzc89yj3Ep Bx0wHNi6ngJ3rCb3aySNx+KMBwxcJCqMmlSEKDmswXMCjRz5rQ9JWrSqYRKqEsBJk1yn vuaoI2RvjP7lrG0w3Go3XXtiOAutk9gTtvhW+FpPv34b0txBSExDMIGkAjSWGw+t1aqn ZS6wdndMqJbNO+wBsFQjBbpuljEhMGoVT7otbAMs4wGAIbJwZyNVJ57Xq6lGCxeFO7W6 cDgg==
X-Gm-Message-State: APf1xPCAYPP6gBIbGfWR/Z6ODjB+iKKkaqFotnB+9dDnlmIr95DCFdvZ w4VqCcjNA2b0gAz4y1amrwzsmu0aM5i5Y7N13qA=
X-Google-Smtp-Source: AH8x225xWbnLr/8VErg/k2Eu6yV8orQebM99vwiU8OSyec+dF4VC8qwbHFjIOmcwfCye+/nOKTfZGnYJOY65Yc0dQyM=
X-Received: by 10.202.18.6 with SMTP id 6mr670827ois.46.1518654851939; Wed, 14 Feb 2018 16:34:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.3.71 with HTTP; Wed, 14 Feb 2018 16:33:41 -0800 (PST)
In-Reply-To: <4483006c-1652-7340-19f8-8d0579af8213@cdt.org>
References: <4483006c-1652-7340-19f8-8d0579af8213@cdt.org>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 14 Feb 2018 16:33:41 -0800
Message-ID: <CA+9kkMBK0YzWmVZqFnRuzKj_mTZeSHy4xhZSgrjjNr7NnO68DQ@mail.gmail.com>
To: Joseph Lorenzo Hall <joe@cdt.org>
Cc: iasa20@ietf.org
Content-Type: multipart/alternative; boundary="f4f5e808dbccfc81dc056535627e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/I7iP44pCjreDh0U6RYhsX93DmC0>
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 00:34:15 -0000

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