Re: [ietf-nomcom] NomCom 2023 Extension of Nomination Period to 2023-10-12
John C Klensin <john-ietf@jck.com> Fri, 29 September 2023 03:19 UTC
Return-Path: <john-ietf@jck.com>
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 373B6C15C509; Thu, 28 Sep 2023 20:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-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 NuyD5tbVRTT0; Thu, 28 Sep 2023 20:19:50 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19550C15C513; Thu, 28 Sep 2023 20:19:49 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1qm42d-000BZX-Tn; Thu, 28 Sep 2023 23:19:47 -0400
Date: Thu, 28 Sep 2023 23:19:41 -0400
From: John C Klensin <john-ietf@jck.com>
To: Martin Thomson <mt@lowentropy.net>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Michael StJohns <msj@nthpermutation.com>, ietf-nomcom@ietf.org
Message-ID: <790259A09017DBF97C3BA1C0@PSB>
In-Reply-To: <09bd05c6-85b5-4943-8479-a9fc23512a65@betaapp.fastmail.com>
References: <169586436096.57370.9087034672258353524@ietfa.amsl.com> <b50bb5d9-7f2b-5260-f04f-44561794d68c@comcast.net> <325534a5-8a69-4b8e-bf69-d1a656db2c19@betaapp.fastmail.com> <ffb9a9bb-5a8d-8d24-1549-6d00b8115aec@nthpermutation.com> <F77FEBE2-A323-4B3B-9AD1-F5D5E7A189B2@akamai.com> <deb58221-f245-0404-f3d0-132f16a6c512@nthpermutation.com> <0024EBA9-5174-4030-B69A-FFA52C602C2E@akamai.com> <8B3524ED5D57C7C43CBF0A5E@PSB> <09bd05c6-85b5-4943-8479-a9fc23512a65@betaapp.fastmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/iMVtm6vHhBB_MzZB8u4KI85hqDk>
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: Fri, 29 Sep 2023 03:19:52 -0000
--On Friday, September 29, 2023 12:23 +1000 Martin Thomson <mt@lowentropy.net> wrote: > On Fri, Sep 29, 2023, at 05:28, John C Klensin wrote: >> While I probably would not have phrased things that way Mike >> did, I think it has been clear since the beginning of the >> Nomcom model that job descriptions provided by the IESG or >> other bodies are advisory to the Nomcom, not rigid >> requirements. > > This indicates to me some level of acceptance with the > proposed course of action. Maybe. Or, if "some level" is stressed, yes, because one thing about which I've seen no disagreements (and you aren't going to get it from me) is that the the IESG has the authority to rearrange Areas and their scope. Viewed very narrowly and in that light, the question is whether the IESG can move Francesca from ART to the new Area or whether it creates the new area with an empty slot for which Francesca (like any other member of the community) can be a candidate. If the Nomcom had the option and chose to move her there --possibly based, not only on her personal skills and interests, but on what the Nomcom concludes it will do to AET, new appointees there, etc. -- then fine... and the Nomcom presumably goes on to fill the then soon-to-be-vacant ART position. If, instead, the Nomcom decides to leaver her in ART, then there is a position in the new Area to fill. > The IESG have indicated, after community consultation, that > they wish to adopt a new organizational structure that they > believe will aid them in accomplishing the task they are > entrusted with (make the IETF function effectively). Yes, and whether I agree with that decision (or some of its details) or not, I am not questioning their right to make that decision. If I seriously dislike the decision, my main option is to give advice to the Nomcom about whether IESG members who were most active in promoting it should be returned -- advice the Nomcom can presumably weight as it deems appropriate. > The NomCom have been given guidance on the sort of > characteristics that people might need in order to help the > IESG do that. We will consider that guidance - along the > input we receive from others in the community - in selecting > an IESG slate to present to the IAB for confirmation. And, again, I think that is just right so we are in agreement. > I am interpreting Mike's concern as being grounded in a desire > to avoid extreme outcomes if this process is left unchecked. > Yes, if we had an IESG comprised solely of dog catching > professionals, the Internet might suffer for it (might). As > established in this thread, these consultations, the > confirmation process, and the NomCom process as a whole would > seem to each act to as a remedy against that sort of extreme > outcome. ok, but I've interpreted Mike's comments and those of a few others, including my own, as not questioning any of the above but only as to whether a decision to move an AD from one role (for which a prior Nomcom evaluated and selected them) to another position. We believe decisions about who occupies which slots after the reorganization are Nomcom decisions and not IESG ones. FWIW, I believe that the reorganization might have been described and announced in a way that would have had this discussion be about Zahed's slot/ position rather than about Francesca's and that would not have changed the argument significantly. The matter would remain that someone would be taking on responsibilities for which they were not selected by a Nomcom and I (at least) see that as problematic. > On that note, I encourage people to please provide feedback to > the NomCom about how you think we should be selecting people > for these positions. And that is precisely the option (and obligation) I am trying to preserve by arguing that the new position created by the new area should be treated as a new/ vacant position and not an IESG-managed move of an AD from one Area to another, a move that, as things are now specified, does not allow candidate-specific input from either the community or the Nomcom. best, john
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Michael StJohns
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Martin Thomson
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Lars Eggert
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Michael StJohns
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Salz, Rich
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Salz, Rich
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Martin Thomson
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Michael StJohns
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Salz, Rich
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Adrian Farrel
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Adrian Farrel
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Michael StJohns
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… John C Klensin
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Michael StJohns
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… John C Klensin
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Salz, Rich
- Re: [ietf-nomcom] NomCom 2023 Extension of Nomina… Joel Halpern