From nobody Tue Jan 20 03:47:34 2015 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D10871B2A14 for ; Tue, 20 Jan 2015 03:47:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.899 X-Spam-Level: X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_DBL_ABUSE_REDIR=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 MiDqZbwqXGsm for ; Tue, 20 Jan 2015 03:47:28 -0800 (PST) Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81B361B29DF for ; Tue, 20 Jan 2015 03:47:28 -0800 (PST) Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id t0KBlQ8w016698 for ; Tue, 20 Jan 2015 11:47:26 GMT Received: from 950129200 (178-190-140-73.adsl.highway.telekom.at [178.190.140.73]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id t0KBlKQE016599 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Tue, 20 Jan 2015 11:47:26 GMT From: "Adrian Farrel" To: References: <20150120011416.23271.30618.idtracker@ietfa.amsl.com> In-Reply-To: <20150120011416.23271.30618.idtracker@ietfa.amsl.com> Subject: FW: IETF NOMCOM 2014 - deadline 2015-01-26 - Call for Nominations: 3rd ROUTING AREA DIRECTOR Date: Tue, 20 Jan 2015 11:47:20 -0000 Message-ID: <054c01d034a6$dcf9d380$96ed7a80$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIAkRZwx7gRBowXQssJZDLiShXbE5xoKgiA Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21264.006 X-TM-AS-Result: No--19.422-10.0-31-10 X-imss-scan-details: No--19.422-10.0-31-10 X-TMASE-MatchedRID: UXnHo+oIYgAO0G36v8LMKszWN98iBBeGTGyd6AixReS1eX0jEQ9c6nAX R/gLaDwapFx5sMh8IjnYjM7q3UlBN2MNX/9K+QfeE367MfaNw8MEu3H7rgYVqUh/iPkdEa290TD 6UetkoeUBftb7YlT+WroquXT0vYEj7IFOpFOFSvgSWCj0fkOcnDa9tZoo+dDb+5+93dPb6/dpgr Yvic2QdaEem0w5q6wQY2fJ5C8RKg4yDIdIGryMaLMjW/sniEQKOFrEjYh/1F44PPb1XDCZIeLEh OJ1lYDl0FE+duy4L4TZMs2IMC3mtbpWfYsnvRet/c0+LJTMrN1t3qsaFY4DBBAjolhx4JJgB1yd LuwLBt9KurHuvVERaLJQpyCoEn/6WoaZKZbZe3FIRA38P/dwblBcSr/tgJjIerbS/Z8GD7KK61Q 63RemBBeWHY3LKnzHC3HydM2pinRdFBQXHE6OFwXysW33GYMpboFDJyXKWBmbKItl61J/ycnjLT A/UDoASlnU38LCY8t3M7/Jzxffcd0H8LFZNFG7JQhrLH5KSJ0= Archived-At: X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2015 11:47:31 -0000 > -----Original Message----- > From: NomCom Chair 2014 [mailto:nomcom-chair-2014@ietf.org] > Sent: 20 January 2015 01:14 > To: IETF Announcement List > Cc: ietf@ietf.org; wgchairs@ietf.org; rtg-chairs@ietf.org > Subject: IETF NOMCOM 2014 - deadline 2015-01-26 - Call for Nominations: 3rd > ROUTING AREA DIRECTOR > > 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. From nobody Mon Jan 26 08:23:47 2015 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4B31A9245 for ; Mon, 26 Jan 2015 08:23:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.899 X-Spam-Level: X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_DBL_ABUSE_REDIR=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 OZrhmhw0dr8q for ; Mon, 26 Jan 2015 08:23:42 -0800 (PST) Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7DFE1A9244 for ; Mon, 26 Jan 2015 08:23:41 -0800 (PST) Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id t0QGNdPX022212 for ; Mon, 26 Jan 2015 16:23:39 GMT Received: from 950129200 (194-166-226-72.adsl.highway.telekom.at [194.166.226.72]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id t0QGNba9022142 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Mon, 26 Jan 2015 16:23:38 GMT From: "Adrian Farrel" To: References: <20150126155101.1316.10801.idtracker@ietfa.amsl.com> In-Reply-To: <20150126155101.1316.10801.idtracker@ietfa.amsl.com> Subject: FW: REMINDER: IETF NOMCOM 2014 - deadline 2015-01-26 - Call for Nominations: 3rd ROUTING AREA DIRECTOR Date: Mon, 26 Jan 2015 16:23:37 -0000 Message-ID: <01c201d03984$717677c0$54636740$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQL3sIvupYa1JG2tvwfpKX33ND+lm5qDp4iA Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21284.006 X-TM-AS-Result: No--20.564-10.0-31-10 X-imss-scan-details: No--20.564-10.0-31-10 X-TMASE-MatchedRID: LVaQDjbTf5aJYap0rLccA/HkpkyUphL9Ud7Bjfo+5jQ5CCUkHUNu7tLu X2hj/M7U2J6HcIguTNLbOE9ZlXIwHSk1demPFQNSvHKClHGjjr0khdC0fjzDyIBmm9OromHhbOZ osFyx8rScro0fSQl5WnGCLMaLz0wcE2Px0QhWm3RIOSHptb5tx/sxkEGymdAKH5kZy/EQbgTTWC 0by8npkG6mUHbiBraMOy811XHia/tQFwI4HzSNosrT39PoDNtWUAjrAJWsTe+Y/Ue6G7XIMs3Nx Xt1YjuOM2wx7gJ9AcGIbFRsXjoxxb8pU887Y2CIbEOa88C4NLpkBDPLxNH5BvFJXtgF4GFLoYk2 ByBT6IROC6h6noQ0L4Jwu6ZstNfdNwMsD3l2j7PPfDU9TFrh70Crr/LkAQ46jA++dGUyvWEqCxS HO83tZH5w5FSrjoDV0lEDgrLd5ywJEs3jF5KNyeor0PKDup1CGWAN/II9wcTsLd+6g/VoGqPFjJ EFr+olA9Mriq0CDAihaIfyMkG0L1Z0V5tYhzdWxEHRux+uk8jpP8tMOyYmaA== Archived-At: X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2015 16:23:45 -0000 > -----Original Message----- > From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of NomCom > Chair 2014 > Sent: 26 January 2015 15:51 > To: IETF Announcement List > Cc: wgchairs@ietf.org; ietf@ietf.org > Subject: REMINDER: IETF NOMCOM 2014 - deadline 2015-01-26 - Call for > Nominations: 3rd ROUTING AREA DIRECTOR > > Nominations for 3rd RTG AD are open until 23:59UTC today! > > 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-nomination is 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.