From nobody Tue Jun 7 09:03:28 2016 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E6C612D095; Tue, 7 Jun 2016 09:03:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.689 X-Spam-Level: X-Spam-Status: No, score=-102.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, USER_IN_WHITELIST=-100] 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 16vCrDrmxWfR; Tue, 7 Jun 2016 09:03:25 -0700 (PDT) Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 5B7BA126BF7; Tue, 7 Jun 2016 09:03:25 -0700 (PDT) Received: by mail-yw0-x22e.google.com with SMTP id o16so174169188ywd.2; Tue, 07 Jun 2016 09:03:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=8bdVjGmhhaWVMVBcMz+pxelqGQMR9PPzqegGYpeZ0iA=; b=QrRbOia6eMsRPGAHMxMUKaHYpwH6HkZdFeUs49VSvAlAE+dFvE54xT9ms0+ZBaNupK WbEQ3SHpDpkCtCE7PAT9zpoVwqem6Xz5DdEfnf1jWuUOhYxHXKdavCnWm7emygVhgc5w TkDmVHETfkFsWjKSlCUwc0YDDR/7mveim4t32c7GP8wvQ2xAdtwBki5jU/pAhskO0CCA O7SO7i15XsaOgHOihKkZxdbWksjE1ipKWaI3Y6OcXoGPu/rdowKbPelGMqOjPZkHtI4g HlJkgoHWNtwTzwHDZvnaZ2JTIrlvaf3hY7rLPN7bbxMN1VC31dcgbuU2vw0L3x8nRHsy ZFJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=8bdVjGmhhaWVMVBcMz+pxelqGQMR9PPzqegGYpeZ0iA=; b=Y8JcMkrt2zsspGZvRWILkkvoJF61O7Psa2xJCNtUJK9MenangZbOl9VH1mDCUOYZQ6 uAYBodnRYTOVA3scbeW12AXlFYkXABFcB5tDYq164nEp7v0tgvcs32OgOiqnwmNRH+Dz a6dyL6DqS+dj4X6dYZNnvx/dM8K+gmRV7q9SBClR2djp5BwC490O/nLOGofy5GgLdvmV qZWh8O12VREssvstugUIYIixlmcmORveqFlS2y0CtRHXhLcS1TsJrAFhA/VkbUOYsXO1 9L16u+rAnJCItjXZZ/Ir+m11S9LXlr6J6TnY2iKvt+3D03bWJOo4fu+VNlzkZfWbVj3O gSyA== X-Gm-Message-State: ALyK8tJRS5LUbX53xhFGFDuD+mfJ3GpOjlccF460h679BTfOwXnERUWDQ0DZsdnBAbUGNStXG++q5ZNunoBx6w== X-Received: by 10.13.194.195 with SMTP id e186mr108063ywd.7.1465315404659; Tue, 07 Jun 2016 09:03:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.221.74 with HTTP; Tue, 7 Jun 2016 09:03:24 -0700 (PDT) In-Reply-To: <20160607143317.13664.96093.idtracker@ietfa.amsl.com> References: <20160607143317.13664.96093.idtracker@ietfa.amsl.com> From: Alia Atlas Date: Tue, 7 Jun 2016 12:03:24 -0400 Message-ID: Subject: Fwd: NomCom 2016-2017 Second Call for Volunteers To: "rtg-chairs@ietf.org" , "routing-discussion@ietf.org" Content-Type: multipart/alternative; boundary=001a114e6cce2dc2880534b25497 Archived-At: X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2016 16:03:27 -0000 --001a114e6cce2dc2880534b25497 Content-Type: text/plain; charset=UTF-8 ---------- Forwarded message ---------- From: NomCom Chair 2016 Date: Tue, Jun 7, 2016 at 10:33 AM Subject: NomCom 2016-2017 Second Call for Volunteers To: IETF Announcement List Subject: NomCom 2016-2017 Second Call for Volunteers The IETF nomcom appoints individuals 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, and BCP10/RFC3797 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 = 91 (Honolulu) \ 92 (Dallas) \ 93 (Prague) -*** ANY THREE! 94 (Yokohama) / 95 (Buenos Aires) / 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 2016 - 2017 Nomcom is responsible for filling. The list of people and posts whose terms end with the March 2017 IETF meeting, and thus the positions for which this nomcom is responsible, are IAOC: Lou Berger IAB: Ralph Droms* Russ Housley* Robert Sparks Andrew Sullivan Dave Thaler Suzanne Woolf IESG: Jari Arkko (GEN) Deborah Brungard (RTG) Ben Campbell (ART) Spencer Dawkins (TSV) Stephen Farrell (SEC)* Joel Jaeggli (OPS)* Terry Manderson (INT) Alvaro Retana (RTG) 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 (with the exception of GEN) have at least one continuing AD. Current members tagged with a * have indicated that they will not accept another nomination to serve in their current role. The primary activity for this nomcom will begin in July 2016 and should be completed in January 2017. 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 IETF97 (Seoul) to conduct interviews. Being at IETF96 (Berlin) is useful for orientation. Being at IETF98 is not essential. Please volunteer by sending me an email before 23:59 UTC June 20, 2016, as follows: To: nomcom-chair-2016@ietf.org Subject: Nomcom 2016-17 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/2016/ I will be publishing details of the randomness seeds to be used for the RFC 3797 selection process within the next few weeks. Thank you! Lucy Lynch llynch@civil-tongue.net nomcom-chair-2016@ietf.org --001a114e6cce2dc2880534b25497 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

