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

Ted Hardie <ted.ietf@gmail.com> Wed, 12 July 2017 16:29 UTC

Return-Path: <ted.ietf@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 EBFD613172E for <iasa20@ietfa.amsl.com>; Wed, 12 Jul 2017 09:29:59 -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, HTML_MESSAGE=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 p2qY6Oe8zzMP for <iasa20@ietfa.amsl.com>; Wed, 12 Jul 2017 09:29:58 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 2BB1D1300CF for <iasa20@ietf.org>; Wed, 12 Jul 2017 09:29:58 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id a66so15231036qkb.0 for <iasa20@ietf.org>; Wed, 12 Jul 2017 09:29:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LuLnghV5/+Ic4BT26OrCbv3UBRkL5srH38OrCszJfGY=; b=opzs/TsYM63w4FTjn88J3Mvw+z7+OhI2ZgbozM9mV7Pg47VorVlTuY/MAchh9EzvQA jMolDhNxZa6C6o5LCJTvOjnJ8oiRnUWUCHfzhJZsLUlw88q6gykCabKisXqt0mXIinwr gK25ctG8opAeHbIF3PYsbTPa3AEeh9kUHAbdjIOZjCBrJI7f1UHz5gW3LmYkwdwcmGPB c2ZDogT/N4AayH733jzDxCvNmALiTSKIARr15fYkGWpI31m61b2ylOsguQwKfxlAIRK9 IcWIWIiOAJIxJBxVVTNnYT/lBncRhC9br9a7NnNdr0fEcgL7zBxXSnb6h4o8seWdLJFn +zSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LuLnghV5/+Ic4BT26OrCbv3UBRkL5srH38OrCszJfGY=; b=CPYbnK8Y9yAMp711Tj0GPfml02PyVYEwOLQmRRTX1iwjAjnz8vXJk6t1pkr5dO2+1M Bsymyrao5/PFtNyDB6ppkPq+F/fgCM8Exxikd1EfVs65dzgnNQW98BOshNep3W2LbGhx 1LDp9BIDQTtCe9IQTyOzGOeBXGl6uzrVkVqPNitZTJnL4TLcfY+9j8/8l9vMgTEI5xQr 1/q3wU63C5hRJKi5oJaRvtnFSHKLryDD/wF/4OQx+6ScVa3YG3IDlCLvcm9odG8cBY3E ywQjROcVxw4LcjOUZYp/edMeTdZNRacZr3Q+HA2d27d3Unp6Mt8RNg7rYhoONsaBYPHe mKWQ==
X-Gm-Message-State: AIVw113V689UUtFGnGIrBbSR1zVkIr/4/pKpGsCm/FQ1sl/v5Lao4YEb 4FjZtGcWdGKhNiJcHrooAAw3jQWH2g==
X-Received: by 10.55.24.146 with SMTP id 18mr6903131qky.190.1499876997093; Wed, 12 Jul 2017 09:29:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.4.21 with HTTP; Wed, 12 Jul 2017 09:29:26 -0700 (PDT)
In-Reply-To: <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> <B351229A-72C2-433B-BC19-C35099491EF6@piuha.net>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 12 Jul 2017 09:29:26 -0700
Message-ID: <CA+9kkMBzgOY+K2w1Yhk3B9irGaMo4CRrJ2kT+oAXRUhLwW0ukg@mail.gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Cc: Joseph Lorenzo Hall <joe@cdt.org>, "iasa20@ietf.org" <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="001a1142df1c9e5e550554215370"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/DlUMlXwDDYrRL8oA1Y2DrbEBayA>
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: Wed, 12 Jul 2017 16:30:00 -0000

On Tue, Jul 11, 2017 at 3:40 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

>
> 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.
>

Scope is an interesting problem here, because in some of these structures
(Subsidiary and independent org), a board will have a fiduciary duty to the
organization.  That duty defines the scope to a very great degree.  The
issue
isn't with scope, at least in my view, but with a combination of mechanism
and culture.



> 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:
>
>
I have not been part of the IAOC for very long, so my opinion is mostly
shaped
by experiences outside it.  My take with that combination of experience is
that
the IAOC could not suddenly revert to a more strategic approach right now,
because many
of the processes and committees it has are built around the current way of
working.
I do think that it could move to a more strategic approach (as, IASA++
suggests)
if  a new set of support systems were in place.  The trick, and it will be
trick, is making
sure that the change goes with the adoption of the support systems *because
it will
not be an inherent part of that change*.  Some combination of personnel
changes (like
dropping the number of ex officio members), new instructions to NomCom, and
very
active recruitment of outside talent will be required.  That is likely
true, honestly, whatever
structural changes we put in place.

Obviously, this is my personal opinion, and should be taken with a bit of
"still a newbie at this"
weighting.


regards,

Ted

> > … 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
>
>