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

Adrian Farrel <adrian@olddog.co.uk> Thu, 28 September 2023 18:36 UTC

Return-Path: <adrian@olddog.co.uk>
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 36C15C16B5A4; Thu, 28 Sep 2023 11:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.807
X-Spam-Level:
X-Spam-Status: No, score=-2.807 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 (2048-bit key) header.d=olddog.co.uk
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 jwRuICnuOHEU; Thu, 28 Sep 2023 11:36:12 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 C771DC13AE41; Thu, 28 Sep 2023 11:36:03 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.7/8.14.7) with ESMTP id 38SIa0Sq025557; Thu, 28 Sep 2023 19:36:00 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A72454604B; Thu, 28 Sep 2023 19:36:00 +0100 (BST)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9B06C46048; Thu, 28 Sep 2023 19:36:00 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs2.iomartmail.com (Postfix) with ESMTPS; Thu, 28 Sep 2023 19:36:00 +0100 (BST)
Received: from LAPTOPK7AS653V (82-69-109-75.dsl.in-addr.zen.co.uk [82.69.109.75]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.7/8.14.7) with ESMTP id 38SIZvGQ018728 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 28 Sep 2023 19:35:59 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Joel Halpern' <jmh@joelhalpern.com>, "'Salz, Rich'" <rsalz=40akamai.com@dmarc.ietf.org>, 'Michael StJohns' <msj@nthpermutation.com>, 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> <9c688aec-d923-b5d8-ba79-991fa6e491e2@joelhalpern.com>
In-Reply-To: <9c688aec-d923-b5d8-ba79-991fa6e491e2@joelhalpern.com>
Date: Thu, 28 Sep 2023 19:35:57 +0100
Organization: Old Dog Consulting
Message-ID: <046a01d9f23a$a0b10140$e21303c0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQMg2kaV0GmbrOB/cGM7xlz3LwSw6AGeVe1HAhXWpd4CrLAobgDIZC1qAf6IWQkCme0o+AHVEn4NrTYIX+A=
Content-Language: en-gb
X-Originating-IP: 82.69.109.75
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding; s= 20221128; bh=tZLj+KdwOF/BR896Hr2x0qtLgDLU1rpCsKWOxKn8NJg=; b=p8F fZXOxVANCLiDuxf3gFtZQjMeqR02VWJFveZpyevMdCJzD2hP7D4y46O/2gujvmix oKrTdWjB/uvh/HSZ3qPmbNqAw31SPADCmMU0US5QQOD6vbyKc/vvx3BsABW/943r u7U9jj2FpYVIegtC0Rp7WOfX55zByBAZXkKhbzaLpDD21jrIWo5UN3FUwW9KK9GB Pcn0aYMEMgmPjwWu2b7edhtY9pQsFscyw4cJQT4RX7HmcGgewvXwVsEuA9zamU0W lYtmJTahAhIHqRGX8nUs3WTo/ZKziRMwyE/Z9gd2g5ct3De2R3ql7KIbR0ZApQ1K KX6UqYkQJMfru1UhUbQ==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-27904.001
X-TM-AS-Result: No--3.887-10.0-31-10
X-imss-scan-details: No--3.887-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-27904.001
X-TMASE-Result: 10--3.887100-10.000000
X-TMASE-MatchedRID: QW5G6BKkLTrxIbpQ8BhdbP7FEhWgo0y8AajW+EL+laM/gf7afIrQU1xU x6Nc3kkvufYjJzeVm6waoVn+bD9mBba2Vh2jQ2eEIi5n/oIUxv8SNP8jmDInFrDGRtqVMwHzsro aYqmkZ2q10Ftke0gt6xRwgFJGApeDQ9tg+p38ZokLsPjFXByaSkdW1WeJf8+Ca0TOsL14A2n8vi H5LwNzLAcpZ1LthGwi5zyDwiE+qjScCBjhV/UcN51U1lojafr/xMZq+YajS9bX/DmPbicSta6Sh yJ3gvTW6QigdfhQUnFftuJwrFEhTf306Q4zhC4D3QfwsVk0UbtuRXh7bFKB7pMoTskNuvgEyHgl /K2nRcPa0VBQ8NBp14VwFwssYfKmlExlQIQeRG0=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/mGjHck0xNEUcEDrVXPHI2uhE5-w>
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:36:16 -0000

Yes, those are good points, Joel. The IESG structures the work of the IETF and self-organises to manage it. They tell the NomCom what they think they need to make that possible.

And peculiarly, the NomCom could decide to appoint only people with a narrow technical ability (say, Dog Catching) to the IESG such that the IESG has to work out how to self-organise to shepherd the Areas.

Adrian

-----Original Message-----
From: ietf-nomcom <ietf-nomcom-bounces@ietf.org> On Behalf Of Joel Halpern
Sent: 28 September 2023 19:19
To: Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org>; Michael StJohns <msj@nthpermutation.com>; ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] NomCom 2023 Extension of Nomination Period to 2023-10-12

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

_______________________________________________
ietf-nomcom mailing list
ietf-nomcom@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-nomcom