[Idr] Fwd: Seeking volunteers for NomCom

Jeffrey Haas <jhaas@pfrc.org> Thu, 23 June 2022 19:24 UTC

Return-Path: <jhaas@pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AAD0C157B49 for <idr@ietfa.amsl.com>; Thu, 23 Jun 2022 12:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] 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 Zn7AiEeYxXZ2 for <idr@ietfa.amsl.com>; Thu, 23 Jun 2022 12:24:03 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 36F7DC157B5D for <idr@ietf.org>; Thu, 23 Jun 2022 12:24:01 -0700 (PDT)
Received: from smtpclient.apple (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id BDAE31E345; Thu, 23 Jun 2022 15:24:00 -0400 (EDT)
From: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_00E98A6F-B006-429A-A246-E2E33210A648"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
Date: Thu, 23 Jun 2022 15:24:02 -0400
References: <165583402594.35436.3058271770862012242@ietfa.amsl.com>
To: "idr@ietf. org" <idr@ietf.org>
Message-Id: <41B6268E-858B-4B79-B693-68B308937C85@pfrc.org>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/OdTdIVAgQoBNDv0DMzRUrKTx4Os>
Subject: [Idr] Fwd: Seeking volunteers for NomCom
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2022 19:24:04 -0000

Serving on nomcom is a rewarding way to learn more about how the IETF as a whole functions while helping the IETF find its leadership for the next term.  Please consider participating!

-- Jeff


> Begin forwarded message:
> 
> From: NomCom Chair 2022 <nomcom-chair-2022@ietf.org>
> Subject: Seeking volunteers for NomCom
> Date: June 21, 2022 at 1:53:46 PM EDT
> To: "IETF Announcement List" <ietf-announce@ietf.org>
> Reply-To: nomcom-chair-2022@ietf.org
> 
> The IETF NomCom appoints people to fill the open slots on the IETF LLC, IETF
> Trust, the IAB, and the IESG.  Ten voting members for the NomCom are selected
> in a verifiably random way from a pool of volunteers. The more volunteers,
> the better chance we have of choosing a random yet representative cross
> section of the IETF population.
> 
> To volunteer click on this link: ttps://datatracker.ietf.org/nomcom/volunteer
> Note that if you are selected for NomCom you are ineligble to be a candidate
> for any position.
> 
> The primary activity for this NomCom will begin in shortly after IETF 114 in
> July 2021 and should be completed by January 2022.  The NomCom will have
> regularly scheduled conference calls to ensure progress. There will be
> activities to collect requirements from the community, review candidate
> responses, review feedback from community members about candidates, and
> talk to candidates.
> 
> The details of the operation of the NomCom can be found in RFC 8713. RFC 3797
> details the selection algorithm. Note that the IESG has already decided to
> repeat the experiment detailed in RFC 8989 for this cycle. That is, in
> addition to the traditional "Path 1" of eligibility (three out of the last
> five meetings), there are two other ways to become eligible:
>        Path 2. WG chair or Secretary within the past three years
>        Path 3. Author of Editor (as listed on the front page) of two
>           IETF stream RFC's within the past five years. An approved
>           draft in the RFC Editor queue counts as an RFC.
> 
> Last year, there were no NomCom members from Path 2 or Path 3.  If you
> qualify under those criteria, please consider volunteering.  The list of
> positions will be announced soon, well before the NomCom is chosen, so you
> can "back out" if you need to.
> 
> You can check your eligibility by logging in and viewing your profile page at
> https://datatracker.ietf.org/accounts/profile/ Note that the code is being
> reviewed, so if you dispute it please let me know.  Again, should you wish
> To volunteer, click on this link: https://datatracker.ietf.org/nomcom/volunteer
> 
> While being a NomCom member does require some time commitment it is also
> immeasurably important to the short-term future of the IETF.  I hope that one
> outcome from this year's NomCom is that future volunteers will have much
> better information about the commitment.  All NomCom meetings and candidate
> interviews will be hybrid (a mix of virtual and remote).
> 
> You can find a detailed timeline on the NomCom web site shortly:
>    https://datatracker.ietf.org/nomcom/2022/
> 
> Within the next week or two, I will add more details on the timeline, as
> well as details of the randomness seeds to be used for the RFC 3797
> selection process.
> 
> Thank you! I will be in-person for IETF 114 (arriving Saturday, leaving early Friday morning) if you want to chat.
> 
> Rich Salz
> nomcom-chair-2022@ietf.org
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce