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

"Leslie Daigle" <ldaigle@thinkingcat.com> Fri, 16 February 2018 21:57 UTC

Return-Path: <ldaigle@thinkingcat.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 2A9131241F3 for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 13:57:18 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=thinkingcat.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 ZLz9Ho4p1xFh for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 13:57:15 -0800 (PST)
Received: from hapkido.dreamhost.com (hapkido.dreamhost.com [66.33.216.122]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2867126BF3 for <iasa20@ietf.org>; Fri, 16 Feb 2018 13:57:15 -0800 (PST)
Received: from homiemail-a102.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by hapkido.dreamhost.com (Postfix) with ESMTP id A33F286C30 for <iasa20@ietf.org>; Fri, 16 Feb 2018 13:57:15 -0800 (PST)
Received: from homiemail-a102.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a102.g.dreamhost.com (Postfix) with ESMTP id 67D42201702C6; Fri, 16 Feb 2018 13:57:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :cc:subject:date:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=thinkingcat.com; bh=B SEkISHFIliwWWbkQ8gaJA0gBos=; b=W9vG7/D4rdPCYuL4NMUezoswEvVyp/aqj XM+TNRw5U3cd92eZkyn1wljOpt0f1n51K5fxIKXnDem6XH+6AwtmTSvY4PSspN9A Peq9EIgIxrPh+tF5Bphx/VV5vHNXIeXgFHucmnpnsYMsDc2DN06eNw+/HtMbY6Q0 dX7f0sECGM=
Received: from [192.168.1.94] (vtelinet-216-66-102-83.vermontel.net [216.66.102.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a102.g.dreamhost.com (Postfix) with ESMTPSA id AB550201702C2; Fri, 16 Feb 2018 13:57:14 -0800 (PST)
From: Leslie Daigle <ldaigle@thinkingcat.com>
To: Brian Carpenter <brian@cs.auckland.ac.nz>
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, iasa20@ietf.org
Date: Fri, 16 Feb 2018 16:57:13 -0500
X-Mailer: MailMate Trial (1.10r5443)
Message-ID: <C87440E9-70FA-4A00-88C8-A349C7FC4E51@thinkingcat.com>
In-Reply-To: <5327daa0-1d54-f051-e620-7c8f4bdc4870@cs.auckland.ac.nz>
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> <40a7ffe5-8417-cfdf-15dc-6603a5c7978f@cs.auckland.ac.nz> <20180216192334.jjgn6bineinfofux@mx4.yitter.info> <5327daa0-1d54-f051-e620-7c8f4bdc4870@cs.auckland.ac.nz>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_73A65C25-C2D2-4CC6-9B0F-5394A81F9B98_="
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/E8_y8Vq27qje2bkQ0aHm_gdc1MI>
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 21:57:18 -0000

Brian,

Short answer is:  yes.

Longer answer:   Repeatedly.  Within ISOC, and as the IETF owning more 
of its own efforts in the sponsorship program.

It’s not an easy relationship to explain to people who just need to 
know enough about us to recognize our value to them, and where to send 
the cheques.  And, as you likely know, this kind of friction is the last 
thing you want in a discussion about organizational support, because as 
soon as eyes glaze over, chequebooks go back into pockets.

Leslie.

-- 

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises
ldaigle@thinkingcat.com
-------------------------------------------------------------------

On 16 Feb 2018, at 16:20, Brian Carpenter wrote:

> Andrew,
>
> Yes, I have seen these arguments and I understand them. And I'm not
> in the least criticising the I* for trying to find a fix. It's the
> complexity and cost of the fix that concerns me.
>
> Have we tried the cheap fix, which is a carefully written primer for
> potential sponsors?
>
> Regards
>    Brian
> On 17/02/2018 08:23, Andrew Sullivan wrote:
>> On Sat, Feb 17, 2018 at 08:07:46AM +1300, Brian Carpenter wrote:
>>>
>>> But the only concrete example I've seen is the minor hassle that ekr
>>> just mentioned.
>>
>> If you haven't seen them, then it seems it's because you're not
>> reading the examples already raised.  But, for instance,
>>
>> 	- because the contracts have to be between ISOC and others, the
>> 	signing authority must be employed by ISOC, not us.
>>
>> 	- because the contracts are let by ISOC, it appears to donors and
>> 	sponsors that money to the IETF is fungible funds given to ISOC.
>>
>> 	- it causes confusion among vendors as to whom they are dealing
>> 	with.
>>
>> 	- the minor hassle could actually lead to a large hassle in a
>> 	future case so far unexperienced.
>>
>> Having the ability to make decisions independently comes with some
>> costs. It seems plain you don't think those costs are worth bearing,
>> but I also think it is unfair for you to dismiss the issues others
>> have raised as being "minor hassles".  You're not now the one who
>> faces the community when things don't happen because ISOC's needs and
>> the IETF's needs are imperfectly aligned.
>>
>> Best regards,
>>
>> A
>>
>
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20