[babel] Fwd: Nomcom 2020-2021 Call For Volunteers

Donald Eastlake <d3e3e3@gmail.com> Mon, 01 June 2020 17:23 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E0E33A12ED for <babel@ietfa.amsl.com>; Mon, 1 Jun 2020 10:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 tyyPqWBUVdda for <babel@ietfa.amsl.com>; Mon, 1 Jun 2020 10:23:28 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 8525B3A12EB for <babel@ietf.org>; Mon, 1 Jun 2020 10:23:28 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id q8so7736855iow.7 for <babel@ietf.org>; Mon, 01 Jun 2020 10:23:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=fth7IMH6Bq0FzWGJ5fh5jC0z6lBgZ3Jh+0N2bzLvteQ=; b=VN5XKIPo/5Lzg2GQxrxyMKbGXKqznUFXUq4ZMGlJxrNidGqi7cW8s6tYSESdcP+qjC euSNRz/nwFMCb0fCtebZibWyXezWgEUR+t39k0kDFpq8r3JS6JvxPq8i1+Bhk4nmHxGs lR0dRxli8QqvG8fc+6BMZ1F4wPee0pHqgnpCue1aTIFOI9NYIY1RPcj/tQib3mUtMvTk kDpQJJzBXVp2rJUQyNKE56S1qpl1i87HRsrQgmjYmsC24MmxL9xwJtGjdOJMJMNDqbjm paEiXrfcKRLgXXUqprrYnLw01t3ilWYsUDT/vdzYKVq3yplZosCYAmI4hxi15yyzsFYZ 2+mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=fth7IMH6Bq0FzWGJ5fh5jC0z6lBgZ3Jh+0N2bzLvteQ=; b=pctxd/1QRPUuvhVhgk4S1Nu1M/ovPCZl0dWnFQuQXDIDHfASw3BKyoHCrukUJzw339 yBYqoCnJvgEfe9m6S2j7DBrL4RiS4oASwPGJeyD4KPtRuH0dH7+DAR7PcsmS+bgvZsFv OMzbO2KAwSuqxcyA+ESCeHHIU+jlgn7E1OvANsDhGmpX4DadUB4//hNT8CmyRXM7LC0R nsPbt7UUhxZgloTpryJg+t/Pk993F9gjSjkljjS9/9VXHe+dhN9i4quWOc0YaVX8zGIv fwUKQZWszBbgu77rizUZenxvduAqmniwa4yK9Rd558vxYeSPcVDnt1IYOztqVJX3Xdxq VlMA==
X-Gm-Message-State: AOAM530qGFK5AUswVoVUuiZunEuAhHuXNLPgkuLCpxT/hdPMdy70PTus qIGXev+Feccws74TmXVbL7GDlMl4ORKxAnUPX97Lzaun
X-Google-Smtp-Source: ABdhPJzlSZ3g/QNYjUkAV3/F3JCurTBn4h8CmfN1WCUbGxhfKwR9UvYWNJsVXtkcmq0v/FIhZaj+41Y3cc8o64Gj9GA=
X-Received: by 2002:a02:14c8:: with SMTP id 191mr8597936jag.39.1591032207344; Mon, 01 Jun 2020 10:23:27 -0700 (PDT)
MIME-Version: 1.0
References: <159060174027.19786.17250259010206020465@ietfa.amsl.com>
In-Reply-To: <159060174027.19786.17250259010206020465@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 01 Jun 2020 13:23:16 -0400
Message-ID: <CAF4+nEHAz-6fzLVKyvX6dii0e6sZrxWErr81q_8FYuMkhwaGFQ@mail.gmail.com>
To: Babel at IETF <babel@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/IIKYUJnk_RCyGJ17XlKfZRE8Iz4>
Subject: [babel] Fwd: Nomcom 2020-2021 Call For Volunteers
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2020 17:23:30 -0000

---------- Forwarded message ---------
From: NomCom Chair 2020 <nomcom-chair-2020@ietf.org>
Date: Wed, May 27, 2020 at 4:37 PM
Subject: Nomcom 2020-2021 Call For Volunteers
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: <ietf@ietf.org>


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://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:

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://datatracker.ietf.org/nomcom/2019/

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

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce