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

Michael StJohns <msj@nthpermutation.com> Thu, 28 September 2023 17:54 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 EC039C1524DE for <ietf-nomcom@ietfa.amsl.com>; Thu, 28 Sep 2023 10:54:50 -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 P7NV6DaPz6U2 for <ietf-nomcom@ietfa.amsl.com>; Thu, 28 Sep 2023 10:54:48 -0700 (PDT)
Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (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 E3416C1522AB for <ietf-nomcom@ietf.org>; Thu, 28 Sep 2023 10:54:48 -0700 (PDT)
Received: by mail-qk1-x730.google.com with SMTP id af79cd13be357-7741109bdeeso837509585a.2 for <ietf-nomcom@ietf.org>; Thu, 28 Sep 2023 10:54:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20230601.gappssmtp.com; s=20230601; t=1695923688; x=1696528488; 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=qw2HCEIJmym0UqOHL797AyUCMVAk7ARYW1NitU3VOQA=; b=rwwYW6jJPHzuAu34ZNCVwm+gWbNnJwHEqfirueiKlq44Zj+/P6uYjiilOny4dckzgi aJQVTp358DWJN0r03JjVno0d+BTXcv/dM7dVr93XMPvO51R2v8ISFuM1g2nCGaLaAhCB JWnkwmDPft99HgQF/cH/aHQSa3DTtVNbZOs9OS75oqwIH1b+VZZMmTseSXQC9MzlQ17c gqNnA0pN5u4xYTAAcC5kYkhYcE15Vu/9GP+eMDOjTu7gwQV6lz2S+oDPaaB0+zpibv8d texYvRWh226CsozKnEFi5D8uP6XLflP6dakReVCbN26diSpkgDCqdaYy5vn5hucHNpXT +36Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695923688; x=1696528488; 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=qw2HCEIJmym0UqOHL797AyUCMVAk7ARYW1NitU3VOQA=; b=ehmbCX4oPTnbGwP0vt82j3PKJ/MC2KFIG/KPFl3vGym8hCk8KdVUi3tZfYxTDrU698 xE/rqpjTAp7FwJJJdXrugA9+PnWPEr3x/aot4bILhf9UWq5DKyxidtAh4PjCWzoBsh9G f9aqdt3BlvBStr6tpuME0uiZ7L1p/J5YCKTlIZhnDgtKXFrnhaFXCLg30td/Mb4JDMTZ 5g4KWJ/GGVA701gz/nqXM5w4tUOC5vnvHJuCYWwxzvjdpVI6H1RzAIFXs74utNq2Dtog Dep8/k/tSefNkf/HJv6RpKHK67ZgQqDjW3jJsn7N1WvevztadSlZ/JdQ3hr4pwlJL7aT Likw==
X-Gm-Message-State: AOJu0Yxdxtv+CQRvZyLJBJg6ulDWsAw0Wr5QyOkYF6iP/SOuw1vkm0kR 32Q9kB15nPtRQM01cvqEVULQPQ==
X-Google-Smtp-Source: AGHT+IEWa0YMZouEu02Wyaodh9NTiD373XGeVqDE5sSXbYNA/zcEYfOwWfUS6TWizu18xEMhZ806yg==
X-Received: by 2002:a05:620a:4708:b0:76d:268b:9741 with SMTP id bs8-20020a05620a470800b0076d268b9741mr2250975qkb.17.1695923687707; Thu, 28 Sep 2023 10:54:47 -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 22-20020a05620a079600b0076f0744ff50sm1040473qka.136.2023.09.28.10.54.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Sep 2023 10:54:47 -0700 (PDT)
Message-ID: <deb58221-f245-0404-f3d0-132f16a6c512@nthpermutation.com>
Date: Thu, 28 Sep 2023 13:54:46 -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>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <F77FEBE2-A323-4B3B-9AD1-F5D5E7A189B2@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/goXAFbpvzhxaiKydNRMyOw8zmAg>
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 17:54:51 -0000

On 9/28/2023 1:40 PM, Salz, Rich wrote:
>> In any event, getting back to your first question - let me turn it
> around on you and ask where it's documented that the IESG may as a body
> appoint someone to a new position without going through the Nomcom?
>
> Do you believe that the NomCom has any role in oversight on what the IETF job descriptions are?
>
Yes.  As do the confirming bodies.

A reductio ab adsurdum argument:   The IESG opens up a Dog Catcher area, 
and writes a position description for that area that basically describes 
what you might expect a dog catcher to do. The Nomcom looks at it and 
declines to fill the position because its outside the the scope of the 
IETF, or offers a dog catcher to fill the position.  The confirming body 
(IAB) looks at the candidate, the position description, and rejects the 
candidate. Both are doing their jobs and both are not subject to being 
overridden by the IESG.

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

Another not so absurd argument:   The IESG writes a position description 
with a particular candidate in mind.  If the Nomcom followed the PD to 
the letter and only selected exact matches, it would only select a 
particular candidate.  In this case, the Nomcom should ignore the more 
specific requirements and look at a broader set.

So - yes.  It's a de facto oversight role, but it's there.  The Nomcom 
doesn't get to say what's in the PD, but it's interpretations of the PDs 
are what get the weight.  However, describing why things were done in a 
particular way relative to a PD may be useful for the confirming body's 
benefit.

Later, Mike