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

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 15 February 2018 20:59 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 A40A01241F3 for <iasa20@ietfa.amsl.com>; Thu, 15 Feb 2018 12:59:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 i-iE0lWJLrLt for <iasa20@ietfa.amsl.com>; Thu, 15 Feb 2018 12:59:40 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F20051243F3 for <iasa20@ietf.org>; Thu, 15 Feb 2018 12:59:39 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 76F2B20090 for <iasa20@ietf.org>; Thu, 15 Feb 2018 16:06:41 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2E89380AE1 for <iasa20@ietf.org>; Thu, 15 Feb 2018 15:59:39 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "iasa20@ietf.org" <iasa20@ietf.org>
In-Reply-To: <5a3e7819-cde0-7cdb-32f0-aa6bd788da29@cs.auckland.ac.nz>
References: <4483006c-1652-7340-19f8-8d0579af8213@cdt.org> <458C6912-4C20-4A5E-88A1-6397ABE3969A@akamai.com> <CABtrr-XXTvhhs0bFq=oYVJHpr2fnWEr8YLAwwKzaM5Pcq-UdJw@mail.gmail.com> <05DFEC48-5443-475C-BB98-5059FC51C654@akamai.com> <8F5DBA58-FC19-43FF-A2D5-45A4CE5EA5DE@cooperw.in> <5a3e7819-cde0-7cdb-32f0-aa6bd788da29@cs.auckland.ac.nz>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Thu, 15 Feb 2018 15:59:39 -0500
Message-ID: <22604.1518728379@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/hBcW_GP2asH6hPpa-OCyC7NqgeI>
Subject: Re: [Iasa20] [FORGED] Re: 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 20:59:43 -0000

Brian Carpenter <brian@cs.auckland.ac.nz> wrote:
    >> The nature of the options present in the memo has nothing to do with
    >> the nationalities of the people on the design team. It has to do with
    >> the fact that ISOC is a 501(c)3 not-for-profit organization incorporated
    >> in the US, and that the preferences expressed in the hums in Singapore
    >> were for options that maintain the IETF’s administrative activity under
    >> ISOC’s umbrella [1].

    > Indeed, that's why I pointed out that ISOC has at least one overseas
    > office. The US might be the most obvious option but that doesn't mean
    > it's the best.

My instinct is that setting up a non-US entity would be no easier starting
From scratch then starting from ISOC's 501(c)3 status.
(I come to this trying to setup Cdn branches of various US based non-profits,
and observing the fate of a few that failed.  I've also been on the board of
6 Ottawa based non-profits over the past 20 years, and done all the paperwork
for a few of them)

Or to put it another way: if having a non-US ISOC/IAOC equivalent entity is
worthwhile doing, then it's worthwhile doing even if we *are* going to create
some new (I),(II) or (III) structure inside the US.

I'm claiming the cost is probably the same regardless of what we do today.

I think that if we were going to do such a thing, that the first question
we/ISOC/DT should ask is to those contributing money:  are there other
jurisdictions where you'd like to contribute to ISOC?
(/me Eyes cash in Google and Apple's Dublin banks...)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-