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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sat, 28 October 2017 14:36 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 4A9E213F571 for <ietf-nomcom@ietfa.amsl.com>; Sat, 28 Oct 2017 07:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 qFMRWnphlbiH; Sat, 28 Oct 2017 07:36:51 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 227E31394FB; Sat, 28 Oct 2017 07:36:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 47D4BBE4D; Sat, 28 Oct 2017 15:36:49 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWzNV-L92x7A; Sat, 28 Oct 2017 15:36:47 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 6E9D5BE4C; Sat, 28 Oct 2017 15:36:47 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1509201407; bh=/wY3M4h43GOcCZCXTUCdzqkSuvwpmjdh8qbZ2YX/5Go=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=V0BM72OaRm1fLC8SuiY9akcS8KQF64SRVzZNHSSmySBJDszaENE07lolj6RlVkUpC nLL+2ZvlF2wTPSWXI7irbTTu0S8xoKGO5KqGV8Wfe8mx+sRQJ8/cH16S3ZkLHFaYR0 t5wBf2zCnpByOcHh9idtSqySyOaFQSl7q79hZcos=
To: "Salz, Rich" <rsalz@akamai.com>, Peter Yee <peter@akayla.com>, 'John C Klensin' <john-ietf@jck.com>
Cc: 'NomComDiscussion' <ietf-nomcom@ietf.org>, 'NomCom Chair 2017' <nomcom-chair-2017@ietf.org>
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>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <5c51ab08-13f7-0579-6d1e-4e73575c10e4@cs.tcd.ie>
Date: Sat, 28 Oct 2017 15:36:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <C2001C2C-567F-4BBA-8549-26F8D25DC1A3@akamai.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="GsFufrxioOJJT3trHf5MkuHGQXcueGQdT"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/F1o6HarukWH5UFMtsN-w6y1b-6c>
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: Sat, 28 Oct 2017 14:36:53 -0000

Hi Rich,

On 28/10/17 15:06, Salz, Rich wrote:
> I think it will be worthwhile, after the process is done, to have
> some kind of report about what it was like with all the non-voting
> liaisons, and I hope you’ll do that.  Six out of 16 are in that
> group, and it seems very high to this outsider.

I was IESG liaison to a nomcom a couple of years ago.

AIUI, the non-voting folks other than the chair were there to
offer information to the voting members when asked, but not to
steer. We were also there to provide re-assurance to the
relevant bodies (the IESG in my case) that the process inside
nomcom was well run and to help handle confirmation of selected
folks. (I don't recall any IESG liaison coming back to the IESG
saying anything other than that year's process had been well-run
for the 6 years I was on the IESG.)

I forget if that's written down in the BCPs or not, but it seems
useful for nomcom to have folks in those roles, and maybe more
than useful for bodies (IESG,IAB,ISOC board) that confirm selected
folks. Without a liaison, it might be just too easy for a
confirming body and a nomcom to hit near deadlock, due to the
mechanics of handling the confidentiality involved.

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.

As a minor point the non-voting folks I think have also sometimes
been logistically useful when it comes to the November IETF meeting,
when there's a lot of running about and interviewing going on. If
fewer people had to do all that, it might not work as well.

S.



> 
> 
> _______________________________________________ ietf-nomcom mailing
> list ietf-nomcom@ietf.org 
> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>