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

Jari Arkko <jari.arkko@piuha.net> Tue, 11 July 2017 22:40 UTC

Return-Path: <jari.arkko@piuha.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 D9D3F1317E4 for <iasa20@ietfa.amsl.com>; Tue, 11 Jul 2017 15:40:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 srqFJAai7Vyu for <iasa20@ietfa.amsl.com>; Tue, 11 Jul 2017 15:40:15 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 256E912EC15 for <iasa20@ietf.org>; Tue, 11 Jul 2017 15:40:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3CE242DB68; Wed, 12 Jul 2017 01:40:14 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3cMj6rLfNBZ1; Wed, 12 Jul 2017 01:40:13 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTP id 9CD792DB67; Wed, 12 Jul 2017 01:40:13 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_3936EEBE-2A3D-48D8-BDF8-BB40901746E7"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CABtrr-X6rENwvScwJJCLO9XrgDDBLtw_v_G3PxQZhdHiB6xuew@mail.gmail.com>
Date: Wed, 12 Jul 2017 01:40:11 +0300
Cc: "iasa20@ietf.org" <iasa20@ietf.org>
Message-Id: <B351229A-72C2-433B-BC19-C35099491EF6@piuha.net>
References: <CABtrr-VtbzvTuBxV1y8910m8zPNi53CWVKd9NGpvAfprwc8iEA@mail.gmail.com> <CA+9kkMDa1gkyeywF9zNa3Z3w5FDuD=J9p3fW_pPaQtoLsUXM5Q@mail.gmail.com> <CABtrr-X6rENwvScwJJCLO9XrgDDBLtw_v_G3PxQZhdHiB6xuew@mail.gmail.com>
To: Joseph Lorenzo Hall <joe@cdt.org>, Ted Hardie <ted.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/wIy1AuQy0snnKgk_YgkjwoMSRJ0>
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: Tue, 11 Jul 2017 22:40:18 -0000

What Joe said.

Despite what the document may be saying, we did think of the nature of the
IAOC decision making and ISOC relationship as two different dimensions of
the solution space. They are related, but not bound to each other. My personal
opinion is that there absolutely needs to be a change in what the scope of
community-filled oversight board does from what they are doing today,
irrespective of what happens in the ISOC interface.

Ted wrote:

> Changes in the relationship to ISOC might be useful for clarity in fund raising, in financial management, and in other structural things …

Well articulated.

> Many different board types dive in and out of the weeds and selecting a new type thus may not help us avoid that.   Avoiding that requires understanding what drives a board to drill down and what keeps them in that path after (in our case, I suspect it was initially concerns over capture and eventually precedent).

Good points. It wasn’t the intent to claim that a change in the ISOC
interface would bring about a change in board behaviour, we were
trying to ask for an independent change in the scope of the board.
Your point about board’s official role not necessarily driving this
sort of behaviour is valid. Would be interested in your thoughts
(you now also being an IAOC member) on how to change that
in this particular case.

Also:

> Make no mistake, I agree that there is change needed along this axis.

Let me ask a clarifying question. Since again you’ve now seen
the insides of IASA, do you personally agree that this is at least
a part of the problem we are having:

> … one key concern is that the type of oversight exercised by the IAOC may not be appropriate.  Some folks feel that it is working at the "decision by decision" level rather than in the "strategic, goal-setting level" mode and that this contributes to a series of other issues (speed, transparency, and consistency all being effected) ...

Jari