Oooops CORRECTION Reply to This - Re: Nomcom 2013-14 Volunteering - 2nd Call

"Mankin, Allison" <amankin@verisign.com> Wed, 29 May 2013 21:09 UTC

Return-Path: <amankin@verisign.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B49C21F9263; Wed, 29 May 2013 14:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 tyxesYK4GZB3; Wed, 29 May 2013 14:08:58 -0700 (PDT)
Received: from exprod6og127.obsmtp.com (exprod6og127.obsmtp.com [64.18.1.78]) by ietfa.amsl.com (Postfix) with ESMTP id E702D21F856D; Wed, 29 May 2013 14:08:57 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob127.postini.com ([64.18.5.12]) with SMTP ID DSNKUaZuaSRoZGmiHTPtkEJqCWlP1+2palzH@postini.com; Wed, 29 May 2013 14:08:58 PDT
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id r4TL8vRH015040 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 May 2013 17:08:57 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Wed, 29 May 2013 17:08:56 -0400
From: "Mankin, Allison" <amankin@verisign.com>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
Subject: Oooops CORRECTION Reply to This - Re: Nomcom 2013-14 Volunteering - 2nd Call
Thread-Topic: Oooops CORRECTION Reply to This - Re: Nomcom 2013-14 Volunteering - 2nd Call
Thread-Index: AQHOXLAohg3/5/hJhka74OTHCGTCZZkc6yMA
Date: Wed, 29 May 2013 21:08:56 +0000
Message-ID: <639CE511-1B0E-47D8-9D9D-1A48964467E2@verisign.com>
References: <D9F5D76C-1929-4C6B-B902-3A0854821FB7@verisign.com>
In-Reply-To: <D9F5D76C-1929-4C6B-B902-3A0854821FB7@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0553B016F069A34196A7AF0900A6EC62@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org, "Mankin, Allison" <amankin@verisign.com>
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 21:09:04 -0000

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