[xrblock] FW: NomCom 2014-2015 Call for Volunteers

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 18 May 2014 17:54 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3D01A022A for <xrblock@ietfa.amsl.com>; Sun, 18 May 2014 10:54:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level:
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 jZUYt4t9zAfQ for <xrblock@ietfa.amsl.com>; Sun, 18 May 2014 10:54:29 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B9D61A01B1 for <xrblock@ietf.org>; Sun, 18 May 2014 10:54:29 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An8FACrzeFOHCzIm/2dsb2JhbABZgmUhT1ipUgEBAQEBB5orAYELFnSCJQEBAQEDEgtLHQQCAQgNBAQBAQsdBwIwFAcBAQUDAgQTCAYGCAaIHwEMokGpRYULEwSFVYNcghEBgisOAwEfBjICAgKDJYEVBJE6gTqNeYwHgzeBdzk
X-IronPort-AV: E=Sophos;i="4.98,862,1392181200"; d="dat'?scan'208";a="63427655"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 May 2014 13:54:28 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 18 May 2014 13:52:42 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0174.001; Sun, 18 May 2014 19:54:27 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: NomCom 2014-2015 Call for Volunteers
Thread-Index: AQHPcRXSEKVybB6Dr0mPzdiT1genj5tGoiRg
Date: Sun, 18 May 2014 17:54:27 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C7EAAC4@AZ-FFEXMB04.global.avaya.com>
References: <8770.1400250056@sandelman.ca>
In-Reply-To: <8770.1400250056@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: multipart/mixed; boundary="_002_9904FB1B0159DA42B0B887B7FA8119CA5C7EAAC4AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/9I4c4Enh6v0yTKDbdLNZk7pKrlA
Subject: [xrblock] FW: NomCom 2014-2015 Call for Volunteers
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 May 2014 17:54:31 -0000

Please consider volunteering for NomCom - this activity is highly important for the IETF. 

Regards,

Dan


> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Michael Richardson
> Sent: Friday, May 16, 2014 5:21 PM
> To: ietf@ietf.org
> Subject: NomCom 2014-2015 Call for Volunteers
> 
> 
> 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
> 
> IAOC:
> To be confirmed
> 
> IAB:
> Joel Halpern
> Russ Housley
> Eliot Lear
> Xing Li
> Andrew Sullivan
> Dave Thaler
> 
> IESG:
> 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 also a very rewarding experience.
> 
> It is very important that you be able to attend IETF91 to conduct interviews.
> 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:
>     https://datatracker.ietf.org/nomcom/2014/
> 
> 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
> mcr+nomcom@sandelman.ca
> nomcom-chair-2014@ietf.org