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

Martin Thomson <mt@lowentropy.net> Wed, 20 September 2023 02:09 UTC

Return-Path: <mt@lowentropy.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 70103C1522AD for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 19:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_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=lowentropy.net header.b="A7Ja1uFs"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="YTkWBF8S"
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 ZbG91_vJWaFM for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 19:08:56 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 F181CC15108E for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 19:08:55 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id D5CE73200974 for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 22:08:54 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute6.internal (MEProxy); Tue, 19 Sep 2023 22:08:54 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1695175734; x=1695262134; bh=UU6H4Motq1p/d+nKh50ulAqVtvSXlEKerXP YuIcAer0=; b=A7Ja1uFsRwTrZTBbXHSqk9oD+bW9B6KrMyl7G3PdpJskAQobD8p rCaZecza0Vx8z58uFqiypg5+h3RKmJ0HXlcS1NWniuhyhTaNLx8P8lObwTp/dAyZ DiX+JLh8MZ6rJBQEbIemKy4mW9uG6IAGm+4Mc6HUWEv3nZqmEfqIj0woXa4m0/2/ 9/x7mS+w0QOXGlNw9Pse5NWsW48xi011Adr370gAblaOWZr8J/AfNyv/bDIstdky OQBfNdSPCpf1JNpXTCjEpOr6PGek/BxPFvVLYjTUUXJASH44nzvncK0SQy4hTJ7I LMR+qGWiwNJKuZTSGZnIsjCY2uBsAK5BWiQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1695175734; x= 1695262134; bh=UU6H4Motq1p/d+nKh50ulAqVtvSXlEKerXPYuIcAer0=; b=Y TkWBF8SjFNvmpbwkuUD3miwelJvtJ7bjBQNrEJTHwoB0W1hpqMQWgT+xSDDaRfkf pq/wZRNC7xP+fmOvY3DV/fK2FqixeZxMIzCc6u8feT97xvve1XtPdG1vwX6yDYLA p3asKjv/LwtH57MLHEwssNLCFPfA3UBY7qr71VrnxUxA7jBfl//wiGZ1z8Reh+qH zgZ/pnFuOhbjZxN23fpEoE58EPvzyDTtRkzWAnnWLOzkJmRgwC1uCEhF2fOOQIEK u1qHBpRhteRt8VizAGfMT9Pz8w4ZgF3Pd4er9hZh3Mlg7igpxP5ZC9a1AW7LNGaK 9BrJmvqcWkKn97qtMa5vw==
X-ME-Sender: <xms:NlQKZTXWF8abGLpdKZbStvU93gLVU14HvyYLZ9WZopvr_SlohPfhJw> <xme:NlQKZbnua3nNuSQzoE5VPnM7WytpjwlHDzVcupdFBe11QV4dkeQ3AvOf6K86_ORZS giy2kHBTxU-R4JrFZ0>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudekvddgheegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtgfesth hqredtreerjeenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepgfejueduieffledtge elheejvdettdejudduhefggeefgfekgfeuieetgefftddtnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnh gvth
X-ME-Proxy: <xmx:NlQKZfYyWyO-LTVYL4Vz7JRVH8nkfJm57131vRQsjiXVPUHNSvjANA> <xmx:NlQKZeUiSZFrnZEsluJw1VgkhvrGGbnvN01oSUf6ye2okjo-fozssQ> <xmx:NlQKZdld3Y5TYfsayNSAjxOLqfSVf6pog73varMJUH2NI9T6YEWz8A> <xmx:NlQKZZzyFsQv4D88Vh5CTggam8r5qWUqNX9TtNX7q6U6O_kgj6AAcw>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 0CB14234007E; Tue, 19 Sep 2023 22:08:54 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.9.0-alpha0-761-gece9e40c48-fm-20230913.001-gece9e40c
MIME-Version: 1.0
Message-Id: <bbe84e87-5cb8-4010-ac73-9c8f8fe454f9@betaapp.fastmail.com>
In-Reply-To: <7530b225-ffa0-7581-1799-1557c66b4857@comcast.net>
References: <169517281292.65045.5821119946773619226@ietfa.amsl.com> <7530b225-ffa0-7581-1799-1557c66b4857@comcast.net>
Date: Wed, 20 Sep 2023 12:08:33 +1000
From: Martin Thomson <mt@lowentropy.net>
To: ietf-nomcom@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/iIVEMH89PfrtmEY4LKtZcKzFe_o>
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 02:09:00 -0000

Hi Mike,

I will cut this down to the advisor question, but I think that your point of "could this person have disproportionate influence on the outcome" is a good razor to apply here.

On Wed, Sep 20, 2023, at 11:43, Michael StJohns wrote:
>> 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.

Cutting this down to the advisor question, which is probably not relevant (Rich is the only advisor presently involved in this NomCom).

The lack of a clear definition of "member" compounds the issue.

Section 4.9 says:

> An advisor is responsible for such duties as specified by the invitation that resulted in the appointment.

That creates considerable uncertainty for me.

One interpretation says that if the duties do not include voting, then the advisor cannot vote.  That interpretation takes the text you quoted below as allowing advisors to be granted the ability to vote (for procedural matters),but it does not require that they be given a vote once appointed.

The other interpretation gives advisors all the rights ascribed to members.

Personally, I would be unhappy if an advisor was brought in for a small matter, but then insisted on voting on procedural issues and also insisted on exercising a right to engage in deliberations (see Section 5.9).

Either way, I think that it is clearly better to consider advisors to be ineligible in this specific case.  I'm less sure about the general case, especially for advisors who have very strictly constrained roles, but we can debate that when it comes to revising RFC 8713 (i.e., later).

>> 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.

I admit to missing this text.  Thankfully, this question is academic in this case (whether or not Rich is an advisor or not, he has indicated no intention of running for IETF chair).  

Again, this only highlights the need for a more thorough process document.