[Acme] FW: Nomcom 2020-2021 Second Call For Volunteers

"Salz, Rich" <rsalz@akamai.com> Wed, 10 June 2020 23:30 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E543C3A15B0; Wed, 10 Jun 2020 16:30:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Ozis2UGbc_H9; Wed, 10 Jun 2020 16:30:56 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 B60613A15B2; Wed, 10 Jun 2020 16:30:56 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net []) by m0050095.ppops.net-00190b01. ( with SMTP id 05AN7gru011714; Thu, 11 Jun 2020 00:30:56 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=Dn1QmbKpYM1JH2qWlXuZdFnLcszecSBEsjMZiSdtsjU=; b=jemN+fOOpbc/Fvx7of2QLxCPWaQ4p9tVdmFOy3edbju/nRof8sNFsNciWVa1Sc7fNwnw ZEDRM9uXykkevwSRdOE2x9mdiBZuvw24wS7+i9LXZK8lWtudHGNS0AvuyGon5qbwnEaT CtMspdhRRXzhqe3Jvk6gJXZ8HgFKNx9B+qDveD6sauah2/VKifK1tnShuYl8Tquk5oY7 YKi+Jsk+OaawbpIKV8AEchg+e1hKSHsVRRNm7dNyUzfEswb4p9dZ7GidR34sB8yE2i7I OLqidLVpxIm97ZEc3D/bRrKSgDNOY/h6NGfZYv0LQ/e/+TDKI4DCXhJCbL7x/LbRj/4/ Rw==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 31g2peg2pb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 Jun 2020 00:30:56 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com []) by prod-mail-ppoint1.akamai.com ( with SMTP id 05AN4aRh017553; Wed, 10 Jun 2020 19:30:54 -0400
Received: from email.msg.corp.akamai.com ([]) by prod-mail-ppoint1.akamai.com with ESMTP id 31g6fxwgq5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 10 Jun 2020 19:30:54 -0400
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ( by ustx2ex-dag1mb6.msg.corp.akamai.com ( with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 10 Jun 2020 16:30:53 -0700
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([]) with mapi id 15.00.1497.006; Wed, 10 Jun 2020 18:30:53 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: "acme@ietf.org" <acme@ietf.org>, "curdle@ietf.org" <curdle@ietf.org>
Thread-Topic: Nomcom 2020-2021 Second Call For Volunteers
Thread-Index: AQHWP1i5AYhYkoE02E+E13ausY3O/ajSt38A///Y7wA=
Date: Wed, 10 Jun 2020 23:30:52 +0000
Message-ID: <7CB3720A-1B6C-4DB2-9551-B0C803C9A22A@akamai.com>
References: <159181529656.16063.6964178024900109434@ietfa.amsl.com> <90F43A4B-9A1E-480A-B7BF-75A93842C261@att.com>
In-Reply-To: <90F43A4B-9A1E-480A-B7BF-75A93842C261@att.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/16.38.20060702
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_7CB3720A1B6C4DB29551B0C803C9A22Aakamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.687 definitions=2020-06-10_13:2020-06-10, 2020-06-10 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 phishscore=0 mlxlogscore=999 bulkscore=0 malwarescore=0 suspectscore=0 mlxscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000 definitions=main-2006100166
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.687 definitions=2020-06-10_13:2020-06-10, 2020-06-10 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 mlxlogscore=999 priorityscore=1501 cotscore=-2147483648 mlxscore=0 spamscore=0 malwarescore=0 clxscore=1011 lowpriorityscore=0 suspectscore=0 adultscore=0 impostorscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000 definitions=main-2006100166
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/yje6BQorY3Roix-v8sNWkMTHKdo>
Subject: [Acme] FW: Nomcom 2020-2021 Second Call For Volunteers
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2020 23:30:59 -0000

Please consider volunteering, or recommending to others that they do so.

The system we have is broken, but it’s all we have for now.

From: "STARK, BARBARA H" <bs7652@att.com>
Date: Wednesday, June 10, 2020 at 5:51 PM
To: 'WG Chairs' <wgchairs@ietf.org>
Subject: Fwd: Nomcom 2020-2021 Second Call For Volunteers

Hi fellow chairs,
Would you mind sending this announcement on to your WGs and impress on them how important it is? Especially if the WG’s AD is up for selection.

Begin forwarded message:
From: NomCom Chair 2020 <nomcom-chair-2020@ietf.org>
Date: June 10, 2020 at 1:55:21 PM CDT
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Nomcom 2020-2021 Second Call For Volunteers
This is the second sending of the call for volunteers for the 2020-2021 NomCom.

I wanted to mention a few updates from the previous email (sent 2 weeks ago):
- I've fixed the URL at the bottom of the email to point to https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_nomcom_2020_&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=ZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEnsbPBtI&s=NgIu-7Ij0nEdsFcbJOLcl2M56RxyREhLAtcaHLatD34&e=  instead of /2019/. This was a test to see if anyone was paying attention. Apparently, some people were. ;)
- The IETF 108 registration form includes a checkbox that will let you volunteer. You can use this instead of emailing me, when you register for IETF 108.
- I currently have 39 volunteers. Last year had 149. I need more volunteers!
The IETF NomCom appoints people to fill the open slots on the 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.

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 (and only this year), we also have RFC 8788 (one-off update to RFC 8713 / BCP 10) to tell us who is eligible to volunteer:

     Members of the IETF community must have attended at least three of
     the last five in-person IETF meetings in order to volunteer.

     The five meetings are the five most recent in-person meetings that
     ended prior to the date on which the solicitation for NomCom
     volunteers was submitted for distribution to the IETF community.
     Because no IETF 107 in-person meeting was held, for the 2020-2021
     Nominating Committee those five meetings are IETFs
       102 [Montreal, Canada; July 2018],
       103 [Bangkok, Thailand; November 2018],
       104 [Prague, Czech Republic; March 2019],
       105 [Montreal, Canada; July 2019], and
       106 [Singapore; November 2019].

Keep in mind that eligibility is based on in-person attendance at the five listed meetings. You can check your eligibility at: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_registration_nomcom.py&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=ZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEnsbPBtI&s=7_9x9PPoUIajJs2AnUFYg0KnEg8gkD3Jnwf1v079EQo&e= .

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

People commonly volunteer by ticking the box on IETF registration forms. The IETF 106 form did not ask whether people were willing to volunteer. IETF 107 did ask, but all those registrations were canceled. I have asked the Secretariat if it is possible to get the list if volunteers from canceled IETF 107 registrations. If that list is available, I will contact all who are verified as eligible. But given the uncertainty of this process, I would encourage people to volunteer directly (see the bottom of this email for instructions). Thank you for volunteering!

The list of people and posts whose terms end with the March 2021 IETF meeting, and thus the positions for which this NomCom is responsible, are

IETF Trust:
   Joel Halpern

   Maja Andjelkovic

   Jari Arkko
   Jeff Tantsura
   Mark Nottingham
   Stephen Farrell
   Wes Hardaker
   Zhenbin Li

   Alissa Cooper, IETF Chair/GEN AD
   Alvaro Retana, RTG AD
   Barry Leiba, ART AD
   Deborah Brungard, RTG AD
   Éric Vyncke, INT AD
   Magnus Westerlund, TSV AD
   Roman Danyliw, SEC AD
   Warren Kumari, OPS AD

All appointments are for 2 years. The Routing area has 3 ADs and the General area has 1; all other areas have 2 ADs. Thus, all areas (that have more than one AD) have at least one continuing AD.

The primary activity for this NomCom will begin in July 2020 and should be completed in January 2021.  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 candidates.

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 either videoconference or in-person meetings (which may not happen) during 14-20 November (IETF 109 - Bangkok) to conduct interviews. Videoconference 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 20-24 July (exact time and date to be determined after NomCom membership is finalized on July 12), the week prior to IETF 108.  Being at IETF 110 (Prague) is not essential.

Please volunteer by sending me an email before 23:59 UTC June 24, 2020, as follows:

To: nomcom-chair-2020@ietf.org
Subject: NomCom 2020-21 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

  // All email addresses used to register for the past 5 IETF meetings
  // Preferred email address first

   // For confirmation if selected

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:

I will be publishing a more detailed target timetable, as well as details of the randomness seeds to be used for the RFC 3797 selection process, within the next few weeks.

Thank you!

Barbara Stark
bs7652 at att dot com
nomcom-chair-2020 at ietf dot org