[spring] Fwd: Second (of three) NomCom 2021-2022 Call for Volunteers

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 09 June 2021 06:00 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D60D23A1009; Tue, 8 Jun 2021 23:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Status: No, score=-2.798 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id a3Po8T2E02e9; Tue, 8 Jun 2021 23:00:11 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 998973A1004; Tue, 8 Jun 2021 23:00:10 -0700 (PDT)
Received: from localhost (localhost []) by mailb2.tigertech.net (Postfix) with ESMTP id 4G0Gff1x6nz1nsm9; Tue, 8 Jun 2021 23:00:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1623218410; bh=8WvXmhLFyyoho4KgbMq9Ihd9lDUnWFkdwH0/1XmxazA=; h=Subject:References:To:From:Date:In-Reply-To:From; b=mhDb300QhJ0vu4xoYBaKLl7MBKb8xFuyKRSLWU83fpB2WseC0XJud+qHgy/vx8i9n /URlqYPsY+ZjYwjFxS8CndLeTZAiUOGtBcYdo+5Z2i7qnX6L/ZikHsU21AQcfk/D+M V0MO9qrvCM3vL15HJHLPSW3frsl0nfvIoHr6j/wg=
X-Quarantine-ID: <x7zWTrr4Gyk9>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [] (50-233-136-230-static.hfc.comcastbusiness.net []) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4G0Gfd3qYkz1nsWP; Tue, 8 Jun 2021 23:00:09 -0700 (PDT)
References: <162321006980.2778.11448893938626362170@ietfa.amsl.com>
To: "lisp@ietf.org" <lisp@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, "spring@ietf.org" <spring@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Forwarded-Message-Id: <162321006980.2778.11448893938626362170@ietfa.amsl.com>
Message-ID: <0db733f3-abf1-ee8f-ba7b-8de96bf94321@joelhalpern.com>
Date: Wed, 09 Jun 2021 02:00:08 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <162321006980.2778.11448893938626362170@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/ATT5oIHN4tsrox1R0ZhqhT0I1wk>
Subject: [spring] Fwd: Second (of three) NomCom 2021-2022 Call for Volunteers
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2021 06:00:17 -0000

Please consider volunteering for the IETF nomcom.  The community needs 
your participation.

Thank you,

-------- Forwarded Message --------
Subject: Second (of three) NomCom 2021-2022 Call for Volunteers
Date: Tue, 08 Jun 2021 20:41:10 -0700
From: NomCom Chair 2021 <nomcom-chair-2021@ietf.org>
Reply-To: ietf@ietf.org
To: IETF Announcement List <ietf-announce@ietf.org>
CC: ietf@ietf.org

This is the second (of three) call for volunteers for the 2021-2022 NomCom.
I wanted to mention a few updates from the previous email (sent 2 weeks 

  - Unlike previous IETFs (e.g., IETF 108 a year ago) for IETF 111 the 
registration form
    does not (yet) include a checkbox that will let you volunteer 
(instead of emailing me).

  - However, the email can be a very short 3 line message (see below).
  - Thanks to everyone who has volunteered so far. However, we currently 
only have    56 volunteers. We need many more. So, please, please volunteer.


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

The details of the operation of the NomCom can be found in BCP 10 (RFC
8713). RFC 3797 details the selection algorithm.

Special for this year RFC 8989 (one-off update to RFC 8713 / BCP 10)
tells us who is eligible to volunteer as anyone who satisfies any of the
three following conditions:

	Path 1: The person has attended 3 out of the last 5 IETF meetings,
	including meetings held entirely online. For the 2021-2022 NomCom, 	the 
meetings concerned will be IETF 106, 107, 108, 109, and 110

	Path 2: The person has been a Working Group Chair or Secretary within
	the 3 years prior to the day the first call for NomCom volunteers is 
sent 	to the community

	Path 3: The person has been a listed author or editor (on the front
	page) of at least two IETF Stream RFCs within the last 5 years prior 
to 	the day the call for NomCom volunteers is sent to the community. 
An 	Internet-Draft that has been approved by the IESG and is in the 
RFC 	Editor queue counts the same as a published RFC, with the relevant 
date being
	the date the draft was added to the RFC Editor queue.
[Normative details are in RFC8989.]

You can check your eligibility at: 
https://datatracker.ietf.org/accounts/profile/ (after logging in, you 
will see your eligibility displayed in the field "Nomcom Eligible").

If you qualify, please volunteer as explained below. However, please
remember that anyone appointed to this NomCom will not be considered as
a candidate for any of the positions that the 2021-2022 NomCom is
responsible for filling.

Details of Positions to Be Filled (some details to be finalized)

An asterisk (*) next to a person's name indicates they do not intend to 
accept renomination.

LLC Board (3-year term)
• Jason Livingood

IETF Trust (3-year term)
• Kathleen Moriarty

IAB (2-year term) • Ben Campbell     • Cullen Jennings
• Mirja Kühlewind
• Jared Mauch
• Tommy Pauly
• Jiankang Yao
IESG (2-year term)
• Murray Kucherawy, ART AD
• Erik Kline, INT AD
• Robert Wilton, OPS AD
• Martin Vigoureux, RTG AD
• Benjamin Kaduk, SEC AD *
• Martin Duke, TSV AD
The primary activity for this NomCom will begin 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 questionnaires, review
feedback from community members about candidates, and talk to

While being a NomCom member does require some time commitment it is also
a very rewarding experience.

As a member of the NomCom it is very important that you be willing and
able to attend meetings either remotely or in-person during IETF 112
(Madrid 6-12 November 2021) to conduct interviews. Remote attendance
will be supported whether or not there are in-person meetings.
Orientation and setting of the NomCom schedule will be done by
videoconference during the week 26-30 July (exact time and date to be
determined after NomCom membership is finalized on July 15), prior to
IETF 111.
Please volunteer by sending me an email before 23:59 UTC on Wednesday
June 23, 2021, as follows:

To: nomcom-chair-2021@ietf.org
Subject: NomCom 2021-22 Volunteer

Please include the following information in the email body:

Your Full Name:
     // as you write it on the IETF registration form

Current Primary Affiliation:
     // Typically what goes in the Company field
     // in the IETF Registration Form

Emails:    // Email addresses used to register for the past 5 IETF meetings
    // Preferred email address first

You should expect an email response from me within 5 business days
stating whether or not you are qualified.  If you don't receive this
response, please re-send your email with the tag "RESEND"" added to the
subject line.

If you are not yet sure if you would like to volunteer, please consider
that NomCom members play a very important role in shaping the leadership
of the IETF.  Questions by email or voice are welcome. Volunteering for
the NomCom is a great way to contribute to the IETF!

You can find a detailed timeline on the NomCom web site at:

Within the next few weeks, I may 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!

Gabriel Montenegro
nomcom-chair-2021 at ietf dot org

IETF-Announce mailing list