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

Martin Thomson <mt@lowentropy.net> Thu, 28 September 2023 02:23 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 22B15C15DD6A for <ietf-nomcom@ietfa.amsl.com>; Wed, 27 Sep 2023 19:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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_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="iWTJozbp"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="mYXVd6Zb"
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 r_LivYOVTD6u for <ietf-nomcom@ietfa.amsl.com>; Wed, 27 Sep 2023 19:23:42 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 80CF9C15DD5E for <ietf-nomcom@ietf.org>; Wed, 27 Sep 2023 19:23:42 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id C28C55C068D for <ietf-nomcom@ietf.org>; Wed, 27 Sep 2023 22:23:41 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute6.internal (MEProxy); Wed, 27 Sep 2023 22:23:41 -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=1695867821; x=1695954221; bh=qz l2j6LK+HxgcQnqGfT1rAjJagQ8GmtD9r5O20Qwo60=; b=iWTJozbpHz3Fxtc4Gg UED8d2eu/I4UjrI3Ff0zYrD8Mc3g/Jev2MXyfTMwnKtr+svAc3VFgFOMbmCpMYrC pq+rmH1krE0zc4fXWgemaW4580jXFetIXOvkUQOW1z9OIuJYALH7XU10L5a8DLUN 9BhiZ1lsA99a+plCnRMEj8WokVBunezHRFNV63ppRfD5XVm8oXgoiS4r6+AWusQz v4rC1OKum6qIOMZmmFVtFFGe52U38HilNALMk3pHx/tyVvcikxLMAKoF+mm1o8tF dhWkO0WARq8dCK3nLNQkM0ToqAvthLL10fNH+ryrbkDxC0OI6aAxmlr0Dgt04bo3 agpQ==
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=1695867821; x=1695954221; bh=qzl2j6LK+Hxgc QnqGfT1rAjJagQ8GmtD9r5O20Qwo60=; b=mYXVd6ZbJk28xq4ETygaep46tktdw ANQcXBPWpsMlDV1w1hYeIpKrrtbmr0ENsEAWuGGAnh7oBJ7p+qmD3wPhkPTC+cCz vBaJWozxqBr6AFG7N8Z+Hym0BoLwS9VmRpiVB1AyJPm7X2jeEHYOKzRBpFWzXxh9 X7mMEDQQfTluFhhX+Chs/WGMAo9pi8afy3xkS41ENPhJxO6v90dPvW13g18yP0CO rgYxz+YUHIPdQHnHLX6tfIlezh3Ub2c0qbbn9ccQi4/vvmXpUixmmFSCZmbRvyBR OGNDMZTz8MFHG2ZMsSSP1Dfl7E8Y3ybr8Bf+KJi0xXh1JCoHWMA9t5yNg==
X-ME-Sender: <xms:reMUZe7LhhWlz73YANyhLQsW0y8BOghdW9GanIgXHmvoK-88zUwB9w> <xme:reMUZX7E-vC0UiJ19uDtfZAa6oKgBwUwV6eFgdGALpPyqt32S2SEwMj5nDQkl6YdL 5YPrsHF3QvjO-rU2qs>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvjedrtdehgdehlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:reMUZdc110YgA2MgLsHK4R6pA3uMRPDXAvmqbxvB8bsn9qR1O7jLbg> <xmx:reMUZbKCGN0f6DD89hcsjIjHbOoJGrq3wkOe_RkIofmRGYOgg9ATvA> <xmx:reMUZSJWNz1mGunLAVPSsZWb__i9cyYyA9dtI1Or85IZGl6jd22W0Q> <xmx:reMUZXWGv1YIZWyHiogYF7yaSdwr22vNEUKJ2MLQ7NPTWYd7ZM-1aw>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 8928E234007E; Wed, 27 Sep 2023 22:23:41 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.9.0-alpha0-958-g1b1b911df8-fm-20230927.002-g1b1b911d
MIME-Version: 1.0
Message-Id: <325534a5-8a69-4b8e-bf69-d1a656db2c19@betaapp.fastmail.com>
In-Reply-To: <b50bb5d9-7f2b-5260-f04f-44561794d68c@comcast.net>
References: <169586436096.57370.9087034672258353524@ietfa.amsl.com> <b50bb5d9-7f2b-5260-f04f-44561794d68c@comcast.net>
Date: Thu, 28 Sep 2023 12:23:22 +1000
From: Martin Thomson <mt@lowentropy.net>
To: ietf-nomcom@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/MbeBW_-D2SxsgeA4ygamSZQ4DW0>
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 02:23:47 -0000

Hi Mike,

On Thu, Sep 28, 2023, at 11:56, Michael StJohns wrote:
> Can you expound a bit on the thinking of how the term of the position 
> is 1 year rather than 3?  Is the IESG declaring the ART position vacant 
> now ?  

My understanding is that the position is not vacant today, but it will become vacant at the March IETF meeting.  So the same logic as applied to Lars' vacancy applies.  With all the same caveats.  As the vacancy is not less than one year (it is one year exactly), the term duration is one year.

> We sort of blinked at this for Lars, 

In terms of process, we're definitely not in territory that is well mapped by RFCs.  But the feedback we got in the previous consultations was that with adequate community consultation (as run by the IESG in this case) it was broadly acceptable.  I concluded that a separate comment period for the NomCom half of this transaction wasn't going to help us.

> *_Generally, moving someone from one AD position to another is handled 
> by the Nomcom, not  by the IESG._*   

Can you point me to where this is documented?  I have consulted RFC 8713 and the word "area" appears only in two places and one of those places is an "Oral Tradition" appendix.  My best interpretation of that is the alternative fungible one you included in your postscript.  Fungible ADs are free to move around, which fits my mental model better: they already do that to some degree for those working groups that are in one area, but are overseen by an AD from a different area.

I will admit that that interpretation requires extrapolating from a very small signal, so I'm relying on the consultation that the IESG ran as far as legitimacy goes.

I'm not old enough to remember the details previous IESG shuffles, so I'll rely on others regarding what happened in those cases, if precedent is your preferred method of judging criterion.

Cheers,
Martin