[ppsp] 转发: NomCom 2014-2015 Call for Volunteers

Zongning <zongning@huawei.com> Fri, 23 May 2014 00:03 UTC

Return-Path: <zongning@huawei.com>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA8141A02A3 for <ppsp@ietfa.amsl.com>; Thu, 22 May 2014 17:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.902
X-Spam-Level:
X-Spam-Status: No, score=-98.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 5hAxSqTL6dof for <ppsp@ietfa.amsl.com>; Thu, 22 May 2014 17:03:21 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B45D81A0295 for <ppsp@ietf.org>; Thu, 22 May 2014 17:03:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BHC18146; Fri, 23 May 2014 00:03:17 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 23 May 2014 01:03:02 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 23 May 2014 01:03:16 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Fri, 23 May 2014 08:03:12 +0800
From: Zongning <zongning@huawei.com>
To: "ppsp@ietf.org" <ppsp@ietf.org>
Thread-Topic: NomCom 2014-2015 Call for Volunteers
Thread-Index: AQHPcRXSEKVybB6Dr0mPzdiT1genj5tGoiRggAav9NA=
Date: Fri, 23 May 2014 00:03:11 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC66677966139099@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.54]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/i4yRbEVlgMi7m5j76IzoOdySrFo
Subject: [ppsp] 转发: NomCom 2014-2015 Call for Volunteers
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ppsp/>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 May 2014 00:03:24 -0000

Hi, folks,

Please consider volunteering for NomCom, if you are willing to contribute to IETF on this perspective. 

Thanks.

-Ning

> -----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