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

Joel Halpern <jmh@joelhalpern.com> Thu, 28 September 2023 18:19 UTC

Return-Path: <jmh@joelhalpern.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 756A7C1522C8 for <ietf-nomcom@ietfa.amsl.com>; Thu, 28 Sep 2023 11:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.197
X-Spam-Level:
X-Spam-Status: No, score=-7.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (1024-bit key) header.d=joelhalpern.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 C_SEKqArBEjs for <ietf-nomcom@ietfa.amsl.com>; Thu, 28 Sep 2023 11:19:20 -0700 (PDT)
Received: from mailb1.tigertech.net (mailb1.tigertech.net [208.80.4.153]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B33FC14CF1E for <ietf-nomcom@ietf.org>; Thu, 28 Sep 2023 11:19:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb1.tigertech.net (Postfix) with ESMTP id 4RxMFN1ryYz5bqRy; Thu, 28 Sep 2023 11:19:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1695925160; bh=HvXxWLm8Xo147Eb4X5z54o/sVnAFTiFvYte4MfOaf/4=; h=Date:Subject:To:References:From:In-Reply-To:From; b=Vr2UsHcSigy5c/PKq+Zai6F3DPLVR/TNVMKXEr+Z7EtiebZS7EavJ278bXoYnPrFL HfJKhayehyGbsJeCFSILZlgouRKKzEadQ4xSI9zcTRRRbzcjbXGm46UDuUxEpJ1p3f pZdfrR5J/gekEwTSlozZxJSjtf/5Xd+0OBZrmJaQ=
X-Quarantine-ID: <FNFPlNmdq2cY>
X-Virus-Scanned: Debian amavisd-new at b1.tigertech.net
Received: from [192.168.20.19] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb1.tigertech.net (Postfix) with ESMTPSA id 4RxMFM3b0rz5bqFs; Thu, 28 Sep 2023 11:19:19 -0700 (PDT)
Message-ID: <9c688aec-d923-b5d8-ba79-991fa6e491e2@joelhalpern.com>
Date: Thu, 28 Sep 2023 14:19:17 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Michael StJohns <msj@nthpermutation.com>, "ietf-nomcom@ietf.org" <ietf-nomcom@ietf.org>
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>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <0024EBA9-5174-4030-B69A-FFA52C602C2E@akamai.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/Z0hDG4cPjAU_1mVbkGLn33b8vcM>
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: Thu, 28 Sep 2023 18:19:24 -0000

As I understand it, the position descriptions from the bodies are 
requests, not orders.  If the nomcom decides that a different skill set 
is what is needed, that is the nomcom's right and responsibility.   This 
can be easily seen in the case of IAB appointments, where the nomcom 
frequently listens to the community about what skills and abilities the 
IAB needs, even when those do not appear in the job description.

On the other hand, I do slightly disagree with Mike in one regard.  The 
structuring of areas is explicitly an IESG responsibility.  So the 
nomcom is NOT free to decide that the IESG needs 3 OPS ADs and one 
Routing AD, nor is it free to make up or dissolve areas.  If the IESG 
were to undertake an unworkable reorganization, i would expect other 
remedies to be invoked.

So the overall structure is mandated to the nomcom.  But the job 
descriptions and skill expectations are advisory as I understand it.  
(Usually with significant deference, but advisory.)

Yours,

Joel

On 9/28/2023 2:09 PM, Salz, Rich 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 have never heard that from anyone before this. I wonder if others believe this, or if you are in the rough.
>
>
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom