Fwd: [Teas] Fwd: Nomcom 2020-2021 Final Call For Volunteers
Jeff Tantsura <jefftant.ietf@gmail.com> Fri, 19 June 2020 21:31 UTC
Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2191A3A0EA1 for <rtgwg@ietfa.amsl.com>; Fri, 19 Jun 2020 14:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, 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=gmail.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 0hCAmfgSU_F2 for <rtgwg@ietfa.amsl.com>; Fri, 19 Jun 2020 14:31:25 -0700 (PDT)
Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED96A3A0EA0 for <rtgwg@ietf.org>; Fri, 19 Jun 2020 14:31:24 -0700 (PDT)
Received: by mail-pj1-x102c.google.com with SMTP id s88so4831510pjb.5 for <rtgwg@ietf.org>; Fri, 19 Jun 2020 14:31:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=o6XBN2fShPuO3AJoQd7FLz+8wXlcfXS7SBFFVpX6zfY=; b=WVHvDOggrZwZsEuiIfB11GZrO3l4qxmTW39bGCssI5OOP1WBFVzm2zhMdRrRyWJwBi ovBoD/gsaiT/Rei2iko0NyGyJ6C91dGKKbzKR8RX+mt8oba7O0q3b1dEYaj0Bj6r19J2 VQKylLvXr6AcAT9bj2BYeF9Guus1kdXasglFLd4Y67+/fdwgUHjb8V0xLapyEySUV/JG kBbFCZo62LdlB/NArqKqrgjfexIkFh/9+rtV8cQqLhk5YCbwXObJtKqPT5vo1gtfC4qN Ro7+r82yCM7R7BxtDDyPU6zkUvrEN/zcwQBJBOFOlzdzJcGL6CTbpOCOutSDTqzNTCo3 Awjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=o6XBN2fShPuO3AJoQd7FLz+8wXlcfXS7SBFFVpX6zfY=; b=JvNpifeofvny1OLjbxaefMa8KDtvw06Fv2hEngPbWbW07h/enqORgxqtnuCkurKUxk QNf5x1qr7IOkOjBiucf9DyF1DLoUx/eWPTtTs4ZD7QSoFGzvlJF3443MZfl14KqhnMb7 TFI4V/B/QETmwTnHIqVla+x/briqIx9JTMEknMdsCcVPXmsUyMfO8flKfTg3rC0mJFQP WKvU/1vgwdG98r6wxRGknECWTp/h+Ogvpv+1scFSnhxqb4AIbwdu8Gat4wmkqHIdUExE wjS1vVz/Z/X7AYa2VPUnNkTTGy2RAyWQmeHDRNynHgSl0UUVqhhH0YcY/aJRTAz82jOP YtLA==
X-Gm-Message-State: AOAM533IGS9K/CpZDpGiwIShgxeq2K7Z6pstDfmOHE7mL53nbd03ltn1 8y2v/MDoIgkBlpiDaEP+kGhMYVmKafw=
X-Google-Smtp-Source: ABdhPJwiYRktGU7l7wDYFR+jKS/75/ag4Z232JIsbUN12G8QAiHOErHwpRikWPREpjmIfX/8tbUReg==
X-Received: by 2002:a17:90a:4d87:: with SMTP id m7mr5088443pjh.26.1592602284144; Fri, 19 Jun 2020 14:31:24 -0700 (PDT)
Received: from [192.168.1.3] (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id q65sm6797763pfc.155.2020.06.19.14.31.23 for <rtgwg@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Jun 2020 14:31:23 -0700 (PDT)
Date: Fri, 19 Jun 2020 14:31:17 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: RTGWG <rtgwg@ietf.org>
Message-ID: <e2963273-a357-40ff-92a9-ccd5a8bc64c8@Spark>
In-Reply-To: <172c9f45af0.277b.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
References: <159251992201.11993.15942540018989542642@ietfa.amsl.com> <172c9f45af0.277b.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
Subject: Fwd: [Teas] Fwd: Nomcom 2020-2021 Final Call For Volunteers
X-Readdle-Message-ID: e2963273-a357-40ff-92a9-ccd5a8bc64c8@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5eed2eaa_1f404301_178"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/4JkrdZxTXy_FPTDgT7P_iFHbPJw>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jun 2020 21:31:27 -0000
FYI Cheers, Jeff ---------- Forwarded message ---------- Date: Jun 18, 2020, 6:41 AM -0700 To: NomCom Chair <nomcom-chair-2020@ietf.org> > > 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: > www.ietf.org/registration/nomcom.py. > > 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:
- Fwd: [Teas] Fwd: Nomcom 2020-2021 Final Call For … Jeff Tantsura