[lisp] Fwd: NomCom 2014-2015 Call for Volunteers

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 16 May 2014 17:06 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id BDDE31A02CC; Fri, 16 May 2014 10:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id IJHo6_IDlC4D; Fri, 16 May 2014 10:06:09 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F113A1A02AE; Fri, 16 May 2014 10:06:08 -0700 (PDT)
Received: from localhost (localhost []) by mailc2.tigertech.net (Postfix) with ESMTP id B1AB5141E34; Fri, 16 May 2014 10:06:01 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-10.clppva.east.verizon.net []) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id D7DC3141E33; Fri, 16 May 2014 10:06:00 -0700 (PDT)
Message-ID: <53764577.6070502@joelhalpern.com>
Date: Fri, 16 May 2014 13:05:59 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "lisp@ietf.org" <lisp@ietf.org>, "karp@ietf.org" <karp@ietf.org>
References: <9913.1400250296@sandelman.ca>
In-Reply-To: <9913.1400250296@sandelman.ca>
X-Forwarded-Message-Id: <9913.1400250296@sandelman.ca>
Content-Type: multipart/mixed; boundary="------------090905030802060406060007"
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/inC4uqsa7w5h0zPZdyfZySD-Jto
Subject: [lisp] Fwd: NomCom 2014-2015 Call for Volunteers
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 May 2014 17:06:11 -0000

Please consider volunteering for the IETF nominating committee.
Broad community participation is important for our process.

Thank you,

-------- Original Message --------
Subject: NomCom 2014-2015 Call for Volunteers
Date: Fri, 16 May 2014 10:24:56 -0400
From: Michael Richardson <mcr+ietf@sandelman.ca>
Reply-To: nomcom-chair-2014@ietf.org
To: ietf@ietf.org

{I have to post using my subscribed address. Appologies for duplicates}

The IETF nominating committee (nomcom) process for 2014-15 has begun. The
IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
and the IESG (including IETF Chair).

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.

Let's break the 200 volunteer mark again this year!

The details of the operation of the nomcom can be found in RFC 3777,
and BCP10/RFC3797 details the selection algorithm.

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 this
email announcement goes out to start the solicitation of volunteers.
The five meetings out of which you must have attended *three*
are IETF 85(Atlanta),      \
          86(Orlando),       \
          87(Berlin),         *** ANY THREE!
          88(Vancouver),     /
          89(London)        /

If you qualify, please volunteer.   However, 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 2015 IETF
meeting, and thus the positions for which this nomcom is responsible, are

To be confirmed

Joel Halpern
Russ Housley
Eliot Lear
Xing Li
Andrew Sullivan
Dave Thaler

Pete Resnick (Applications)
Ted Lemon (Internet)
Joel Jaeggli (Operations and Management)
Richard Barnes (RAI)
Adrian Farrel* (Routing)
Stephen Farrell (Security)
Spencer Dawkins (Transport)
Jari Arkko (Gen)

(names with * have publically indicated they will not serve another term)

The primary activity for this nomcom will begin in July 2014 and should be
completed in January 2015.   The nomcom will have regularly scheduled
conference calls to ensure progress. (We might dogfood WebRTC)
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; but it is 
a very rewarding experience.

It is very important that you be able to attend IETF91 to conduct 
Being at IETF90 is useful for training.  Being at IETF92 is not essential.

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

To: nomcom-chair-2014@ietf.org
Subject: Nomcom 2014-15 Volunteer

Please include the following information in the email body:

  <Your Full Name>
     // First/Given Name followed by Last/Family Name
     // matching how you enter it in the IETF Registration Form)

  <Current Primary Affiliation>
     // Typically what goes in the Company field
     // in the IETF Registration Form
[<All email addresses used to register for the past 5 IETF meetings>]
  <Preferred email address>
  <Telephone number>
     // 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.  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:

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!
Michael Richardson