[karp] Fwd: Oooops CORRECTION Reply to This - Re: Nomcom 2013-14 Volunteering - 2nd Call

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 29 May 2013 22:54 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA60221F971C; Wed, 29 May 2013 15:54:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sQB7C2TgF9BS; Wed, 29 May 2013 15:53:54 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id B1E7121F9712; Wed, 29 May 2013 15:53:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 9ED421C046B; Wed, 29 May 2013 15:53:52 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-134-119.clppva.east.verizon.net [70.106.134.119]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id C6BA71C06E9; Wed, 29 May 2013 15:53:51 -0700 (PDT)
Message-ID: <51A686FC.9070704@joelhalpern.com>
Date: Wed, 29 May 2013 18:53:48 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "karp@ietf.org" <karp@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
References: <639CE511-1B0E-47D8-9D9D-1A48964467E2@verisign.com>
In-Reply-To: <639CE511-1B0E-47D8-9D9D-1A48964467E2@verisign.com>
X-Forwarded-Message-Id: <639CE511-1B0E-47D8-9D9D-1A48964467E2@verisign.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [karp] Fwd: Oooops CORRECTION Reply to This - Re: Nomcom 2013-14 Volunteering - 2nd Call
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for key management for routing and transport protocols <karp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/karp>, <mailto:karp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/karp>
List-Post: <mailto:karp@ietf.org>
List-Help: <mailto:karp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/karp>, <mailto:karp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 22:54:00 -0000

For those of you who did not get the message the first time...
Yours,
Joel


-------- Original Message --------
Subject: Oooops CORRECTION Reply to This - Re: Nomcom 2013-14 
Volunteering - 2nd Call
Date: Wed, 29 May 2013 21:08:56 +0000
From: Mankin, Allison <amankin@verisign.com>
Reply-To: Mankin, Allison <amankin@verisign.com>
To: ietf-announce@ietf.org <ietf-announce@ietf.org>
CC: <ietf@ietf.org> <ietf@ietf.org>

Sorry - my eye was on entering the reply-to field and then I 
forgot....apologies in advance for
pain that may result from this lapse.


On May 29, 2013, at 5:04 PM, "Mankin, Allison" <amankin@verisign.com> wrote:

> Hi, everyone,
>
> Remember that I'm challenging the IETF to come up with 200 volunteers for
> the upcoming nomcom.  You can volunteer just by hitting Reply to this email.
>
> What are you waiting for??  The more volunteers we get, the better chance we
> have of choosing a random yet representative cross section of the IETF
> population.  Respond to the 200-volunteer challenge and hit Reply right now.
> (Well, much as I want you to do this, please look below at the posts being
> filled and be sure you are willing to forgo trying for any of them this year).
>
> The official information:
> The IETF nominating committee (nomcom) process for 2013-14 is under way. 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 details of the selection and operation of the nomcom can be found
> in RFCs 3777, 5078, 5633, 5680, and 6859.  Four of those RFCs  (3777, 5633,
> 5680 and 6859)  comprise BCP 10. We will also reference RFC 3797.
>
> 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 82, 83, 84, 85, 86.
>
> If you qualify, reply to this email and volunteer.
>
> 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.  Being a nomcom member will require some time
> commitment - there will be interviews with candidates at meetings, regularly
> scheduled conference calls to ensure progress, collection and review of
> requirements from the commitment, review of candidate questionnaires and
> of community feedback.  A more detailed timetable for the nomcom tasks
> will appear soon.
>
> Please respond to this email before 11:59 pm EDT (UTC -4 hours)
> June 16, 2013.  In the body include:
> 1. your Given Name as you enter it when you register for the IETF
> 2. your Family Name as you enter it when you register for the IETF
> 3. your current primary affilation (the information you enter into the Company field)
> 4. any/all email addresses you've used to register for IETF meetings
> 5. which email address you prefer
> 6. your phone number (for our use in confirming you if selected).
>
> You should expect an email response from me within 3 business days stating
> whether or not you are qualified (and added to the list).  If you don't receive this
> response, please re-send your email adding the tag "RESEND" to the subject line.
>
> Participating in the IETF nomcom is a meaningful and fun way to contribute to the IETF.
> Please help us meet the 200-volunteer challenge by hitting Reply to this message today.
>
> Allison
>
> Allison Mankin
> Nomcom Chair 2013-2014