Re: [ietf-nomcom] Experiment in "full transparency"

John C Klensin <john-ietf@jck.com> Sun, 12 November 2017 17:25 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf-nomcom@ietfa.amsl.com
Delivered-To: ietf-nomcom@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4CD6126B7F for <ietf-nomcom@ietfa.amsl.com>; Sun, 12 Nov 2017 09:25:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 eh_La2cTavUD; Sun, 12 Nov 2017 09:25:09 -0800 (PST)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B4DF12008A; Sun, 12 Nov 2017 09:25:09 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eDw0C-0002Zu-1j; Sun, 12 Nov 2017 12:25:00 -0500
Date: Sun, 12 Nov 2017 12:24:55 -0500
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Salz, Rich" <rsalz@akamai.com>, Peter Yee <peter@akayla.com>
cc: 'NomComDiscussion' <ietf-nomcom@ietf.org>, 'NomCom Chair 2017' <nomcom-chair-2017@ietf.org>
Message-ID: <439F201200F4BC596F7A0343@JcK-HP5.jck.com>
In-Reply-To: <5c51ab08-13f7-0579-6d1e-4e73575c10e4@cs.tcd.ie>
References: <6.2.5.6.2.20171016135236.12dcaa60@elandnews.com> <3E158B61-DCF7-485C-B350-DA14B2B8CBDA@akamai.com> <CAA=duU0aiLUzZAP3vmS2tTzxEinzc4hA0UFpd3_dprkjDHnqkg@mail.gmail.com> <FF365C9F-6CE1-41A5-82BB-F15CFB748492@akamai.com> <CAA=duU2k+8-+M2vj5Tk_czJA_VL0ZJ8Z8xhpo0zqu-JqY7mWNQ@mail.gmail.com> <8CB73C9E-9BF2-4252-A98A-D5AA1FE597DC@akamai.com> <DE6132DBB7813E23C606B56B@PSB> <5BDAF4B0-FE20-4940-B436-683209FAC9C9@akamai.com> <70A26384995DDC19DC8E2CAC@PSB> <09f301d34fb0$fe5925d0$fb0b7170$@akayla.com> <C2001C2C-567F-4BBA-8549-26F8D25DC1A3@akamai.com> <5c51ab08-13f7-0579-6d1e-4e73575c10e4@cs.tcd.ie>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/kyn93wxpTCWOcRKW_Gnkn1GMLZk>
Subject: Re: [ietf-nomcom] Experiment in "full transparency"
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-nomcom/>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Nov 2017 17:25:11 -0000

Sorry for the slow response to this, but I've been preoccupied
with other issues and more specific comments...

--On Saturday, October 28, 2017 3:36 PM +0100 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>...
> The reason for this mail though is that I figure the utility of
> the liaisons increases as the voting members are less
> experienced IETFers. Highly experienced voting members could
> likely get by with fewer liaisons, but if we're more likely to
> have less experienced voting members the non-voting folks seem
> to me to be a thing to be very careful about ditching, even if
> 6/16 seems like a lot.

I think this is true.  At the same time, having liaisons present
who explain "how things work" in the relevant bodies creates an
inherent bias toward keeping them working that way, possibly as
well as reinforcing some tendencies toward returning incumbents
(if only in the interest of stability and continuity).

Those are not necessarily bad things, but the Nomcom also has
considerable responsibility for determining the strategic
direction of the IETF (IAB included) by the choices it makes.
That makes possible discussions along the lines of lines of "is
that group doing what we want as a body (or even set of ADs) or
is it time to seat a new group that will set new directions"
important.   Liaisons who represent, and are expected to
advocate for, the incumbent body and its definition of what it
should be doing are an impediment to such discussions even while
they may provide useful insights.

I have similar concerns about liaisons participating in
interviews.  Depending on dynamics within the leadership bodies
(not just the one a particular liaison comes from) those
liaisons may bring strong biases for or against an incumbent to
the interview or reports to the rest of the Nomcom about the
interview as well as insights into how an incumbent is or is not
effective and how they play well with others.

These are a tricky balances, both specifically and relative to
the points you make, and I think the Nomcom should be sensitive
them, and should have considerable flexibility about how
liaisons are involved, what information they have access to, etc.

best,
   john