---------- Forwarded messag= e ----------
From: NomCom Chair 2016 <= span dir=3D"ltr"><nomcom-c= hair-2016@ietf.org>
Date: Tue, Jun 7, 2016 at 10:33 AM
= Subject: NomCom 2016-2017 Second Call for Volunteers
To: IETF Announceme= nt List <ietf-announce@ietf.or= g>


Subject: NomCom 2016-2017 Second Call for Volunteers
The IETF nomcom appoints individuals 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 o= f
choosing a random yet representative cross section of the IETF population.<= br>
The details of the operation of the nomcom can be found in RFC 7437, and BCP10/RFC3797 details the selection algorithm.

Volunteers must have attended 3 of the past 5 IETF meetings.=C2=A0 As speci= fied
in RFC 7437, that means three out of the five past meetings up to the time<= br> this email announcement goes out to start the solicitation of volunteers. The five meetings out of which you must have attended *three* are:

IETF =3D 91 (Honolulu)=C2=A0 =C2=A0 =C2=A0 \
=C2=A0 =C2=A0 =C2=A0 =C2=A092 (Dallas)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0\ =C2=A0 =C2=A0 =C2=A0 =C2=A093 (Prague)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -*= ** ANY THREE!
=C2=A0 =C2=A0 =C2=A0 =C2=A094 (Yokohama)=C2=A0 =C2=A0 =C2=A0 =C2=A0/
=C2=A0 =C2=A0 =C2=A0 =C2=A095 (Buenos Aires)=C2=A0 /


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 2016 - 2017 Nomcom is
responsible for filling.

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

=C2=A0 =C2=A0 Lou Berger

IAB:

=C2=A0 =C2=A0 Ralph Droms*
=C2=A0 =C2=A0 Russ Housley*
=C2=A0 =C2=A0 Robert Sparks
=C2=A0 =C2=A0 Andrew Sullivan
=C2=A0 =C2=A0 Dave Thaler
=C2=A0 =C2=A0 Suzanne Woolf

IESG:

=C2=A0 =C2=A0 Jari Arkko (GEN)
=C2=A0 =C2=A0 Deborah Brungard (RTG)
=C2=A0 =C2=A0 Ben Campbell (ART)
=C2=A0 =C2=A0 Spencer Dawkins (TSV)
=C2=A0 =C2=A0 Stephen Farrell (SEC)*
=C2=A0 =C2=A0 Joel Jaeggli (OPS)*
=C2=A0 =C2=A0 Terry Manderson (INT)
=C2=A0 =C2=A0 Alvaro Retana (RTG)


All appointments are for 2 years. The ART and Routing areas have 3 ADs and<= br> the General area has 1; all other areas have 2 ADs. Thus, all areas (with the exception of GEN) have at least one continuing AD. Current members
tagged with a * have indicated that they will not accept another nomination=
to serve in their current role.

The primary activity for this nomcom will begin in July 2016 and should be<= br> completed in January 2017.=C2=A0 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<= br> very rewarding experience.

As a member of the nomcom it is very important that you be able to attend IETF97 (Seoul) to conduct interviews. Being at IETF96 (Berlin) is useful fo= r
orientation.=C2=A0 Being at IETF98 is not essential.

Please volunteer by sending me an email before 23:59 UTC June 20, 2016, as<= br> follows:

To: nomcom-chair-2016@ietf.or= g
Subject: Nomcom 2016-17 Volunteer

Please include the following information in the email body:

Your Full Name: __________
=C2=A0 =C2=A0 // as you write it on the IETF registration form
Current Primary Affiliation:
=C2=A0 =C2=A0 // Typically what goes in the Company field
=C2=A0 =C2=A0 // in the IETF Registration Form
Emails: _______________
=C2=A0 =C2=A0// All email addresses used to register for the past 5 IETF me= etings
=C2=A0 =C2=A0// Preferred email address first
Telephone: _______________________
=C2=A0 =C2=A0 // For confirmation if selected

You should expect an email response from me within 5 business days stating<= br> whether or not you are qualified.=C2=A0 If you don't receive this respo= nse,
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 tha= t
nomcom members play a very important role in shaping the leadership of the<= br> IETF. Questions by email or voice are welcome. Volunteering for the nomcom<= br> is a great way to contribute to the IETF!

You can find a detailed timeline on the nomcom web site at:

=C2=A0 =C2=A0 https://datatracker.ietf.org/nomcom/2016/=

I will be publishing details of the randomness seeds to be used for the
RFC 3797 selection process within the next few weeks.

Thank you!

Lucy Lynch
llynch@civil-tongue.net
nomcom-chair-2016@ietf.org


--001a114e6cce2dc2880534b25497--