[Iasa20] More questions?

Alissa Cooper <alissa@cooperw.in> Tue, 27 February 2018 01:36 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 D19C912DA3E for <iasa20@ietfa.amsl.com>; Mon, 26 Feb 2018 17:36:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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=ig8qal+a; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=k5QUfAYI
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 8CGI_K8SfyFl for <iasa20@ietfa.amsl.com>; Mon, 26 Feb 2018 17:36:33 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AF2212D96B for <iasa20@ietf.org>; Mon, 26 Feb 2018 17:36:33 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 9719A211AE for <iasa20@ietf.org>; Mon, 26 Feb 2018 20:36:32 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Mon, 26 Feb 2018 20:36:32 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=IkfLj/fZclFCQhnVfC5s/72xz+qPs1TvXV4702kwPag=; b=ig8qal+a 4IeOytkv3lnzy0SwIyB2qJElzNXbOXHkw/PP9i+cl9pMwTyADLwlnwA7Bh2TPh8a 8+JXoWhJ3U6lSw0u8K3l6ViSNuRL1p1s+Ev6hXIR7Y+RDPrKX3SsZtLT5hlKI59k qvpbfR5y4HAZGqg28VcZT31rTGQrO+Bi76H1WjUa1/wha9ntwEj0xqqUwxYxO3pf kBKFAaJmsuEhG7ptlFVare28OyCY519qbfDoIGp5HbWFkG0zvnUENQpxMqHGFMhC T2q1BzLJDlzJMGohFsPPiK0sIx51SmqC+84pja78zDEW41DEjLd2n7liEs4Be3aM W1kN0uDn1zZXww==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=IkfLj/fZclFCQhnVfC5s/72xz+qPs 1TvXV4702kwPag=; b=k5QUfAYIBdaLMDCGFpVwWp5+mIQkaixSX4hqWn27UESsR xrDVSnzYY1QpqFt/P87yqEc0rbr7SCaO61mxpbw6+jZ+ItnF5rQdL/g6nRqw43a2 lMWqnAJVCYhSdA++rz1iLaRPjzFUSmoyaiqOHGMyK7jdtFNmTuIGle7BzcyvgAzc azRLosi+e3bOHIzof23kaHCB8Gg3JEni1esLN3ci6NjZbe9aJwz0ZM7NfhAYuc2n byzXVFubdFF0Xa0g63/LDqsmEwkslt15ShfXM2FScd0lawF+2JfjGfeXXv/Mx1PI v+K9ji56+qLISU8Fdj6gGT6h0fkWS+V/NSrnsF0Mw==
X-ME-Sender: <xms:ILaUWqNqIohFme6-vh7hoqDGxpfJwFV3LT7cW0jRYezKDr-KkKoKHA>
Received: from [10.19.234.245] (unknown [128.107.241.174]) by mail.messagingengine.com (Postfix) with ESMTPA id 0BB0B24591 for <iasa20@ietf.org>; Mon, 26 Feb 2018 20:36:31 -0500 (EST)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <E596FE5B-A6F9-481D-B2BA-07401B416E79@cooperw.in>
Date: Mon, 26 Feb 2018 20:36:30 -0500
To: iasa20@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/NSFDLJrqpge-pSUrq2L80zVPo3M>
Subject: [Iasa20] More questions?
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: Tue, 27 Feb 2018 01:36:35 -0000

I’ve compiled the list of questions below for review by the folks at ISOC and Morgan Lewis (as appropriate). Some of these are derived from the list discussion and some from the design team’s initial discussions of the memo. 

1. We’d like more information about the public support test, what the desired relationship is between public support and total support, and whether the 2% cap applies to non-profit foundations.

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.

3. We’d like more information about the extent of the administrative burden under options 1 and 2, both the one-time burden to create the entity and the ongoing burdens relating to tax and audit obligations. 

4. We’d like to understand whether it would be possible for the IETF administrative entity to be incorporated outside of the US under options 2 and 3, and if so, how the administrative complexities compare to incorporating the entity in the US.

5. Ted’s question about whether the notion of membership under option 2 contemplates members aside from ISOC as the sole member.

6. We’d like to understand how the tax receipts work under option 3 — whether sponsors and/or meeting attendees will pay the IETF administrative entity but receive a tax receipt from ISOC, or whether there is another way of handling receipts.

Are there other clarifications that people feel they need in order to understand the options explained in the memo?

Thanks,
Alissa