Re: [Iasa20] draft-haberman-iasa20dt-recs-00.txt

Lou Berger <lberger@labn.net> Sat, 15 July 2017 13:01 UTC

Return-Path: <lberger@labn.net>
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 7476C129B4B for <iasa20@ietfa.amsl.com>; Sat, 15 Jul 2017 06:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 uKM_trZswssn for <iasa20@ietfa.amsl.com>; Sat, 15 Jul 2017 06:01:34 -0700 (PDT)
Received: from gproxy4.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) (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 930B6126D73 for <iasa20@ietf.org>; Sat, 15 Jul 2017 06:01:34 -0700 (PDT)
Received: from CMOut01 (unknown [10.0.90.82]) by gproxy4.mail.unifiedlayer.com (Postfix) with ESMTP id EB1B417617E for <iasa20@ietf.org>; Sat, 15 Jul 2017 06:58:00 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with id l0xx1v0012SSUrH010y0kq; Sat, 15 Jul 2017 06:58:00 -0600
X-Authority-Analysis: v=2.2 cv=FvB1xyjq c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=G3gG6ho9WtcA:10 a=48vgC7mUAAAA:8 a=heT85LjycNxKoE24u78A:9 a=3g94yIJ_w0CQ0RSU:21 a=Zw-yPWCCawpkp1yy:21 a=QEXdDO2ut3YA:10 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=4cyhpPt6JyuSuDZoo/Pype9q6fcWsUxG9CQ7NKqXzQs=; b=KvwMF4oQNJVPYnr6HxUniSNDo6 nU83dBt1zHXNg7/4jl8KD2821Y9nP5qkvWaJ0HSe+HGNwEnHjKTAdFWp3f+ZO6TJSfd27E3XRJgJb j71uPKExZBUuiwfKIQVtEQgXk;
Received: from pool-100-15-84-20.washdc.fios.verizon.net ([100.15.84.20]:57966 helo=fs2.dc.labn.net) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1dWMdw-0005gY-SK; Sat, 15 Jul 2017 06:57:56 -0600
To: Bob Hinden <bob.hinden@gmail.com>, "iasa20@ietf.org" <iasa20@ietf.org>
References: <CABtrr-VtbzvTuBxV1y8910m8zPNi53CWVKd9NGpvAfprwc8iEA@mail.gmail.com> <CA+9kkMDa1gkyeywF9zNa3Z3w5FDuD=J9p3fW_pPaQtoLsUXM5Q@mail.gmail.com> <CABtrr-X6rENwvScwJJCLO9XrgDDBLtw_v_G3PxQZhdHiB6xuew@mail.gmail.com> <B351229A-72C2-433B-BC19-C35099491EF6@piuha.net> <CA+9kkMBzgOY+K2w1Yhk3B9irGaMo4CRrJ2kT+oAXRUhLwW0ukg@mail.gmail.com> <D146FE44-3263-4379-A4DB-D89E3624C9B8@piuha.net> <90E524B1-730D-4F29-8987-3D0DBE5380E5@gmail.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <f9fae915-18c5-a203-2e65-ff489d894702@labn.net>
Date: Sat, 15 Jul 2017 08:57:55 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <90E524B1-730D-4F29-8987-3D0DBE5380E5@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.84.20
X-Exim-ID: 1dWMdw-0005gY-SK
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-84-20.washdc.fios.verizon.net (fs2.dc.labn.net) [100.15.84.20]:57966
X-Source-Auth: lberger@labn.net
X-Email-Count: 8
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/XpAsKPU3ea2d-6u2wl4JZvvD7mA>
Subject: Re: [Iasa20] draft-haberman-iasa20dt-recs-00.txt
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: Sat, 15 Jul 2017 13:01:36 -0000

Bob,
	+1 for your comments on considering financial impact; they resonate
with me.

Lou

On 07/15/2017 08:08 AM, Bob Hinden wrote:
> [Resend without Draft in the Subject, please respond to this one]
> 
> Hi,
> 
> I finished reading the draft and have some comments I would like to share.
> 
> I think it is an oversight in the document to not discuss the financial implications of the different models.  It’s most significant in the Independent organization, but they all have financial impact.  Creating an ISOC subsidiary or Independent organization will have a significant financial impact and should be part of the discussion.  Where will the money come to pay for the increase?  I think it’s critical to understand the financial implications of the different model.
> 
> The current expense level (from 2017 IASA budget) is a little over $7M a year (including indirect ISOC contributions of staff).  ISOC contributes about $2.2M to make up the difference revenue and expenses.  I don’t know how much additional an independent organization will cost, but I suspect it will be a large number.  It’s going to have to cover new staff, insurance, overhead of running a corporate entity (filing taxes, HR, corporate reporting, etc.), etc.  New issues will be created, for example will a venue want to sign a contract with the new IETF org it has never heard about before and doesn’t have a credit rating?
> 
> I agree we have a fund raising problem, but it’s not going to be fixed simply by adding a Director of Fundraising.  The problems are more structural and caused by changes in the industry.  We recently all saw a large company that provided significant support for the IETF, layoff many long time IETF contributors.   We need to come up with better ways of show the value the IETF brings to the Internet.  Essentially, how do we sell the value of IETF to potential donors?  This isn’t fixed by reorganizing ourselves.
> 
> Significantly increasing the cost of the IETF without knowing how expensive the new plan is, or knowing how it is going to be paid for isn’t going to work well.  If we want to be an independent organization, we need to also be responsible for the finances.  We have lived in a world were decisions were made without thinking about how much they will cost.  No cost benefit analysis.  If the IETF is going to be an independent organization, that culture will have to change.
> 
> One of the issues raised in the document is the difficulty of the NomCom finding qualified volunteers for the IAOC.  Unless we can understand how to fix that, how is the NomCom going to fill positions on a Board of Directors?   It’s only going to become worse.
> 
> Another thing the IETF is not very good about is managing staff.  That is, writing performance reviews, setting appropriate goals, fairly judging their performance, replacing them as needed.  If we are going to have more staff, then this needs to be dealt with.  It’s hard for volunteers to manage paid employees.
> 
> I think it’s important that the IETF Trust should be kept of of this.  It is working, it has a bank account, and is doing well holding the IETF IPR, and IANA trademarks and domains.  Bringing it into some sort of new IETF organization, might well cause the ICANN community to reconsider moving the IANA trademarks and domain there.  Let’s not go there, the rest of this is hard enough.  At some point, we might consider having the IETF Trust have a set of trustees who are not the same as the IAOC.  But again, that doesn’t need to be done now.
> 
> Bob
> 
> 
> 
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>