IETF Logo Mail Archive

Re: [ietf-nomcom] NomCom 2023 Extension of Nomination Period to 2023-10-12

"Salz, Rich" <rsalz@akamai.com> Fri, 29 September 2023 18:09 UTC

Return-Path: <rsalz@akamai.com>
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 A2E60C15154E; Fri, 29 Sep 2023 11:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.805
X-Spam-Level:
X-Spam-Status: No, score=-2.805 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kjNDZWea9lnv; Fri, 29 Sep 2023 11:09:22 -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 8DE46C14CE4A; Fri, 29 Sep 2023 11:09:22 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.17.1.22/8.17.1.22) with ESMTP id 38TEC3M8022162; Fri, 29 Sep 2023 19:09:22 +0100
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:content-id:content-transfer-encoding:mime-version; s=jan2016.eng; bh=D9u3+p9vSKTYYiSqGisydT5DCjjd2D7RUyQAcN6IlaE=; b= hrbKFQvCSWr6gLlK+D5wGShrw3nsWzuveJ05i+xiXx4ahodD+fpp+oXy2oDQXzxD gH9mK4h+rQ9BcxIRHZUMqR0tfhdfwmoFU2GSOv/+D4AfusOmAlbFu/gKUMxoPi+A ix1FyehR9u24la//0Z+dSON/dRNs9Qq1eAWrg49KZOQx6KnRDiPVw8AomejBvRf2 lSULhMf9pyrKk1YC4Ul9ryx1se1qqo2+9eboWMBDlBGd7MYVKKRuhgwWi4auOtxk wjDRR161SOsxk1HPBb7/oO/sqi2xbJxWrrmwUfSGfzrvuMclaXpERZKqj8usqbPg MfzR5kmEC2d2oksqqCh83Q==
Received: from prod-mail-ppoint3 (a72-247-45-31.deploy.static.akamaitechnologies.com [72.247.45.31] (may be forged)) by m0050095.ppops.net-00190b01. (PPS) with ESMTPS id 3tdug2wm7e-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 29 Sep 2023 19:09:21 +0100 (BST)
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.17.1.19/8.17.1.19) with ESMTP id 38TGY1AF021903; Fri, 29 Sep 2023 14:09:20 -0400
Received: from email.msg.corp.akamai.com ([172.27.50.207]) by prod-mail-ppoint3.akamai.com (PPS) with ESMTPS id 3tacwybuq2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 29 Sep 2023 14:09:20 -0400
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com (172.27.50.203) by ustx2ex-dag4mb8.msg.corp.akamai.com (172.27.50.207) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.25; Fri, 29 Sep 2023 11:09:19 -0700
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) by ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) with mapi id 15.02.1258.025; Fri, 29 Sep 2023 11:09:19 -0700
From: "Salz, Rich" <rsalz@akamai.com>
To: John C Klensin <john-ietf@jck.com>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Michael StJohns <msj@nthpermutation.com>, "ietf-nomcom@ietf.org" <ietf-nomcom@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Thread-Topic: [ietf-nomcom] NomCom 2023 Extension of Nomination Period to 2023-10-12
Thread-Index: AQHZ8arLeCrml3IAUEWzQdTYjnnprrAv8BAAgAAHdACAAP5ZgP//vvqAgABG6AD//8EBAIAAWRuA//+9iIAAL3ZHAA==
Date: Fri, 29 Sep 2023 18:09:19 +0000
Message-ID: <93CDF775-0F24-4046-8E2C-57695C91B0AE@akamai.com>
References: <169586436096.57370.9087034672258353524@ietfa.amsl.com> <b50bb5d9-7f2b-5260-f04f-44561794d68c@comcast.net> <325534a5-8a69-4b8e-bf69-d1a656db2c19@betaapp.fastmail.com> <ffb9a9bb-5a8d-8d24-1549-6d00b8115aec@nthpermutation.com> <F77FEBE2-A323-4B3B-9AD1-F5D5E7A189B2@akamai.com> <deb58221-f245-0404-f3d0-132f16a6c512@nthpermutation.com> <0024EBA9-5174-4030-B69A-FFA52C602C2E@akamai.com> <8B3524ED5D57C7C43CBF0A5E@PSB> <F8AEC554-C3BE-4AC7-8BEB-4118C8B1976B@akamai.com>
In-Reply-To: <F8AEC554-C3BE-4AC7-8BEB-4118C8B1976B@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.77.23091003
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A378B88FE654884BA3DAA51E539DEBD6@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.267,Aquarius:18.0.980,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-09-29_16,2023-09-28_03,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 phishscore=0 malwarescore=0 mlxscore=0 bulkscore=0 mlxlogscore=568 adultscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2309180000 definitions=main-2309290156
X-Proofpoint-GUID: orsZvkjoydrJPldkXJ-r0k_m873vv5fZ
X-Proofpoint-ORIG-GUID: orsZvkjoydrJPldkXJ-r0k_m873vv5fZ
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.267,Aquarius:18.0.980,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-09-29_16,2023-09-28_03,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 clxscore=1015 bulkscore=0 lowpriorityscore=0 mlxscore=0 phishscore=0 priorityscore=1501 adultscore=0 impostorscore=0 mlxlogscore=601 suspectscore=0 spamscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2309180000 definitions=main-2309290156
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/-bQjic8JSEmyt3ZBBzO_TSiugvM>
Subject: Re: [ietf-nomcom] NomCom 2023 Extension of Nomination Period to 2023-10-12
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 29 Sep 2023 18:09:26 -0000

> Thanks everyone for the information.

Thinking about it some more, I want to re-ask the question as it were:

Mike wrote:

> By virtue of their position in the process, the Nomcom and the
confirming bodies have an ability to say something about the job
descriptions.

I guess I was hung up on "say something" and took it to mean revise/modify/edit, etc.

Sure, NomCom and the confirming bodies can interpret the job description and fill it how they want. But if they decide to *change the wording* or *disregard the input* I would expect the IESG liaison and the IAB confirming body would raise issues, unless they agreed with NomCom's interpretation.  Yes, the general IETF community can provide feedback that says "the job description is wrong, we don't need an AD DogCatcher we need an AD CatCatcher" Presumably they might do that earlier, when the job descriptions are posted, rather than later. But I don't see the IETF community ever really doing that in enough force that NomCom would say "you're right, we'll look for a good CatCatcher."

v2.23.0 | Report a Bug | By Email