Re: Want to be on the IESG?

"Salz, Rich" <rsalz@akamai.com> Mon, 04 October 2021 14:05 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 2073F3A074E for <ietf@ietfa.amsl.com>; Mon, 4 Oct 2021 07:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-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 (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 dohTWqsMe3su for <ietf@ietfa.amsl.com>; Mon, 4 Oct 2021 07:05:29 -0700 (PDT)
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 0900B3A0774 for <ietf@ietf.org>; Mon, 4 Oct 2021 07:05:28 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.1.2/8.16.1.2) with SMTP id 194Ao12n030810; Mon, 4 Oct 2021 15:05:25 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=TOFKZdEsdSmQEMdlk8tCxUff6yX/hTlSn6OZCNXPiDw=; b=fHBUWvfAcMnTQ5y9m9c41AhHbnaoVYVRNB/vMTp8W2rLAZgNCNZY2UWwfdRLbYKSw13o G+410huJDL0lFiRm4vGnH5uBD40YGthodd4yTb0QEy8BfYsZeQdw5RdY25xUEXQYr95x sRLhxsNEAbykbfbbSMtXeVz4Z7cfAEc5MAPZ/o878AJ7hwcrutTIZKCZ2lAbVCFe7nUS LpFsv86HDsLKqyrEJl2TftclPDRjpus1docslVEXZjLWfTWj3WhZ8dutzzKVvAww0nTD QfPH0sDj0MXn7hnllwqjXJ3mo3ELXw8mZ3W40WvxanzdPZdUg4oW5BPfLMBYhkJTueUV xw==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 3bfn0t2x5u-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 04 Oct 2021 15:05:25 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 194E5OSw013590; Mon, 4 Oct 2021 10:05:24 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.57]) by prod-mail-ppoint2.akamai.com with ESMTP id 3bejrybk3k-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 04 Oct 2021 10:05:24 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Mon, 4 Oct 2021 10:05:21 -0400
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.023; Mon, 4 Oct 2021 10:05:21 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: John C Klensin <john-ietf@jck.com>, Donald Eastlake <d3e3e3@gmail.com>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: Want to be on the IESG?
Thread-Topic: Want to be on the IESG?
Thread-Index: AQHXts80IgZb0X0JKkulxwbn/iKb5Ku/JysAgANhQoCAAJhMAP//w2MA
Date: Mon, 04 Oct 2021 14:05:21 +0000
Message-ID: <6D74EDE3-0F73-4C97-B9CC-65624BF95FF9@akamai.com>
References: <2A8C8B98-CBA9-4BF0-82C5-594B0F309F07@akamai.com> <FA5A7C084BDEF72CE3FC510B@PSB> <CAF4+nEG1-isV2aKgrtFE=Yv2RNyv-XP=ysN3ZeE-H8bNTykx7g@mail.gmail.com> <9A7FD2DE22C1D2ED1AB9E21D@PSB>
In-Reply-To: <9A7FD2DE22C1D2ED1AB9E21D@PSB>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.53.21091200
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A788CB92F26B2E4BBC10B82682AA850F@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-10-04_04:2021-10-04, 2021-10-04 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 suspectscore=0 adultscore=0 malwarescore=0 mlxscore=0 bulkscore=0 spamscore=0 mlxlogscore=597 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2109230001 definitions=main-2110040097
X-Proofpoint-GUID: sIOsLi0a9Wmp6A8emsrS-JyojUV0M0bg
X-Proofpoint-ORIG-GUID: sIOsLi0a9Wmp6A8emsrS-JyojUV0M0bg
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.182.1,Aquarius:18.0.790,Hydra:6.0.391,FMLib:17.0.607.475 definitions=2021-10-04_04,2021-10-04_01,2020-04-07_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 clxscore=1011 priorityscore=1501 mlxscore=0 phishscore=0 bulkscore=0 adultscore=0 suspectscore=0 lowpriorityscore=0 impostorscore=0 spamscore=0 mlxlogscore=530 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2109230001 definitions=main-2110040097
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ij0pA0qkiY_NdX58IYKL_fiTWUo>
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: Mon, 04 Oct 2021 14:05:35 -0000

>    then making a big deal about getting additional candidates for a
    slot that will almost certainly be returned to the incumbent
    (because they are completing their first term and have done a
    competent job) may actually discourage candidacies for other
    positions because, unless people clearly understand the
    distinction between first-term and later incumbents -- a
    distinction those public calls rarely make-- the impression is
    that there is no point being a candidate against an incumbent
    unless one is prepared to argue that incumbent has done a bad
    job. 

When I was first asked to stand for Security AD, I was told that I should consider this a practice run for future because it was almost definite that the current incumbent was going to be re-selected. I don't know if that is, or was, still commonplace. Perhaps it should be. It has to be a negative impact on the nominee pool, however. Because it means that if you want to be an AD, you have to convince your employer that it will be a couple of years of nearly-full-time commitment, but not immediately. That means convincing them at least twice.

The public information about candidates should include all previous nomcom-selected positions they've had. It should be fairly simple to link the nominees to their "dt.ietf/org/person/Lars%20Eggert" page, for example.

More importantly, I notice many of these same suggestions being made annually.  The only forum we have for preserving these things is the previous Chair's recommendations, which doesn't seem good enough.