The IETF NomCom appoints folks to fill the open slots on the IAOC, 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 RFC 7437 (BCP 10), and RFC 3797 details the selection algorithm.
Volunteers must have attended 3 of the past 5 IETF meetings. As specified in RFC 7437, that means three out of the five past meetings up to the time this email announcement goes out to start the solicitation of volunteers. The five meetings out of which you must have attended *three* are:
IETF = 94 (Yokohama) \
95 (Buenos Aires) \
96 (Berlin) -*** ANY THREE!
97 (Seoul) /
98 (Chicago) /
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 2017 - 2018 NomCom is responsible for filling.
Some 201 people have already volunteered by ticking the box on the IETF 96 through 98 registration forms. I will contact all of these volunteers shortly. Thank you for volunteering!
The list of people and posts whose terms end with the March 2018 IETF meeting, and thus the positions for which this NomCom is responsible, are
IAOC:
Leslie Daigle
IAB:
Ted Hardie
Joe Hildebrand
Lee Howard
Erik Nordmark
Martin Thomson
Brian Trammell
IESG:
Alia Atlas (RTG)
Benoit Claise (OPS)
Suresh Krishnan (INT)
Mirja Kühlewind (TSV)
Alexey Melnikov (ART)
Kathleen Moriarty (SEC)
Adam Roach (ART)
All appointments are for 2 years. The ART and Routing areas have 3 ADs and the General area has 1; all other areas have 2 ADs. Thus, all areas have at least one continuing AD.
The primary activity for this NomCom will begin in July 2017 and should be completed in January 2018. 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 able to attend IETF 100 (Singapore) to conduct interviews. Being at IETF 99 (Prague) is useful for orientation. Being at IETF 101 (London) is not essential.
Please volunteer by sending me an email before 23:59 UTC June 26, 2017, as follows:
To: nomcom-chair-2017 at ietf dot org
Subject: NomCom 2017-18 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/2017/
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!
Peter Yee
peter at akayla dot com
nomcom-chair-2017 at ietf dot org
