Re: [Eligibility-discuss] Suggestions for nomcom chair selection?

Adrian Farrel <adrian@olddog.co.uk> Sat, 15 August 2020 08:51 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7DBA3A0B75 for <eligibility-discuss@ietfa.amsl.com>; Sat, 15 Aug 2020 01:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 7WOQGIcpQD6j for <eligibility-discuss@ietfa.amsl.com>; Sat, 15 Aug 2020 01:51:26 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC95D3A0B73 for <eligibility-discuss@ietf.org>; Sat, 15 Aug 2020 01:51:25 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 07F8pDRc005464; Sat, 15 Aug 2020 09:51:13 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 1546B22044; Sat, 15 Aug 2020 09:51:13 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs2.iomartmail.com (Postfix) with ESMTPS id F406822042; Sat, 15 Aug 2020 09:51:12 +0100 (BST)
Received: from LAPTOPK7AS653V (1.196.bbplus.pte-ag1.dyn.plus.net [81.174.196.1] (may be forged)) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 07F8pC7X024772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 15 Aug 2020 09:51:12 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Andrew Sullivan' <ajs@anvilwalrusden.com>, eligibility-discuss@ietf.org
References: <20200814192145.iiuoma7a3frf7mm7@crankycanuck.ca>
In-Reply-To: <20200814192145.iiuoma7a3frf7mm7@crankycanuck.ca>
Date: Sat, 15 Aug 2020 09:51:11 +0100
Organization: Old Dog Consulting
Message-ID: <006801d672e1$3a7989a0$af6c9ce0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLR9R2A4yw3F2e8aFx/XdPoLiGZnadBz02Q
Content-Language: en-gb
X-Originating-IP: 81.174.196.1
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25604.005
X-TM-AS-Result: No--13.943-10.0-31-10
X-imss-scan-details: No--13.943-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25604.005
X-TMASE-Result: 10--13.942800-10.000000
X-TMASE-MatchedRID: yebcs53SkkDxIbpQ8BhdbPVY7U3NX8JgGbJMFqqIm9wXY+gNTubOQApV YG/kN9KL6BOMiDDOnF+m+tMEVnYS8eB5jgp3IqvErIGj0lq6L0b+RcK6KcE/TcuSXx71bvSLUK6 DcAiawdeuK2CoOfWQDokf+JWxPW2XpnMHibrMeQFZZYpuBxXlgAILzOoe9wbaO7BMOlfyKLQYtM cgj4NA2Dd9pYrMSojfO3zzFKyR0Mbtrl3Jv2BOW3T7rnt3EYkYEPlgwlUI7asjQVhmUJBUfBiKM YfGmauZxc5XBXa64JBJX0McqNha4TH1cWgHZiIlWq5hNdu7obaa3EBSlxl8oKpQzXkrsNqFfbqs +MN5rgGuuJMfEZy1kRT1WTJquodpoQm5U8PFtKT+PIg4IQlDMfiH64jt3FfEiiSKNWTejkutbk9 slw0NY4ePFWORpPsG0UA4qxORCEG2blHvx2C+qjfEJhkPJ1IaSKtQRCeqSDROr5MX40rI1ElKbD VaPbo9CnsmyjCYdb0/Gl2UPqGHkldoUl7fsaXTjKwdMGjY1SvOgC2urH8uITa3GWz2bI6yZRKub rBGI11qxDW2t0OTLAT6kckgl4G3HXTWJ1V3mfVoQhvKjFvisjm+9yH0witksQ66N9SS+88JOF1L i2DZFT9JLqb4lSiCtaB2Pv3kLHaZrzm56RA43MzSKGx9g8xhKINyBe8DNbKA6UrbM3j3qYEAY9M DLXFuSJppr/g/KEXDTdpV7Ec2zt3npSOv5LD7Z93oz43dfXELy8o3bV9yTVc/CedjlcvktNfews mJeFYZw5ucm3NLWsuT6pyURQPh5UcZtwNsCro5f9Xw/xqKXcidYBYDjITpi2QFaYS1v20qtq5d3 cxkNRvtSXvbrEoCzU66pBFl3e5GQRlu3vY8uJ6s/gJLf+ZaCqymwiZL4Ws=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/kDpaSFEuRhUbTRYSsRCqFxwRBEY>
Subject: Re: [Eligibility-discuss] Suggestions for nomcom chair selection?
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Aug 2020 08:51:28 -0000

Andrew,

Thanks first for raising this subject, and more importantly for taking
extremely seriously the job of selecting NomCom chairs.

As I read your mail there are two questions that arise:
1. How can the ISOC President continue to select quality NomCom chairs
2. Should we consider a transition to some other way of selecting the NomCom
chair

The first point will, I think, be the subject of a number of suggestions,
and you've already seen emails on the topic. It might help the discussion if
we could hear from you a brief list of qualities you are looking for. I
could suggest a number such as: history of involvement with the IETF;
familiarity with people and task management; a bit of a process wonk;
personally willing to make the commitment; funded to do the work. But it
might be better to have your thoughts rather than my second-guesses. This
list will, I believe, not be used to judge how you make the selection, but
will be helpful to the community in suggesting where you might find
candidates.

The second issue should be approached with great care. You and the past ISOC
Presidents have served us well in this respect and we should be slow to
throw that away. In addition, as others have pointed out, some degree of
separation between those appointed by NomCom and the appointment of the
NomCom chair is highly desirable. But your point that you are gradually
becoming less familiar with the IETF community is important and I can
imagine that a things develop it could get harder and harder so that even
with a list of volunteers or recommendations, it would be hard for the ISOC
President to make a reliable appointment.

Thanks again for starting this thread in good time before it is an
insurmountable issue.

Best,
Adrian
-----Original Message-----
From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org> On Behalf
Of Andrew Sullivan
Sent: 14 August 2020 20:22
To: eligibility-discuss@ietf.org
Subject: [Eligibility-discuss] Suggestions for nomcom chair selection?

Dear colleagues,

I'm the President and CEO of the Internet Society (ISOC), and I'm writing
with that hat on; but this account is where my IETF mail subscriptions
generally are so it's more convenient to use this address.

One of the things that I have been reflecting on in the discussions about
nomcom eligibility is that it would also affect the pool for nomcom chair
availability.  As you probably know, I'm responsible to appoint the nomcom
from year to year as part of my job.  When I am replaced, that person will
take over the responsibility.

My job pulls me ever more away from the IETF, and I found it challenging to
recruit and appoint the last two chairs.  I am grateful that, in my
estimation, I was able to get two people to volunteer that I thought were
well-qualified and likely to do a good job, but I'm also aware that my
familiarity with the IETF community is decreasing over time.  This is in
part due to the way the LLC has been designed, which I always understood as
intending to create a little more distance between the Internet Society and
the IETF.  In keeping with that institutional design, I have been limiting
my own participation; and ISOC has adopted a number of policies to ensure
that it is not possible for others to mistake staff participation as ISOC
control or dominance of the IETF.  But, this means that the informal
networks of connections that have historically bound the IETF and ISOC are
perhaps not as strong as they once were.  In any case, an IETF with very
different nomcom eligibility criter!
 ia will m
 ean different criteria for nomcom chairs, too, so this seems like a good
time to try to describe some sort of community mechanism to inform the
nomcom chair selection.  I could try it out for the next year, to see
whether it might be practical.

The trouble I have is that I don't really know where to start except with
the approaches I have, which are mostly informal and depend upon the
social-professional networks I have as well as those of others.  That seems
like a poor foundation on which to build, so I thought I'd ask to see
whether people here have other suggestions for a starting point.

Thanks and best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

-- 
Eligibility-discuss mailing list
Eligibility-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/eligibility-discuss