[Eligibility-discuss] Suggestions for nomcom chair selection?

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 14 August 2020 19:21 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 4FC753A11F2 for <eligibility-discuss@ietfa.amsl.com>; Fri, 14 Aug 2020 12:21:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, 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=yitter.info header.b=TYIdiBzN; dkim=pass (1024-bit key) header.d=yitter.info header.b=MtxNCePz
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 vextEwUjdjXg for <eligibility-discuss@ietfa.amsl.com>; Fri, 14 Aug 2020 12:21:50 -0700 (PDT)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57E723A11F0 for <eligibility-discuss@ietf.org>; Fri, 14 Aug 2020 12:21:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 4B33ABD5C8 for <eligibility-discuss@ietf.org>; Fri, 14 Aug 2020 19:21:49 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1597432909; bh=dMHCHL6irAeaIiBCFMo9Pif+ap2/vYHxrbcQ1hfPA2c=; h=Date:From:To:Subject:From; b=TYIdiBzNSnI1j5n5g8MsHme7Tr735mTjUhLUfhUAKViqN/cusbYuaUY0tDAmR/uzn KziqPkZQRM3JyTzRSfSncTF9RbP23lfCRH5Iglwi6gJi0wlupYUUPpsl0rkeHviZJs XlmvwXnRL1V4BVB2Bgsxi8QQMYLicrrfBtA6yPzI=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uVCJ1duJ_INa for <eligibility-discuss@ietf.org>; Fri, 14 Aug 2020 19:21:47 +0000 (UTC)
Date: Fri, 14 Aug 2020 15:21:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1597432907; bh=dMHCHL6irAeaIiBCFMo9Pif+ap2/vYHxrbcQ1hfPA2c=; h=Date:From:To:Subject:From; b=MtxNCePzdGSiRzZMOhDc2khEIlINa0z+PMx5cE6iKqTsWLYetse/HyfDzLpnAKShb kzqdGIiZVnWooF1CNjUlQNAs9L/QO8BWkh1D6ZFl/jeMeDZjOPbIvy7M6WlKWtihXW mNQSzeOUHH12UStuSjtpNNymz5zAqxVU4CBpOF6A=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: eligibility-discuss@ietf.org
Message-ID: <20200814192145.iiuoma7a3frf7mm7@crankycanuck.ca>
Mail-Followup-To: eligibility-discuss@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/W0CKX1hR_kquQlSWxP9GuKL0xfQ>
Subject: [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: Fri, 14 Aug 2020 19:21:52 -0000

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 criteria will mean 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