IETF Logo Mail Archive

Re: [ietf-nomcom] NomCom 2023 IETF Chair/GEN AD Term Reset Proposal

Martin Thomson <mt@lowentropy.net> Tue, 19 September 2023 21:18 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 BDDD3C17D667 for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 14:18:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.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_MSPIKE_H3=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="ZPoYRJew"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="Ui0tr/hH"
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 AegMTZA8BxZP for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 14:18:49 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 39433C17CEA6 for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 14:18:49 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 2A94C5C0164 for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 17:18:46 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute6.internal (MEProxy); Tue, 19 Sep 2023 17:18:46 -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=1695158326; x=1695244726; bh=6K iCwVAZaOreBI2SE6N01Qq7V1rofwHHq/Yf53y1gNk=; b=ZPoYRJewob6EaAiCZu TvIsV+SCmnqGn4n4dmvluDSndOqdBm+/2ola0Lwpwi/KzpTcaEE0Un2mZGGkpb6m e+7Q8h6XtpFgEVcxqa6MKpNCXrvVyQZlcx20On3xhDKBPcPsaXUYkijFmAwIKbvm ZN2G1XNp5i99cVAqEd5L5y5nwGfK27oEuYxXUfXNyToGiLh6LZehpacx0ZSV3hJf uycYnOJsD7OackZriWlwPypW/q6l8P5dj86RCWPzXKpnoNkyYeey4JnBYvMu+dS2 Be4IJg7dyky8/TzexYrFfdzXKKpZiO1EUC8Rsl4ad7lppqh3lAsbp/IJamzh3z+4 Jh8Q==
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=1695158326; x=1695244726; bh=6KiCwVAZaOreB I2SE6N01Qq7V1rofwHHq/Yf53y1gNk=; b=Ui0tr/hHDQsDiuZVVKzJ4QiMwNHHW 7LbXpOBZl1KQzVg/QaeQPtxd6hAUjWEJOy6jGAyso+LFW9X4cMBGtg0uK44HQmwI AlyBGmT0XQzD7TX4h/juEOfQUtTuiHnj9twr2i9E7+dd6J/7GeINl+3rGdc6tsAx 3L66JQxngpabi8Z49dWBsgBt/TDl1WtCf1ibAt49XE1icWG8la1DbMaYXOwyL9Rm UwJhHBUNA0T0XwjOhPeTiEHWPJdpuOnitvJLuEOufLe9W+r0LCB5arDnJtEVA0vd vE3MMj74duPVSwG6w1WdIsKy7eue+HpVT0Y4aFhtDErZokr7UAjJ7Nx5w==
X-ME-Sender: <xms:NRAKZZfc2tp146HwEL6_b3Y8uTfTjlBsI5qq5Xbsj2vJP7DwEuLLxw> <xme:NRAKZXOyiWYnz2am-0E1lnwBCsq91GuozfMz9gQsQNNPD6ao2QnRQyMAQUKwQFySj BJic1xMlSy2ig0IXpo>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudekuddguddvlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfe ekvefhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnh gvth
X-ME-Proxy: <xmx:NRAKZSilWJLBTFxlbFJM8r1UufQCfo8IaBYq2jf_uDnyLb-TAmSAUQ> <xmx:NRAKZS-u4ykiT5kIh24853wZg-LgSwW_MWQKYD3Osoz1g5yt6tVRSA> <xmx:NRAKZVsoB_aa7xEO2qVJn1d1NMzg1fMQ4b2Vk-rIQa9XCAaQU1uc7A> <xmx:NhAKZT6jW1xxTAkNxVactewrWzpjRZu9o39PRz1PJ0wgVkCBF9uuzQ>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id C1E55234007E; Tue, 19 Sep 2023 17:18:45 -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: <3695da8c-4b67-4ecd-83aa-46f41314811f@betaapp.fastmail.com>
In-Reply-To: <d0ed47c1-f6ee-e7f3-4a51-718213703a16@nthpermutation.com>
References: <169510712484.33106.6003546482401163584@ietfa.amsl.com> <d0ed47c1-f6ee-e7f3-4a51-718213703a16@nthpermutation.com>
Date: Wed, 20 Sep 2023 07:18:24 +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/Dre40MJlBDB7NPA_Sm8WFFq5ygU>
Subject: Re: [ietf-nomcom] NomCom 2023 IETF Chair/GEN AD Term Reset Proposal
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 21:18:54 -0000

On Wed, Sep 20, 2023, at 03:14, Michael StJohns wrote:
> These sections somewhat interact, and somewhat conflict with section 3.5 
> so I think any of 1+, 2, or 3 years would work.

Thanks for the deeper analysis Mike.  I think we are in the process of exploring the limitations of RFC 8713 here, but I think that this is not so complex.  The NomCom has been asked to fill the position and the IESG has expressed a preference (but preference only) for 2 years.  If that is acceptable, using whatever criteria you like, that is enough for me.

(I'm detecting an underlying desire to do some major surgery to RFC 8713, but that's a longer term initiative.)

v2.23.0 | Report a Bug | By Email