Re: NomCom 2020 Announcement of Selections

"Salz, Rich" <rsalz@akamai.com> Sat, 23 January 2021 14:33 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A04693A1201 for <ietf@ietfa.amsl.com>; Sat, 23 Jan 2021 06:33:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level:
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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 (2048-bit key) header.d=akamai.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 yZPRtq-IERDj for <ietf@ietfa.amsl.com>; Sat, 23 Jan 2021 06:33:08 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 A016E3A11FE for <ietf@ietf.org>; Sat, 23 Jan 2021 06:33:08 -0800 (PST)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 10NEUAhI020544; Sat, 23 Jan 2021 14:33:05 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=4jvi1bsjY1cVtnTYh9fh8v1K7m5CUuUxF9JluhIewiA=; b=blq38LlPY5q7+LtB6NxGC/B6y0Gg1UfVgkdL1kDJlACw/vFJ1jxBL5+8t0gL/W+u3u8+ Zxxr+luXEZPSNuaQCRqBmP5nveA7SWe/N8RN91BIyvo4XzsGtno7jvXbTrVyXyEfC4hA 5e5nSCKy6UmGtK1yLr5FsVQ+f4uBcHas3wen65vML8X5Bk/efPhSgMUkRx5jM2ENyX3i U6KM4ICZ7Dxvwt5AZGCkWbsUMRdtOWsCGXAkW6+M2KPzMxIj1TM8afmjeGIpmpe4XJZi ggIuVrybIINeKk9H8EsCnFaGfCCTiW/fQy6ovYJEMBEoMu6A2A7q/XTzF6qtvlevK9Qz fA==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 368mknjf6s-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 23 Jan 2021 14:33:05 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 10NEMd6x028365; Sat, 23 Jan 2021 09:33:02 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.57]) by prod-mail-ppoint2.akamai.com with ESMTP id 368g12rp4w-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 23 Jan 2021 09:33:01 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 23 Jan 2021 09:33:01 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.010; Sat, 23 Jan 2021 09:33:01 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Bron Gondwana <brong@fastmailteam.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: NomCom 2020 Announcement of Selections
Thread-Topic: NomCom 2020 Announcement of Selections
Thread-Index: AQHW8CIWn5056cBTnU6OqGJaqySJIao00q+AgAB2WQA=
Date: Sat, 23 Jan 2021 14:33:00 +0000
Message-ID: <9BCB1347-3870-498C-8CE5-41AEA56004B0@akamai.com>
References: <289B641E-F445-407F-9A7D-FCDEA9698F7C@akamai.com> <437bfe25-185c-4637-ae9a-59a6ccaade99@dogfood.fastmail.com>
In-Reply-To: <437bfe25-185c-4637-ae9a-59a6ccaade99@dogfood.fastmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.45.21011103
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: multipart/alternative; boundary="_000_9BCB13473870498C8CE541AEA56004B0akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-23_06:2021-01-22, 2021-01-23 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=999 malwarescore=0 spamscore=0 bulkscore=0 adultscore=0 phishscore=0 suspectscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101230082
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-23_07:2021-01-22, 2021-01-23 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=999 bulkscore=0 spamscore=0 lowpriorityscore=0 mlxscore=0 malwarescore=0 suspectscore=0 adultscore=0 clxscore=1011 priorityscore=1501 impostorscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101230084
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.19) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RWG4bOI5k4cgvgGgqvZYZU9AozI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jan 2021 14:33:11 -0000


  *   You make some very interesting points here.  I'm interested in whether you think the issue is with the pool of available candidates who put their hands up for roles, or with the selection process not valuing diversity sufficiently.

It would have been nice to have a more diverse pool of candidates. I cannot speak about the internal deliberations of Nomcom, and I won’t, but to me, the net result is disappointing. Put another way, and I am only saying it like this to make it hopefully more obvious “given what they had to work with, they could have done better.”


  *   of the available candidates, if you had the choice, who would you have selected instead of those who were chosen?  i.e. what would your "perfect" slate have been, given the candidates that were available.

I will not answer that for a couple of reasons.  First, as I stated originally, I have no qualms with any of the individuals. Making my own slate would necessarily leave some of the selected people who, and – rightfully so – lead people to think that I did have issues with anyone left off. Second, as an IETF contributor, I will have to work with many of the current slate and I don’t see how answering that question could do anything except cause friction. Third, I don’t have enough information: I didn’t do any interviews, questionnaires are not public (well, mine was), and there was no chance to talk with a bunch of candidates.  (That last is a separate problem.)

Your point – we can’t take about fixing problems without concrete examples – is compelling, but flawed. As a CEO, I am sure that you know you can change hiring practices to get a more desirable output, without reviewing everyone who was just hired.