[lisp] Fwd: Fwd: Nomcom 2020-2021 Second Call For Volunteers

Joel Halpern <jmh@joelhalpern.com> Thu, 11 June 2020 00:43 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96DE23A15EC; Wed, 10 Jun 2020 17:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_MSPIKE_H4=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VgRikfedOA43; Wed, 10 Jun 2020 17:43:19 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 B9C793A15EB; Wed, 10 Jun 2020 17:43:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 49j4pb4Kjtz6GGl5; Wed, 10 Jun 2020 17:43:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1591836199; bh=JJFnCJr5cEZFkUsQGF9O3k4mbrGNfZUIpN5k0JplajI=; h=Subject:References:To:From:Date:In-Reply-To:From; b=kk+7mu/0d5X3zZM7Peg8yY5we+KkDZij49FkJt2LLnjkKOivGjok+1PKafGb4PK6U ebjSoVpqgCAvCyKrfCJnZf00a7yr0jPSd5In+C86uffv7hhdzbuco02eegdQ2Dlvho qWjyoRQpPDms7gBhZ2VfXyfqNour15xQ6dlPSiWM=
X-Quarantine-ID: <WzZHPjL--ulH>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 49j4pZ74ZMz6G9lW; Wed, 10 Jun 2020 17:43:17 -0700 (PDT)
References: <90F43A4B-9A1E-480A-B7BF-75A93842C261@att.com>
To: "lisp@ietf.org" <lisp@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
From: Joel Halpern <jmh@joelhalpern.com>
X-Forwarded-Message-Id: <90F43A4B-9A1E-480A-B7BF-75A93842C261@att.com>
Message-ID: <c8fff368-63d9-c7aa-156a-1787d16c3853@joelhalpern.com>
Date: Wed, 10 Jun 2020 20:43:16 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <90F43A4B-9A1E-480A-B7BF-75A93842C261@att.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/lisp/dyJ_duKp9AEPq0_y6rUdiwpg7T4>
Subject: [lisp] Fwd: Fwd: Nomcom 2020-2021 Second Call For Volunteers
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jun 2020 00:43:22 -0000

Barbara, our Nomcom chairs, ha sensibly asked chairs to forward this to 
our working groups.

Please volunteer to serve on Nomcom if you are eligible and can make the 
time.  if you are eligible, please try to make the time.

Thank you,
Joel


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
>
> 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=ZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEnsbPBtI&s=NgIu-7Ij0nEdsFcbJOLcl2M56RxyREhLAtcaHLatD34&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
>