For your information. In relation to the GNSO Council Additional Budget Requests, please note:

FY18-22- GNSO - GNSO PDP WG Chairs (Leadership Team) Support Pilot Project

GNSO request for PDP Working Group Chair travel funding pilot program at ICANN Public Meetings

(Yes)(32,400)(Marika Konings)

In an effort to test the effectiveness of furthering face-to-face working group deliberations at ICANN public meetings, four travelers from GNSO Policy Development Process (PDP) Working Group (WG) leadership teams are approved on a pilot basis per each ICANN public meeting in FY18 (ICANN60, 61 and 62).  The GNSO Council is expected to develop clear and transparent guidelines for how candidates can apply and how selections are made, in keeping with the criteria outlined in the request. A report is to be submitted by the GNSO Council evaluating the value of attendance to the meeting against the metrics included in the request to sbr-outcomes@icann.org within 60 days of attending each meeting.

Due to substantial traveler support increases across the organization, meeting space planning and hotel room blocks arrangements, the community will not have the flexibility to reallocate unused slots to other public meetings throughout the year. Unused slots cannot be carried forward to future meetings and will remain unused.

Approved travel: economy airfare + hotel + per diem. Number of hotel nights limited to the number of days relevant to the PDP-WG meeting.  If this pilot proves successful, permanent travel slot increases will need to be approved through the normal operating plan and budget development process.

FY18-23- GNSO - GNSO Council Strategic Planning Session

GNSO request for Intersessional GNSO Council strategy session face-to-face for FY18

(Yes)(75,000)(Marika Konings)

This meeting concept has proven useful for other parts of the ICANN community and merits a pilot effort in FY18 to see if it could improve the effectiveness and efficiency of the GNSO Council's operations. ICANN office location is required, with preference for Los Angeles due to available physical conference facilities. Granting of support is contingent on the submission of a written report to be submitted within 45 days of the meeting which addresses each itemized metric as per request. Report to be submitted to sbr-outcomes@icann.org and is a condition of future resource allocations. Collaboration with ICANN's meetings team and Constituency travel team is required, with detailed and finalized information submitted a minimum of five months prior to the proposed meeting dates (including full list of travelers, office location and meeting space requirements). Travel approved for 21 GNSO Council Members and the GNSO Liaison to the GAC for a three-day face-to-face meeting.   The piloting of this meeting in FY18 could have impacts on planning for other community intersessional meeting activities.

Best regards,

Marika

From: <community-finance-bounces@icann.org> on behalf of "Taryn S. Presley" <taryn.presley@icann.org>
Date: Wednesday, April 19, 2017 at 11:40
To: "community-finance@icann.org" <community-finance@icann.org>
Cc: Sally Costerton <sally.costerton@icann.org>
Subject: [community-finance] FY18 SO/AC Additional Budget Requests Decisions

Dear Community Leaders and Members:

The FY18 SO/AC additional budget requests were adopted by the ICANN Board on 19 April 2017. The decisions can be found on the community wiki[community.icann.org] and attached. 

FY18 SO-AC Additional Budget Requests Explanations Adopted Final.docx[community.icann.org]

FY18 SO-AC Additional Budget Requests Explanations Adopted Final.pdf[community.icann.org]

If you have any questions, please contact ICANN staff at controller@icann.org.

Regards,

ICANN Staff

12025 Waterfront Drive, Suite 300

Los Angeles, CA 90094-2536

Telephone Main: 310) 301-5800

Information contained in this e-mail transmission is privileged, confidential and covered by the Electronic Communications Privacy Act, 18 U.S.C. Sections 2510-2521.  If you are not the intended recipient, do not read, distribute or reproduce this transmission.  If you have received this e-mail transmission in error, please notify sender immediately of the error by return e-mail and please delete the message from your system.  Thank you in advance for your cooperation.