Re: IETF NOMCOM 2014 - deadline 2015-01-26 - Call for Nominations: 3rd ROUTING AREA DIRECTOR

Loa Andersson <loa@pi.nu> Tue, 20 January 2015 05:02 UTC

Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6DC1ACF60 for <ietf@ietfa.amsl.com>; Mon, 19 Jan 2015 21:02:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, URIBL_DBL_ABUSE_REDIR=0.001] 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 CfJSwyEx37DA for <ietf@ietfa.amsl.com>; Mon, 19 Jan 2015 21:02:39 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B84481A909C for <ietf@ietf.org>; Mon, 19 Jan 2015 21:02:38 -0800 (PST)
Received: from [192.168.1.12] (unknown [112.205.75.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 8A095180155B for <ietf@ietf.org>; Tue, 20 Jan 2015 06:02:29 +0100 (CET)
Message-ID: <54BDE160.7060600@pi.nu>
Date: Tue, 20 Jan 2015 13:02:24 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF NOMCOM 2014 - deadline 2015-01-26 - Call for Nominations: 3rd ROUTING AREA DIRECTOR
References: <20150120011416.23271.30618.idtracker@ietfa.amsl.com>
In-Reply-To: <20150120011416.23271.30618.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/DPsXu5OEYWbcbYXYfWNgsy_3wUI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 05:02:42 -0000

Michael,

I was nominated for the position as 2nd AD, and is willing to stand for
the 3rd AD position. Please let me know if there is anything I need to
update questionnaires.

/Loa

On 2015-01-20 09:14, NomCom Chair 2014 wrote:
> The 2014-15 Nominating Committee (NomCom) is seeking nominations
> from now until January 26, 2015, 23:59UTC for the position of 3rd Routing
> Area Director.  Please see below for this much shorter NomCom schedule.
> For background on the request for a third routing area director please see:
>       http://www.ietf.org/mail-archive/web/ietf/current/msg91370.html
>       http://www.ietf.org/mail-archive/web/ietf/current/msg91030.html
>       http://www.ietf.org/mail-archive/web/ietf/current/msg91015.html
>
>   {A note about candidates that have previously been nominated: a number of
>    people were nominated to the role of 2nd Routing AD.  The NOMCOM Chair
>    will be contacting those candidates to determine if they wish to stand
>    for the third position; if they do, they will be listed for feedback.
>    Additional feedback is welcome; but no previous comments have been lost.}
>
> Nominations may be made by selecting the Nominate link at the top of
> the Nomcom 2014 home page, or by visiting the following URL:
>
> https://datatracker.ietf.org/nomcom/2014/nominate/
>
>    {Note that nominations made using the web tool require an ietf.org
>     datatracker account. You can create a datatracker ietf.org account
>     if you don't have one already by visiting the following URL:
>        https://datatracker.ietf.org/accounts/create/ }
>
> Nominations may also be made by email to nomcom14@ietf.org.
>
> If you use email, please include the word "Nominate" in the Subject and
> indicate in the email who is being nominated, their email address (to
> confirm acceptance of the nomination), and the position for which you
> are making the nomination. If you wish to nominate more than one
> person, please use separate emails to do so.
>
> Self-nominations are welcome!
>
> NomCom 2014-15 will follow the policy for "Open Disclosure of Willing
> Nominees" described in RFC 5680.  As stated in RFC 5680: "The list of
> nominees willing to be considered for positions under review in the
> current Nomcom cycle is not confidential". Willing nominees for each
> position will be listed in a publicly accessible way - anyone with a
> datatracker account may access the lists.  In all other ways, the
> confidentiality requirements of RFC 3777/BCP10 remain in effect.  All
> feedback and all Nomcom deliberations will remain confidential and will
> not be disclosed.
>
> NOTE THAT NOMINATIONS SHOULD NOT WAIT FOR MANAGEMENT PERMISSION.
> Nominees should Accept/Decline as soon as they decide they wish to consider
> it, and if they do not have management (or family) support, then they
> can withdraw.
>
> SCHEDULE FOR THIRD ROUTING AREA (at 23:59 UTC):
>           also see calendar at: http://goo.gl/D3q2CY
> 	- Tuesday, January 20, 2015  - open nominations
> 	- Monday, January 26,  2015  - deadline for nominations/open for comments
> 	- Monday, February 2,  2015  - deadline for questionnaires
> 	- Monday, February 13, 2015  - deadline for comments on persons, and requirements
> 	- Target week for interviews Tuesday, February 3, 2016.
>          (We are aware of IAB workshop that occurs last week of January)
>
> Some additional details from the IESG request:
>       - The IESG is currently proposing to move three working groups from the
>       INT area to the RTG area: L2TPEXT, LISP, and TRILL
>
>       - There is a considerable increase in management-related work in the RTG
>         area. Specifically, there are a lot of new YANG models being
>         written. Although the coordination of YANG across the IETF falls as
>         the responsibility of the OPS ADs (specifically the Management AD) it
>         is expected that the RTG ADs will need to work on an increasing number
>         of YANG documents so familiarity with YANG should be added to the list
>         of desirable (but not mandatory) skills.
>
>       - The reasoning behind the addition of a third RTG AD is that the load
>         in the RTG area is currently unsustainably high. The placement of a
>         third AD will have the effect of spreading that load such that the
>         time requirement may now be more consistent with the work loads of ADs
>         in other areas.
>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64