Re: [ietf-nomcom] NomCom 2023 Mid-Term Vacancy Eligibility Clarifications and Questions

Michael StJohns <mstjohns@comcast.net> Wed, 20 September 2023 01:46 UTC

Return-Path: <mstjohns@comcast.net>
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 DD0ABC1519AD for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 18:46:26 -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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=comcast.net
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 lPKxSSlkW0XM for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 18:46:23 -0700 (PDT)
Received: from resqmta-a1p-077720.sys.comcast.net (resqmta-a1p-077720.sys.comcast.net [96.103.146.54]) (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 ECEC0C151064 for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 18:46:22 -0700 (PDT)
Received: from resomta-a1p-077052.sys.comcast.net ([96.103.145.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resqmta-a1p-077720.sys.comcast.net with ESMTP id ilTIqQoX21fFkimGLqFjWg; Wed, 20 Sep 2023 01:44:21 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1695174261; bh=y3N7Q3AOk9ruJ7x0aQhPXWjpwfM6vZ6fqmvVOWYSGGA=; h=Received:Received:Message-ID:Date:MIME-Version:Subject:To:From: Content-Type:Xfinity-Spam-Result; b=zdwdnbvYuINATbdmpbNGycX4BwPLx7pknNCgiO5ZWIT5N6FSZAYEa9H+qai+0iOre 98l8MyHILMIyKm5uxjmrCvTc4F8sKBscZOK51zjhoolHYr3x6BbeAizza7lWdV41TL WMrWEAXgTDSwAKQhq+ZW+tz6OU3p9mZP+oTF6BlKD/C7RdSSMXTvk05nCRp8p6ea8L Rm660t5JSI9RK6G/kF9BM/8qjZsXFtcIiKdwFuQfa9xPNYyi/dOdSmo79FrtBO4o2K DUizXVnpBgaIGRFsNrUjbZLvphjQ5otflvGVmiEej5hTtFuTqtSvi9mm639qQ3dphL BuwxM0E0HVLOw==
Received: from [192.168.1.23] ([108.31.156.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-a1p-077052.sys.comcast.net with ESMTPSA id imFrqsqy99cm6imFsqxZQG; Wed, 20 Sep 2023 01:43:57 +0000
Message-ID: <7530b225-ffa0-7581-1799-1557c66b4857@comcast.net>
Date: Tue, 19 Sep 2023 21:43:51 -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: IETF-Nomcom@ietf.org
References: <169517281292.65045.5821119946773619226@ietfa.amsl.com>
From: Michael StJohns <mstjohns@comcast.net>
In-Reply-To: <169517281292.65045.5821119946773619226@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/-8oR4r74Oy1EdwdG1ffdUdxC6aU>
Subject: Re: [ietf-nomcom] NomCom 2023 Mid-Term Vacancy Eligibility Clarifications and Questions
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: Wed, 20 Sep 2023 01:46:27 -0000

On 9/19/2023 9:20 PM, NomCom Chair 2023 wrote:
> All,
>
> A question has been raised privately about who might be considered an eligible nominee for the IETF chair position.  Unfortunately, RFC 8713 does not deal with this question well when it comes to a mid-term vacancy. I will offer my own interpretation on each, which is based strictly on a reading of RFC 8713.
>
> My reading is that the current situation does not make a process variation absolutely necessary.  However, if the community would like to propose that the NomCom follow a revised process – perhaps because that will result in more good nominees – the committee exists to serve the best interests of the community. The NomCom will follow the advice of the community.
>
> I cannot say at this point whether these questions are academic or not, but I believe that they are worth clarifying either way.
>
> 1. As both the 2022 NomCom and the 2023 NomCom are still active, which members – if any – are eligible to be considered for a position that is vacated unexpectedly?
>
> The relevant text is in Section 5.11 of RFC 8713:
>
>> NomCom members are not eligible to be considered for filling any open position by the NomCom on which they serve. They become ineligible as soon as the term of the NomCom on which they serve officially begins. They remain ineligible for the duration of that NomCom's term.
>>
>> Although each NomCom's term overlaps with the following NomCom's term, NomCom members are eligible for nomination by the following committee if not otherwise disqualified.
> This seems clear to me.  Only members of the NomCom responsible for filling a position are ineligible.

That's correct - the intent of the section is prohibit folk who have 
already played in the process and have possibly influenced the rules, or 
other members from being eligible - that prevents the perception of 
advantage or favoritism whether real or not.


>
> 2. Are liaisons considered to be members by this definition?
>
> Given the imprecise language in the rest of the document, it is not possible to be completely confident. For instance, Section 4.7, which deals with liaisons specifically, does not use the word “member” at all.
>
> My conclusion that a liaison is a member therefore depends on inference. There are many places in RFC 8713 where the word “member” is used to refer to the NomCom as a whole (3.6, 4.3, 4.17, 5.1, 5.7, 5.8, 5.9, …). I also note that the RFC is typically careful in using “voting member” or similar to distinguish those who are drawn from the community at random.
Yes.   Goes to "did this person have an opportunity to influence the 
process".  Given that liaisons vote on everything non-candidate, and 
that they participate in discussions, they could be seen to have an 
advantage, either through direct influence or from close ties to the 
other members of the committee.
>
> 3. Are advisors considered to be members?
>
> My interpretation is that advisors are not members.
>
> Note that the chair of the previous NomCom is strictly defined as an advisor. Consequently, they are not ineligible by a strict interpretation of the RFC.  However, I would suggest that it would be a very bad idea to consider a previous NomCom chair as being eligible for any position.

I have no idea how you came to this interpretation.  They vote, they 
participate - they are members.

Advisors are considered members as well.  There is no difference between 
an advisor and a liaison in their ability to participate in the Nomcom.  
See previous discussions on this topic re Robert Sparks (who is an 
advisor because of tools, but chooses not to participate).  The main 
difference is their form of appointment - liaisons serve via their 
appointing organization, advisors serve at the invitation of the chair, 
with the consent of the Nomcom.

CF :

> The Chair, liaisons, and advisors do not vote on the selection of 
> candidates. They do vote on all other issues before the committee 
> unless otherwise specified in this document.
The past chair is definitely NOT ELIGIBLE.  Although 4.10 refers to him 
"serv[ing] as an advisor", this does not mean they are an advisor in the 
meaning of 4.9.  In any event, they vote on all non-candidate issues, 
and have the same access to candidate info as any other member.

>
> 4. Can a member resign from the NomCom and therefore become eligible?
>
> Section 5.11 seems pretty clear on this point.  A member becomes ineligible instantaneously at the point that the NomCom members are announced, which is the point at which the NomCom term starts. That ineligibility applies to any position that their NomCom is responsible for, whether or not they continue to serve in that NomCom.

That's correct and was put in the document to prevent a repeat of a 
specific situation where this actually happened.


>
> 5. Is this fair?
>
> No.  Consider Section 4.13, which says:
>
>> The list of open positions is published with the solicitation to facilitate community members choosing between volunteering for an open position and volunteering for the NomCom.
> Clearly, the intent is to ensure that people who might consider a leadership position are given the best opportunity to make themselves eligible. That is not possible for a mid-term vacancy.

It's neither fair nor unfair - it's just what it is.  It would be 
problematic to have the Nomcom select one of its own vs other candidates.

Alternately, re-roll the dice and get a new slate of members.


The rest of this I would consider not an appropriate discussion. We're 
already winking a bit at black letter procedures - suggesting that we 
should try and change them more on the fly. Not a good idea.  But that's 
just my personal opinion.

Later, Mike


>
> 6. Can/should we revise these rules?
>
> I have no opinion on this question, but will abide by the consensus of the community.
>
> If anyone wishes to propose a revision to the process for this cycle, I will ask the IESG to judge consensus regarding any proposal. The NomCom will then follow any agreed process.
>
> If you intend to propose a process amendment, please do so as soon as possible, to minimise any delays.
>
> 7. What considerations might apply to rule changes?
>
> Controlling access to confidential information about the NomCom, their deliberations, and nominees is probably the most difficult component of this process. Members have full access to this information, which might influence their ability to effectively campaign for an open position. Advisors – especially the chair from the preceding year – might also be in a position to access this information.
>
> The way that the datatracker system is built, each NomCom has a single key pair, which controls access to most of the confidential information that is stored.  The public key can be changed, causing new information to be stored against the new key.  If keys change in this way, then people accessing confidential information need to juggle multiple keys.
>
> The NomCom could likely manage if there was strong support for varying the process.
>
> Martin Thomson
> nomcom-chair-2023@ietf.org
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce