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

Brian Carpenter <brian@cs.auckland.ac.nz> Fri, 16 February 2018 19:07 UTC

Return-Path: <brian@cs.auckland.ac.nz>
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 39078126C2F for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 11:07:59 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=auckland.ac.nz
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 AdDPuo8sbpTD for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 11:07:57 -0800 (PST)
Received: from mx4-int.auckland.ac.nz (mx4-int.auckland.ac.nz [130.216.125.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50EC71242EA for <iasa20@ietf.org>; Fri, 16 Feb 2018 11:07:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1518808077; x=1550344077; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=xsIix07eioyqYwU8344NdtgLlzE+kBS29DRaZ7fas5k=; b=e3lcKvlr9j2dMSManvY/G9JmvM61lK+19oMRokYMErTtCqU+k0aWc30D t2pF+8Ha+VQslefwtWa4CgmEz1KJTNUldCVoKvp2uiAG6l5abU/cOoYRk 6F0W5auF44PWDxY/E0/v44wkme0BYhV+4rslccVAjZFvKoj0kPhFjflhb wzdaWTzuFpTagEKF3kFJbR8pmGz1kxVLdivEQg1KWF2/lozcu2ftlf20V oBOVzcpQE40993eh6Pk/6oKkh0xQXpQ0jDkcrKHHrGlc8ZO9YGCU+TK9m DPiPrSfUkDfeEludqYqhSw3fxTNJBmEjw9jQ05ZOat41KBGq167zrNS74 A==;
X-IronPort-AV: E=Sophos;i="5.46,520,1511780400"; d="scan'208";a="1613364"
X-Ironport-HAT: BAD-REPUTATION - $RELAY-AUTH-THROTTLE
X-Ironport-Source: 111.69.225.189 - Outgoing - Outgoing-SSL
Received: from 189.225.69.111.dynamic.snap.net.nz (HELO [192.168.178.30]) ([111.69.225.189]) by mx4-int.auckland.ac.nz with ESMTP; 17 Feb 2018 08:07:34 +1300
To: Andrew Sullivan <ajs@anvilwalrusden.com>, iasa20@ietf.org
References: <4483006c-1652-7340-19f8-8d0579af8213@cdt.org> <20182.1518727709@obiwan.sandelman.ca> <C77B41DA-268D-4F0E-8AC8-F2E292E38B14@cooperw.in> <9631.1518800971@obiwan.sandelman.ca> <be961111-9bed-086e-a0ab-b220125a438d@cs.auckland.ac.nz> <20180216185551.cgigor7up7uowmr6@mx4.yitter.info>
From: Brian Carpenter <brian@cs.auckland.ac.nz>
Organization: University of Auckland
Message-ID: <40a7ffe5-8417-cfdf-15dc-6603a5c7978f@cs.auckland.ac.nz>
Date: Sat, 17 Feb 2018 08:07:46 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <20180216185551.cgigor7up7uowmr6@mx4.yitter.info>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/vwg7JInOFYAJqt0nRcUGPhwQN-U>
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: Fri, 16 Feb 2018 19:07:59 -0000

On 17/02/2018 07:55, Andrew Sullivan wrote:
> Hi,
> 
> On Sat, Feb 17, 2018 at 07:50:40AM +1300, Brian Carpenter wrote:
>> On 17/02/2018 06:09, Michael Richardson wrote:
>> ...
>>> 1. I think that we want our own bank account.
>>
>> I have seen no consenus call to that effect.
> 
> The IETF already has its own bank account, so I think you'd need a
> consensus call to undo that.  

Actually, I thought I remembered hearing that. So good, that's one
problem that's already been solved the easy way.

>> Why? When did the IETF ever suffer as a result of its contracts being
>> signed by ISOC?
> 
> I believe some people have made the point about this repeatedly: it's
> not the contracts as such, but the consequences of that contracting
> relationshop, that is the problem.

But the only concrete example I've seen is the minor hassle that ekr
just mentioned. I'm still just not getting what is the major hassle
that justifies the daunting overhead of a separate legal entity.

(That doesn't diminish the other very real problems that IASA 2.0
needs to solve.)

    Brian