Re: [ietf-nomcom] NomCom 2023 Process Details for Mid-Term Vacancies

Martin Thomson <mt@lowentropy.net> Tue, 19 September 2023 07:58 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 1D4F7C1522AA for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 00:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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="OM1Hq41U"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="dmFcoYvj"
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 P_djXTWIPqe0 for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 00:58:12 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94EE2C1519B9 for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 00:58:06 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 06C055C01F5; Tue, 19 Sep 2023 03:58:06 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute6.internal (MEProxy); Tue, 19 Sep 2023 03:58:06 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=cc: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=1695110286; x=1695196686; bh=XY BpVQHxNI4RiYTfP0lK3iOSWm+WV8k7Vat2bh3BRPw=; b=OM1Hq41UPUpUkq3aze cB3l6emGPjvhG5rNU8lFHLI3YAvU2yQzZGaYaZvzoYxsj4PvaNHdJqqJJDle1uoV D+CeOlQHtuRdA39un+N7K3xioAsTom7qu6tBlzMQw87eGYgaULBc3ndGr9HdvWRL f0lf4CeSy069dh5CwHu7NAnqPmDG1q1WmpldM9V2UYhl9OBzSMGwidqxjMZuEhR1 9XqA0u6eTJRg1K6TK8wGhLpDXRPjNGzEWChfNSy0wfJpbrQAnar0IRrnfFrnJddN sQDB1QEJkccsXwY71th9bAU4EaaFWCmThRzdDw1lUu5pC4LBGpf1PEZWMUVh0dnI 4h0g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=1695110286; x=1695196686; bh=XYBpVQHxNI4Ri YTfP0lK3iOSWm+WV8k7Vat2bh3BRPw=; b=dmFcoYvjwWddOCLz8gVuCWwW+pnYa PVJD7uj6XwWwZRxeYF7vavIyJ6zjU717UMxebGPoh2Sr5wexn38NUMNXOYJ47bKI vR3lhOWqceSFGnPArtLuMJtTs9p0sHiHuOyylV6TrmfqzyyLfE/IX6gndkX/8cyB 72wsTo/qISOz6GxiTYFtgywRx6eDTX/e6wX3OrgeCvKuCJ3BwwaVA4kIl4PyGN20 BUFBgMhmWgykq9wJ3bROu+wRdzAFOFks2Eem4zolQH37g9FdKh27mvropaFoPjvP 3b9q+khAzbT8nrV+iGKizNNdLTp4zEjpD08iVGn6vkTA68wvvJSgNR0fg==
X-ME-Sender: <xms:jVQJZf_NALkYs6kZHpfqmktFuixDbFW-MZrerNFg6ONKq-acRHzScg> <xme:jVQJZbvrdM_sRORT83aPATAZwrV1esxJmI2Afzv3quACjmnEmAY1xpAFohcEFqPsn Z-K-KO0Q5lzppBkQQs>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudejledguddvjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfofgr rhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenuc ggtffrrghtthgvrhhnpeekteeuieektdekleefkeevhfekffevvdevgfekgfeluefgvdej jeegffeigedtjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehmtheslhhofigvnhhtrhhophihrdhnvght
X-ME-Proxy: <xmx:jVQJZdC4VtKyQ74CkyxDsTLc0rt8xyWyOhuENgoMvfJwcumANVxSCA> <xmx:jVQJZbf8mn0sejzc1OqUaF1TO0ae4nHfQz6rguIlNyotzpMv8UgTzg> <xmx:jVQJZUPIAaGSLq2rf4KwHt_95XNEH9YbdlkvRiOo6DRQ16IEBfEKhg> <xmx:jlQJZfa6RgPYN58Il6PIcsqLx9uh7Ac0_npilpZcaUgAdEv4uKnhzw>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id C5642234007E; Tue, 19 Sep 2023 03:58:05 -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: <392fb33d-fa6a-4462-a096-d97ac9348988@betaapp.fastmail.com>
In-Reply-To: <ae9570de-e000-dca3-15d1-d456ceba76f2@cs.tcd.ie>
References: <169510744912.45567.17200302232047307359@ietfa.amsl.com> <ae9570de-e000-dca3-15d1-d456ceba76f2@cs.tcd.ie>
Date: Tue, 19 Sep 2023 17:57:45 +1000
From: Martin Thomson <mt@lowentropy.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, ietf-nomcom@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/EYzoS8a75HcaLWhJ0oIvq2yovsY>
Subject: Re: [ietf-nomcom] NomCom 2023 Process Details for Mid-Term Vacancies
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: Tue, 19 Sep 2023 07:58:17 -0000

On Tue, Sep 19, 2023, at 17:48, Stephen Farrell wrote:
> First, what a bummer! I think Lars has been doing a great job

I agree!

> - I think it'd be good if you said where to send comments, so
> that nomcom, the iesg and enough of the community get to see
> those. I assume that ietf@ietf.org is the appropriate place
> for that discussion, given the position. (The same point
> arises wrt your other mail on the term reset.)

The other emails point to the ietf-nomcom@ list (this one only used reply-to).  The IESG are watching.

I'm sure that this will hit ietf@ in some form, but I'd like to keep the discussion on ietf-nomcom@.

> - You don't quite say it below, but I think it makes total
> sense for nomcom to try confirm the IETF chair before other
> IESG positions, if that's feasible. (Given one would normally
> expect some sitting AD to be willing to serve.) I'm not clear
> if you think that may be feasible for this appointment
> though. (Clarifying that may help people provide feedback on
> the chair and other IESG positions.)

My plan was to send the IETF chair selection to the IAB as part of the IESG slate.

If indeed a sitting AD is selected, then we will have to deal with the vacancy, likely in a short period, possibly using this revised process again.  That's not optimal, but I don't see an alternative.  I can't see any way to get a confirmation for the IETF chair early enough for us to be able to do anything much else.