IETF Logo Mail Archive

Re: Call for nominations for IETF NomCom Chair, 2023-2024

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 13 March 2023 09:05 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EAD4C1522AA; Mon, 13 Mar 2023 02:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.095
X-Spam-Level:
X-Spam-Status: No, score=-6.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01] autolearn=ham autolearn_force=no
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 vvklpZd2wTqj; Mon, 13 Mar 2023 02:05:17 -0700 (PDT)
Received: from relay.sandelman.ca (unknown [176.58.120.209]) (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 4198AC15171E; Mon, 13 Mar 2023 02:05:14 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [91.183.8.37]) by relay.sandelman.ca (Postfix) with ESMTPS id 2CCD91F4DF; Mon, 13 Mar 2023 08:55:09 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id BA1EAA1035; Thu, 9 Mar 2023 05:04:45 -0500 (EST)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id B8821A1032; Thu, 9 Mar 2023 11:04:45 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Jay Daley <exec-director@ietf.org>
cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "sullivan@isoc.org" <sullivan@isoc.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Call for nominations for IETF NomCom Chair, 2023-2024
In-reply-to: <F086AC4D-97BA-42ED-A409-F80A6C207A93@ietf.org>
References: <20230221195923.gjtduvn4okxsp2zv@outlook.office365.com> <0BF8E351-4697-4FB6-B6BA-23CA07E3C86E@akamai.com> <2012277.1678022595@dyas> <5145DC98-DEE8-4C22-B895-0D33ECB4AADE@akamai.com> <F086AC4D-97BA-42ED-A409-F80A6C207A93@ietf.org>
Comments: In-reply-to Jay Daley <exec-director@ietf.org> message dated "Mon, 06 Mar 2023 09:29:31 +0000."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 09 Mar 2023 11:04:45 +0100
Message-ID: <2157588.1678356285@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rFgrRvetj3qH4Ah2jiFgeKaZJ14>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Mar 2023 09:05:19 -0000

Jay Daley <exec-director@ietf.org> wrote:
    >> <rsalz=40akamai.com@dmarc.ietf.org> wrote:
    >>
    >>
    >>> Why would we make it public for a limited time?
    >>
    >> We? :) It was an overwhelming, not unanimous, decision of their year's
    >> NomCom. If the community wants to keep it forever, and if the NomCom
    >> approves doing that, we can discuss later. The tools team will have to
    >> get involved, as right now the Wiki is slated for destruction as soon
    >> as the new NomCom is seated. I am reluctant to keep it around forever,
    >> for fear of ossifying things and because this year wasn't typical.

    > Quick correction - it’s slated for deletion when the new NomCom
    > *completes*, not beforehand.  That way the current NomCom has the
    > previous chair to consult and the previous chair has the wiki from
    > their NomCom to consult.

That's way more sensible.
Good content could then migrate each time to the new nomcom site, and then
apply induction :-)




--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.46.0 | Report a Bug | By Email | System Status