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

Michael StJohns <msj@nthpermutation.com> Thu, 28 September 2023 18:55 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 39B91C1522A4 for <ietf-nomcom@ietfa.amsl.com>; Thu, 28 Sep 2023 11:55:11 -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_DNSWL_NONE=-0.0001, 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 nfXWWAatGVgp for <ietf-nomcom@ietfa.amsl.com>; Thu, 28 Sep 2023 11:55:10 -0700 (PDT)
Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (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 AEDAAC151980 for <ietf-nomcom@ietf.org>; Thu, 28 Sep 2023 11:55:10 -0700 (PDT)
Received: by mail-qv1-xf2a.google.com with SMTP id 6a1803df08f44-65b2463d663so34218976d6.0 for <ietf-nomcom@ietf.org>; Thu, 28 Sep 2023 11:55:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20230601.gappssmtp.com; s=20230601; t=1695927310; x=1696532110; 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=/0TfwYzH7fHOn1vgtOYB5SyY0WOMVtw8LuR5cHcMzxM=; b=l/rmyXPEqLh80lJsvPCXi6R7g3CX1FincZFZhz3Ghyl23CVuPkN8YKgNN4ctnuftdl Ot1oLBkXWr7Rjer8zocOOE+NKNtFGSJEtUjv8LwmoqA0hhD+fXgEmXPCJIBWgJrKb4RK c1spoeU392hPZmXuHiAcQ7S4sEZ7uTsOqHJmQmY9ro91aPGP00U7sVamA2WHbEsdfRL2 0B5kLU1No3E1pt0QtnxG3iN70cdZuYdE8UcpqH6skiqZNw3/HDy0A++caBZ9Hy25uIp4 YYq40UNYtaiabvpVKili/b6gX8oC7lMGjKINBd/fpjTY+ampsrmRbfHfHDsgjBKCJoHB w3rQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695927310; x=1696532110; 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=/0TfwYzH7fHOn1vgtOYB5SyY0WOMVtw8LuR5cHcMzxM=; b=bw9K8ohJ2jUQtwO5oIa377RmrAqWz1l5/DOy5qtYktQBWSolDvDyjlhS8zsafL9xq6 N5tuVYrPbWyy845jGdZSzNSu+4qftegEbIyxjeel30YPhBMfUzPw/eWbQ3FRAuSxKsLj KPb5I9KMO1SZoZBlXXyktMaAw95ANnNX9KTSpWXpTQgpHtntQ1GlyE3etqbNXSz+uevy qIsLlmCm8P7DX+rly8UeKO1ymDgw4T3DlZgE/vArELP5mtIIqIVsBTu/2+T7SIls6EvJ 20k+g49a92cvjAFYy5okwGyBWdvRciP8T6s5OeaTzRGNrNzBrheAYgPuybfMFCxow11l 70/Q==
X-Gm-Message-State: AOJu0YxytSPZGmPap3nmg9+yt+ViOfPHIxzd95gD5Fyeyxqt0bFfZqDJ il7+ZvNZiUdijl52t3EHGNFIbEGFb4T2J/05z3c=
X-Google-Smtp-Source: AGHT+IGodSowDsAobG92gO7JgiJ+ynLCIcGXRzh60HpaEpHlYlL8zdL9AV4NFl1JfJGrR8gUwVgjmA==
X-Received: by 2002:a05:6214:509d:b0:659:abd1:8d37 with SMTP id kk29-20020a056214509d00b00659abd18d37mr2033110qvb.4.1695927309708; Thu, 28 Sep 2023 11:55:09 -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 e5-20020a0cb445000000b0063d5d173a51sm4474141qvf.50.2023.09.28.11.55.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Sep 2023 11:55:09 -0700 (PDT)
Message-ID: <19e1c9e7-2d60-5a7a-ab50-546841f510c7@nthpermutation.com>
Date: Thu, 28 Sep 2023 14:55:08 -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: Joel Halpern <jmh@joelhalpern.com>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "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> <9c688aec-d923-b5d8-ba79-991fa6e491e2@joelhalpern.com>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <9c688aec-d923-b5d8-ba79-991fa6e491e2@joelhalpern.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/Eea8hCcJoZi-Yf8yhfR1-5qm1Yg>
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:55:11 -0000

On 9/28/2023 2:19 PM, Joel Halpern wrote:
> 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. 

I agree in the entirety with the above statement.  Sorry if that was 
unclear.  I'm not arguing about the reorg, just about what constitutes 
an open position for the purpose of the Nomcom.  [[In the Nomcom I 
chaired way back when prior to the current series of documents, the 
Nomcom did ask specifically if it should add a second Sec AD, and 
whether or not it was time to close the User Services area.  We added 
the sec ad, and kept the User Services area for another 4 years AIRC.  
Those were discussions, not Nomcom decisions and reasonable given how 
early in the process post kobe we were]]

However, the RedAdAb argument stands.  I don't ever think we'd get 
there, but I'd expect the Nomcom to balk if we did.

Later, Mike