RE: Nomcom 2020-2021 Final Call For Volunteers

"STARK, BARBARA H" <bs7652@att.com> Fri, 19 June 2020 18:29 UTC

Return-Path: <bs7652@att.com>
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 ABD013A0CF9 for <ietf@ietfa.amsl.com>; Fri, 19 Jun 2020 11:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5onhsLzSQ3xI for <ietf@ietfa.amsl.com>; Fri, 19 Jun 2020 11:29:05 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 07A953A0CD8 for <ietf@ietf.org>; Fri, 19 Jun 2020 11:29:04 -0700 (PDT)
Received: from pps.filterd (m0048589.ppops.net [127.0.0.1]) by m0048589.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 05JIDojf044311 for <ietf@ietf.org>; Fri, 19 Jun 2020 14:29:04 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0048589.ppops.net-00191d01. with ESMTP id 31rk6xn5cp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 19 Jun 2020 14:29:04 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 05JIT35J006483 for <ietf@ietf.org>; Fri, 19 Jun 2020 14:29:03 -0400
Received: from zlp30488.vci.att.com (zlp30488.vci.att.com [135.47.91.93]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 05JISwbw006336 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 19 Jun 2020 14:28:58 -0400
Received: from zlp30488.vci.att.com (zlp30488.vci.att.com [127.0.0.1]) by zlp30488.vci.att.com (Service) with ESMTP id C51254009E82 for <ietf@ietf.org>; Fri, 19 Jun 2020 18:28:58 +0000 (GMT)
Received: from GAALPA1MSGHUBAB.ITServices.sbc.com (unknown [130.8.218.151]) by zlp30488.vci.att.com (Service) with ESMTPS id A67504009E80 for <ietf@ietf.org>; Fri, 19 Jun 2020 18:28:58 +0000 (GMT)
Received: from GAALPA1MSGEX1CA.ITServices.sbc.com (135.50.89.108) by GAALPA1MSGHUBAB.ITServices.sbc.com (130.8.218.151) with Microsoft SMTP Server (TLS) id 14.3.487.0; Fri, 19 Jun 2020 14:28:58 -0400
Received: from GAALPA1MSGEX1CB.ITServices.sbc.com (135.50.89.109) by GAALPA1MSGEX1CA.ITServices.sbc.com (135.50.89.108) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Fri, 19 Jun 2020 14:28:57 -0400
Received: from GAALPA1MSGEX1CB.ITServices.sbc.com ([135.50.89.109]) by GAALPA1MSGEX1CB.ITServices.sbc.com ([135.50.89.109]) with mapi id 15.01.1979.003; Fri, 19 Jun 2020 14:28:57 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Nomcom 2020-2021 Final Call For Volunteers
Thread-Topic: Nomcom 2020-2021 Final Call For Volunteers
Thread-Index: AQHWRcFTx68z0v9a3kW1enzteQJZAqjgLz1Q
Date: Fri, 19 Jun 2020 18:28:57 +0000
Message-ID: <9f02bf698c4a4723b0d5807b469312ba@att.com>
References: <159251992201.11993.15942540018989542642@ietfa.amsl.com>
In-Reply-To: <159251992201.11993.15942540018989542642@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.80.214]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.687 definitions=2020-06-19_20:2020-06-19, 2020-06-19 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 mlxscore=0 adultscore=0 priorityscore=1501 lowpriorityscore=0 phishscore=0 suspectscore=0 spamscore=0 clxscore=1015 bulkscore=0 impostorscore=0 malwarescore=0 mlxlogscore=999 cotscore=-2147483648 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000 definitions=main-2006190134
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H3EuzCZXWYNtSyx4ofnEoxSC8pM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <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: Fri, 19 Jun 2020 18:29:07 -0000

Hi again IETFers,
I've had a couple of people asking me about how this year's NomCom will operate. I'd like to draw your attention to these paragraphs buried at the bottom of my email. The first paragraph is the same as other NomComs, with only the years changed. The second paragraph is very much customized. There will be no "in-person attendance" expectations of any NomCom member. All meetings will be accessible to NomCom members by videoconference. Once the NomCom is seated, the group will figure out what time zones are represented and how best to minimize and equitably share pain. The seated NomCom can choose to discuss whether to move some or all of the 14-20 November week activities to a nearby week; but it seemed best to set expectations up front of at least being available during that week.

Please feel free to ask me questions. Or ask this list. There are many experienced NomCommers here
Barbara

> 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.
> 
> 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.



> -----Original Message-----
> From: ietf <ietf-bounces@ietf.org> On Behalf Of NomCom Chair 2020
> Sent: Thursday, June 18, 2020 6:39 PM
> To: IETF Announcement List <ietf-announce@ietf.org>
> Cc: ietf@ietf.org
> Subject: Nomcom 2020-2021 Final Call For Volunteers
> 
> Hi IETFers,
> We're down to the last week of accepting NomCom volunteers. And I need
> more! Lots more!
> 
> I have 64. I'd really like to get another 100 names. Hopefully, some of you are
> checking the volunteer box on IETF 108 registration. But I don't have anything
> from canceled IETF 107 registration, and the NomCom question wasn't asked
> on IETF 106. So I need a flood of volunteers to come in over the next week.
> Barbara
> =============================================
> 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=a9RCEHQWTIKubL1-
> QQkqVwmhfzdWSJ14zPZ8VsgGq10&s=LzKeB4G8quLYg445Nn7rf7pd2B21ybV
> -dDDwzs80pqo&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
> 
> LLC:
>     Maja Andjelkovic
> 
> IAB:
>     Jari Arkko
>     Jeff Tantsura
>     Mark Nottingham
>     Stephen Farrell
>     Wes Hardaker
>     Zhenbin Li
> 
> IESG:
>     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
> 
> Emails:
>    // All email addresses used to register for the past 5 IETF meetings
>    // Preferred email address first
> 
> Telephone:
>     // 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:
>     https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__datatracker.ietf.org_nomcom_2020_&d=DwIDaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=a9RCEHQWTIKubL1-
> QQkqVwmhfzdWSJ14zPZ8VsgGq10&s=BSsSC9wKBTd1O6rU_gB0vHBiV4EKGo
> gxNMn8UJYAlVg&e=
> 
> 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