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

Loa Andersson <loa@pi.nu> Thu, 30 May 2013 07:53 UTC

Return-Path: <loa@pi.nu>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D00D21F977D for <mpls@ietfa.amsl.com>; Thu, 30 May 2013 00:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.749
X-Spam-Level:
X-Spam-Status: No, score=-101.749 tagged_above=-999 required=5 tests=[AWL=0.851, 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 Lw5-VoC3UULG for <mpls@ietfa.amsl.com>; Thu, 30 May 2013 00:53:46 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0439221F9775 for <mpls@ietf.org>; Thu, 30 May 2013 00:53:46 -0700 (PDT)
Received: from [192.168.1.133] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id CC8091802D34; Thu, 30 May 2013 09:53:44 +0200 (CEST)
Message-ID: <51A70589.10708@pi.nu>
Date: Thu, 30 May 2013 09:53:45 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.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: [mpls] Fwd: Oooops CORRECTION Reply to This - Re: Nomcom 2013-14 Volunteering - 2nd Call
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 07:53:52 -0000

Working Group,

Second call for Nomcom volunteers.  Please consider volunteering
for the the Nomcom. IETF depends greatly on Nomcom and it is an
excellent opportunity to contribute to the IETF.

/Loa
mpls wg co-chair


-------- 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: ietf@ietf.org, "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