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

Bob Hinden <bob.hinden@gmail.com> Sat, 15 July 2017 12:07 UTC

Return-Path: <bob.hinden@gmail.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 740A6131AD7 for <iasa20@ietfa.amsl.com>; Sat, 15 Jul 2017 05:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ulKdpz9iMN-z for <iasa20@ietfa.amsl.com>; Sat, 15 Jul 2017 05:07:27 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D95F131A56 for <iasa20@ietf.org>; Sat, 15 Jul 2017 05:07:26 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id f67so44336520wmh.1 for <iasa20@ietf.org>; Sat, 15 Jul 2017 05:07:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=9tbvsLz78wUBer96m2r0tTNgGJQZMjPliDRD6CBr6II=; b=hvd/B7w0haGUoYUEuQ4oLO/HZOSRSssZQUrrkMtKDeKLdeS+8ZTiRTwMq+UXzcDLLL s/iHiQ6yxmiuHQ68FqcSYMaC+EJCOpa8YxIDsJwCVwqajAP+z8PfhN1jxS8Ln8UJ6ipY QIjfCkRSRCInKE48tWSXHTfRpGg3mzNwTfw3LTNt5kVkZsUtOcsZPSRMdZB0VlXnkNvM KUh+WhKi+iGJANHmw7rZk4qdeyUiIHqi5JvQSHVXROEOCwUoBxNfWT4I6EFmmUwSs3+k KSuQCjRXSuh4gEbQSQtXtJkh4uPXbWYWBWRONk0iYbnySQXPPcJpZmn7ZBDdwpvbCFZO ZhpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=9tbvsLz78wUBer96m2r0tTNgGJQZMjPliDRD6CBr6II=; b=EjndsKGFdZMQLKfBxDI6JB1X8B9Al653bOzQd8LZjyA8CBhVrbD9UL1Qa/4dgPyrYu c0miPeHh+y8bf2OPYn/EQkddmqEIMDIbHwLMjJAttN04qctDxXVUKNNNxa1OKa6+rqV6 mlDS/9sjEsWpcvVAguuH3lUlU9Gygs9lsVvllXXxXwSkbC1Zdr7Wpi2GchpD2l9Mqwzb 3FXKdPRVs+dgZddij/K6ppOtRAD3uOnPdDvX+5uEWnzzTpZ1+yKsvKAGO2RjBlU/ww3m cr4Tt1i2DBSoci1sIEkY3k2GghDcE3ek8QAGTBqSmO/OQo92HyiXPY7cR8+XpbMktvTf YGUQ==
X-Gm-Message-State: AIVw111CrLEJjzXbj4x0MxBY3albuqt8snX8z77ga++0laqdURhSRC7n ZXAi1BiZ+IKz1Mfwo0M=
X-Received: by 10.28.97.86 with SMTP id v83mr939813wmb.74.1500120444832; Sat, 15 Jul 2017 05:07:24 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:7109:ae57:7d56:c57e? ([2001:67c:370:128:7109:ae57:7d56:c57e]) by smtp.gmail.com with ESMTPSA id 2sm7170162wrn.24.2017.07.15.05.07.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Jul 2017 05:07:23 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <77B095EB-C89A-4BAC-B4F7-4BD1D68F4B35@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_44C11507-3AC9-4D32-A6AF-594574486B46"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sat, 15 Jul 2017 14:07:21 +0200
In-Reply-To: <D146FE44-3263-4379-A4DB-D89E3624C9B8@piuha.net>
Cc: Bob Hinden <bob.hinden@gmail.com>
To: "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>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/1BkE4IhGyXDTUmApfW0eLjUvERo>
Subject: [Iasa20] DRAFT Re: 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 12:07:28 -0000

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