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

Michael StJohns <msj@nthpermutation.com> Thu, 28 September 2023 18:47 UTC

Return-Path: <msj@nthpermutation.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 BB5EAC151091 for <ietf-nomcom@ietfa.amsl.com>; Thu, 28 Sep 2023 11:47:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.091, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20230601.gappssmtp.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 1KGWR152fDaU for <ietf-nomcom@ietfa.amsl.com>; Thu, 28 Sep 2023 11:47:07 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 9010AC151980 for <ietf-nomcom@ietf.org>; Thu, 28 Sep 2023 11:47:07 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id af79cd13be357-774105e8c37so863542385a.3 for <ietf-nomcom@ietf.org>; Thu, 28 Sep 2023 11:47:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20230601.gappssmtp.com; s=20230601; t=1695926826; x=1696531626; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=hsPcHqjPHkz9cMNRvmFBoSAu7BSVrHRivsIsYW9EDeo=; b=oGSmL1K4E6GcflPW6VjBAfT5sCIpeh4LuqfAidApXhxhuuLJYvNFD61rCaEyff7QdP oRMrtD32HuR+bG8kn6fQu77I284uoJTX3+O4zEHL09xP2Y4p2XjBXEbD/Fqd+Jxb3if0 5eh30/HrPx//i/Otj4B3+MkisvTHFFGDHm/c/O6NEWd3fxcihDwJ42oyWuCpI3fpaTXM u4TycgZt65MUaGd6J9MFboKKuMqj6uL1N9Orl9/ZPw9GTKSdfprxYYBxQ9fy6V41Fspi /IyQ8F50+kS4HxWk5hkakP4mGUeTpViurknZ8YFgzpt/1+o/2GXeP1vFYaozflh2iC0u ki3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695926826; x=1696531626; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=hsPcHqjPHkz9cMNRvmFBoSAu7BSVrHRivsIsYW9EDeo=; b=tBmxN2MUY/DTnCBGNWN8pqQFsOg2bzyUu7UQx8qVLgBVvBij9RPqhOT57VPzVNQPl8 mCJv7IKQ9yDJHU0rqtjN3j1GDUfNnFIdW/2ZvnkpOW8NYNBofIcLDiInom7gvTw0AOXA Ia6CV7ZextnscxkziFlboXmGlIRseOKdbFRWZ565tOlSap3UmcsADpvT/xWspj13i7Wk YunyFULp78XGvGl6uc9vDNZ8f1yCrZfiVh5ahAnHcAqo/awNzhHCpAUefgMv403UQJvs C+z4MGICPT9ttdxEjDRIxw1WNDT47gVVpqFLKYQVVGyTb4pCTbusBBfIZ+Dhf0xudiPv up6w==
X-Gm-Message-State: AOJu0Yyn8orARsq8Y3WR+Rpt0s+SDI1YLhflEPNtrq0XeSn4MKzExyA+ 8hTidbAwbssAbKMZtLa/xQIv8l6S/R9QWSyKyss=
X-Google-Smtp-Source: AGHT+IH5xy1l0XJAPnBJP6E77OcT+WrRM/3rNi1oGXgD9mjywHI7Y6OEox6dHCCiVOC7gOAETp4+wg==
X-Received: by 2002:a05:620a:4145:b0:774:e3b:9044 with SMTP id k5-20020a05620a414500b007740e3b9044mr2553311qko.60.1695926826026; Thu, 28 Sep 2023 11:47:06 -0700 (PDT)
Received: from [192.168.1.23] (pool-108-31-156-76.washdc.fios.verizon.net. [108.31.156.76]) by smtp.gmail.com with ESMTPSA id 17-20020a05620a06d100b00767d2870e39sm4372070qky.41.2023.09.28.11.47.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Sep 2023 11:47:05 -0700 (PDT)
Message-ID: <ea73b1bb-6354-d564-bb35-bb32e89a8f14@nthpermutation.com>
Date: Thu, 28 Sep 2023 14:47:04 -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@akamai.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: Michael StJohns <msj@nthpermutation.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/NDY8sBb4so8qERk7-IeMNP4yGc8>
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:47:09 -0000

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.
>
>
Clipping out all of the rest of it isn't helpful here.

As I said - this is de facto, not de jure.   So far, the Nomcoms mostly 
haven't had to deal with "in the rough" PDs - I think.  I may be wrong - 
but since I haven't been on all of the Nomcoms, and since those details 
tend to be confidential, I'll never know.

It's not only what's written in the PD, it's what interpretation the 
Nomcom and its member place on the PD.  Each combo of nomcom members 
will reach a "unique" understanding of the requirements for a given 
position and will use their own judgement to fit round candidates into 
the mostly round hole they interpret.

Nomcom members are people, with biases, life knowledge, intelligence and 
varying levels of cussedness.  They are not automatons running a program 
that gives the same meaning to a PD that every other member gives.  The 
more objective the requirements, the closer you get to common meaning.  
The more general the requirements, the further the spread among the 
understandings of what's required.  Discussion helps to narrow the scope.

Finally, I would expect any Nomcom that receives an "in-the-rough" PD to 
push back through the appropriate Liaison - that's one of the reasons 
they're there.  If that doesn't result in a satisfying conclusion, I 
would expect the Nomcom to do the right thing for the community, not 
just for the body that provided the PD, irrespective of the requirements 
stated in the PD.

So let me ask you - you've been on a few nomcoms, at least one as a 
voting member.  Did you or did you not interpret the PDs you were handed 
in light of your own experience, your experience with the IETF and with 
the discussion within the Nomcom?

Later, Mike