From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 4468621F13F; Mon, 13 May 2013 15:49:05 -0700 (PDT) Received: by mail-ve0-f177.google.com with SMTP id ox1so1314186veb.22 for ; Mon, 13 May 2013 15:49:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=knwdANnG8IIuGZS5miSZ2vpzal6tSSY8ZLGvUHEAv8I=; b=PHcTzwW3VC67mw+h0EFiIuPfI/MqQDs9qO4N5fT88kyFyu0i4XVqFJ8aVh/mst1Tjy k0TFJHjq3sHyqjCqmOCq3mIei9Q4MT22akvpLAE/CDhxNvmNo5aTHVwczMS75G7DdREL NDV4IZX1neyLYB4RVQvXyzKg62LvI/UlfWKgtygt6HNSX3qoHh6S0U9yEiooqHu5JyNX 9GHYhSPNjko5b8cSJYHNl0rg/x9izC17FnKQy6GKn5RrI8igmqb/tbdfdgc/ENwDrpIk Reo5QDg78sjE3KeToujQuXjGEdJg1fTAAiSuhr9nypitc78rcEhfgOGivEly/L6UG30N ayBQ== MIME-Version: 1.0 X-Received: by 10.52.233.199 with SMTP id ty7mr1441867vdc.122.1368485343939; Mon, 13 May 2013 15:49:03 -0700 (PDT) Received: by 10.58.7.10 with HTTP; Mon, 13 May 2013 15:49:03 -0700 (PDT) In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712953BA68F@MX15A.corp.emc.com> References: <8D3D17ACE214DC429325B2B98F3AE712953BA68F@MX15A.corp.emc.com> Date: Mon, 13 May 2013 15:49:03 -0700 Message-ID: From: Dave Taht To: bloat , cerowrt-devel@lists.bufferbloat.net Content-Type: multipart/alternative; boundary=089e012948f8ce561804dca1523d Subject: [Cerowrt-devel] FW: NomCom 2013-2014 Call for Volunteers - CORRECTED dates in first sentence X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 May 2013 22:49:05 -0000 --089e012948f8ce561804dca1523d Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The transport AD debate was a real disaster at ietf 86. I don't know how to fix it, as I don't understand the processes that broke down, in the first place. That said, well, 10 people selected randomly from volunteers from the ietf population are the people defined to drive the selection processes. humming is not enough. ---------- Forwarded message ---------- From: Black, David Date: Mon, May 13, 2013 at 3:31 PM Subject: [tsvwg] FW: NomCom 2013-2014 Call for Volunteers - CORRECTED dates in first sentence To: Transport Area Working Group Discussion List Please give some thought to participating in this year's NomCom. This is a great way to contribute to the IETF. Thanks, --David -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org= ] On Behalf Of Mankin, Allison Sent: Monday, May 13, 2013 5:27 PM To: ietf-announce@ietf.org Subject: NomCom 2013-2014 Call for Volunteers - CORRECTED dates in first sentence The IETF nominating committee (nomcom) process for 2013-14 has begun. 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 verifiabl= y random way from a pool of volunteers. The more volunteers, the better chanc= e we have of choosing a random yet representative cross section of the IETF population. This year, a challenge: let's get beyond the 100-mark for number of volunteers. Let's get to 200 volunteers! The details of the operation of the nomcom can be found in RFC 3777. Volunteers must have attended 3 of the past 5 IETF meetings. As specified in RFC 3777, that means three out of the five past meetings up to the time thi= s email announcement goes out to start the solicitation of volunteers. The five meetings out of which you must have attended three are IETF 82, 83, 84, 85, 86. If you qualify, please volunteer. However, much as we want this, before yo= u decide to volunteer, please be sure you are willing to forgo appointment to any of the positions for which this nomcom is responsible. The list of people and posts whose terms end with the March 2014 IETF meeting, and thus the positions for which this nomcom is responsible, are IAOC: Chris Griffiths IAB: Bernard Aboba Marc Blanchet Ross Callon Eliot Lear Hannes Tschofenig IESG: Barry Leiba (Applications) Brian Haberman (Internet) Benoit Claise (Operations and Management) Gonzalo Camarillo (RAI) Stewart Bryant (Routing) Sean Turner (Security) Martin Stiemerling (Transport) The primary activity for this nomcom will begin in July 2013 and should be completed in January 2014. 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. Thus, being a nomcom member does require some time commitment. Please volunteer by sending me an email before 11:59 pm EDT (UTC -4 hours) June 16, 2013, as follows: To: amankin@verisign.com Subject: Nomcom 2013-14 Volunteer Please include the following information in the email body: // First/Given Name followed by Last/Family Name // matching how you enter it in the IETF Registration Form) // Typically what goes in the Company field // in the IETF Registration Form [] // For confirmation if selected You should expect an email response from me within 3 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. Volunteering for the nomcom is a great way to contribute to the IETF! 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 couple weeks. Thank you! Allison Mankin amankin@verisign.com P.S. Because the 2012-2013 nomcom is still at work, we cannot use the ietf addresses for the nomcom chair or the nomcom committee yet, so please send all the volunteer mail (and any questions/comments you may have) to the address given. --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html --089e012948f8ce561804dca1523d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The transport AD debate was a real disaster at ietf 86.

I don't = know how to fix it, as I don't understand the processes that broke down= , in the first place.

That said, well, 10 people selected randomly = from volunteers from the ietf population are the people defined to drive th= e selection processes.

humming is not enough.

---------- For= warded message ----------
From: Black, Dav= id <david.b= lack@emc.com>
Date: Mon, May 13, 2013 at 3:31 PM
Subject: [tsvwg] FW: NomCom 2013-2014= Call for Volunteers - CORRECTED dates in first sentence
To: Transport A= rea Working Group Discussion List <tsv= wg@ietf.org>


Please give some thought to participating in this year's NomCom= .
This is a great way to contribute to the IETF.

Thanks,
--David


-----Original Message-----
From: ietf-announce-bounc= es@ietf.org [mailto:i= etf-announce-bounces@ietf.org] On Behalf Of Mankin, Allison
Sent: Monday, May 13, 2013 5:27 PM
To: ietf-announce@ietf.org Subject: NomCom 2013-2014 Call for Volunteers - CORRECTED dates in first se= ntence

The IETF nominating committee (nomcom) process for 2013-14 has begun. 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 verifiabl= y
random way from a pool of volunteers. The more volunteers, the better chanc= e
we have of choosing a random yet representative cross section of the IETF population. =A0This year, a challenge: =A0let's get beyond the 100-mark= for
number of volunteers. =A0Let's get to 200 volunteers!

The details of the operation of the nomcom can be found in RFC 3777.

Volunteers must have attended 3 of the past 5 IETF meetings. =A0As specifie= d in
RFC 3777, that means three out of the five past meetings up to the time thi= s
email announcement goes out to start the solicitation of volunteers. The fi= ve
meetings out of which you must have attended three are IETF 82, 83, 84, 85,= 86.

If you qualify, please volunteer. =A0However, much as we want this, before = you
decide to volunteer, please be sure you are willing to forgo appointment to any of the positions for which this nomcom is responsible.

The list of people and posts whose terms end with the March 2014 IETF
meeting, and thus the positions for which this nomcom is responsible, are
IAOC:
Chris Griffiths

IAB:

Bernard Aboba
Marc Blanchet
Ross Callon
Eliot Lear
Hannes Tschofenig

IESG:

Barry Leiba (Applications)
Brian Haberman (Internet)
Benoit Claise (Operations and Management)
Gonzalo Camarillo (RAI)
Stewart Bryant (Routing)
Sean Turner (Security)
Martin Stiemerling (Transport)

The primary activity for this nomcom will begin in July 2013 and should be<= br> completed in January 2014. =A0The nomcom will have regularly scheduled
conference calls to ensure progress. =A0There will be activities to collect=
requirements from the community, review candidate questionnaires, review feedback from community members about candidates, and talk to
candidates. =A0Thus, being a nomcom member does require some time commitmen= t.

Please volunteer by sending me an email before 11:59 pm EDT (UTC -4 hours)<= br> June 16, 2013, as follows:

To: amankin@verisign.com
Subject: Nomcom 2013-14 Volunteer

Please include the following information in the email body:

=A0<Your Full Name>
=A0 // First/Given Name followed by Last/Family Name
=A0 // matching how you enter it in the IETF Registration Form)
=A0<Current Primary Affiliation>
=A0 // Typically what goes in the Company field
=A0 // in the IETF Registration Form
[<All email addresses used to register for the past 5 IETF meetings>]=
=A0<Preferred email address>
=A0<Telephone number>
=A0 // For confirmation if selected

You should expect an email response from me within 3 business days stating<= br> whether or not you are qualified. =A0If you don't receive this response= ,
please re-send your email with the tag "RESEND"" added to th= e 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. Volunteering for the nomcom is a great way to contribute
to the IETF!

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 couple weeks.

Thank you!
Allison Mankin
amankin@verisign.com

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
address given.











--
Dave T=E4ht

Fixing bufferbloa= t with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html=20 --089e012948f8ce561804dca1523d--