The transport AD debate was a real disaster at ietf 86.<br><br>I don't know how to fix it, as I don't understand the processes that broke down, in the first place. <br><br>That said, well, 10 people selected randomly from volunteers from the ietf population are the people defined to drive the selection processes. <br>
<br>humming is not enough.<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Black, David</b> <span dir="ltr"><<a href="mailto:david.black@emc.com">david.black@emc.com</a>></span><br>
Date: Mon, May 13, 2013 at 3:31 PM<br>Subject: [tsvwg] FW: NomCom 2013-2014 Call for Volunteers - CORRECTED dates in first sentence<br>To: Transport Area Working Group Discussion List <<a href="mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>><br>
<br><br>Please give some thought to participating in this year's NomCom.<br>
This is a great way to contribute to the IETF.<br>
<br>
Thanks,<br>
--David<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ietf-announce-bounces@ietf.org">ietf-announce-bounces@ietf.org</a> [mailto:<a href="mailto:ietf-announce-bounces@ietf.org">ietf-announce-bounces@ietf.org</a>] On Behalf Of Mankin, Allison<br>
Sent: Monday, May 13, 2013 5:27 PM<br>
To: <a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a><br>
Subject: NomCom 2013-2014 Call for Volunteers - CORRECTED dates in first sentence<br>
<br>
The IETF nominating committee (nomcom) process for 2013-14 has begun. The<br>
IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,<br>
and the IESG. Ten voting members for the nomcom are selected in a verifiably<br>
random way from a pool of volunteers. The more volunteers, the better chance<br>
we have of choosing a random yet representative cross section of the IETF<br>
population. This year, a challenge: let's get beyond the 100-mark for<br>
number of volunteers. Let's get to 200 volunteers!<br>
<br>
The details of the operation of the nomcom can be found in RFC 3777.<br>
<br>
Volunteers must have attended 3 of the past 5 IETF meetings. As specified in<br>
RFC 3777, that means three out of the five past meetings up to the time this<br>
email announcement goes out to start the solicitation of volunteers. The five<br>
meetings out of which you must have attended three are IETF 82, 83, 84, 85, 86.<br>
<br>
If you qualify, please volunteer. However, much as we want this, before you<br>
decide to volunteer, please be sure you are willing to forgo appointment<br>
to any of the positions for which this nomcom is responsible.<br>
<br>
The list of people and posts whose terms end with the March 2014 IETF<br>
meeting, and thus the positions for which this nomcom is responsible, are<br>
<br>
IAOC:<br>
Chris Griffiths<br>
<br>
IAB:<br>
<br>
Bernard Aboba<br>
Marc Blanchet<br>
Ross Callon<br>
Eliot Lear<br>
Hannes Tschofenig<br>
<br>
IESG:<br>
<br>
Barry Leiba (Applications)<br>
Brian Haberman (Internet)<br>
Benoit Claise (Operations and Management)<br>
Gonzalo Camarillo (RAI)<br>
Stewart Bryant (Routing)<br>
Sean Turner (Security)<br>
Martin Stiemerling (Transport)<br>
<br>
The primary activity for this nomcom will begin in July 2013 and should be<br>
completed in January 2014. The nomcom will have regularly scheduled<br>
conference calls to ensure progress. There will be activities to collect<br>
requirements from the community, review candidate questionnaires, review<br>
feedback from community members about candidates, and talk to<br>
candidates. Thus, being a nomcom member does require some time commitment.<br>
<br>
Please volunteer by sending me an email before 11:59 pm EDT (UTC -4 hours)<br>
June 16, 2013, as follows:<br>
<br>
To: <a href="mailto:amankin@verisign.com">amankin@verisign.com</a><br>
Subject: Nomcom 2013-14 Volunteer<br>
<br>
Please include the following information in the email body:<br>
<br>
<Your Full Name><br>
// First/Given Name followed by Last/Family Name<br>
// matching how you enter it in the IETF Registration Form)<br>
<Current Primary Affiliation><br>
// Typically what goes in the Company field<br>
// in the IETF Registration Form<br>
[<All email addresses used to register for the past 5 IETF meetings>]<br>
<Preferred email address><br>
<Telephone number><br>
// For confirmation if selected<br>
<br>
You should expect an email response from me within 3 business days stating<br>
whether or not you are qualified. If you don't receive this response,<br>
please re-send your email with the tag "RESEND"" added to the subject line.<br>
<br>
If you are not yet sure if you would like to volunteer, please consider<br>
that nomcom members play a very important role in shaping the leadership<br>
of the IETF. Volunteering for the nomcom is a great way to contribute<br>
to the IETF!<br>
<br>
I will be publishing a more detailed target timetable, as well as details<br>
of the randomness seeds to be used for the RFC 3797 selection process,<br>
within the next couple weeks.<br>
<br>
Thank you!<br>
Allison Mankin<br>
<a href="mailto:amankin@verisign.com">amankin@verisign.com</a><br>
<br>
P.S. Because the 2012-2013 nomcom is still at work, we cannot use the ietf<br>
addresses for the nomcom chair or the nomcom committee yet, so please send<br>
all the volunteer mail (and any questions/comments you may have) to the<br>
address given.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div><br><br clear="all"><br>-- <br>Dave Täht<br><br>Fixing bufferbloat with cerowrt: <a href="http://www.teklibre.com/cerowrt/subscribe.html" target="_blank">http://www.teklibre.com/cerowrt/subscribe.html</a>