Historical Resolution Tracking Feature » 2012-06-23 - Adoption of the FY13 Operating Plan and Budget

Important note: The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.

2012-06-23 - Adoption of the FY13 Operating Plan and Budget


Resolution of the ICANN Board
Topic: 
Operating Plan and Budget
Summary: 

Board adopts the FY13 Operating Plan and Budget.

Category: 
Administration and Budget
Meeting Date: 
Sat, 23 Jun 2012
Resolution Number: 
2012.06.23.21 - 2012.06.23.22
Status: 
Complete
Implementation Actions: 
  • Consider reply comments and recommend changes to the FY13 Budget if warranted
    • Responsible entity: Board Finance Committee
    • Due date: None provided
    • Completion date: 1 July 2012
Resolution Text: 

Whereas, on 6 May 2012, ICANN's Board approved an update to the Strategic Plan:http://www.icann.org/en/planning/.

Whereas, the Framework for the FY13 Operating Plan and Budget was posted on 17 January 2012 for community consultation and was presented during several webinars.

Whereas, community consultations were held to discuss and obtain feedback on the Initial Framework.

Whereas, the draft FY13 Operating Plan and Budget was posted for public comment in accordance with the Bylaws on 1 May 2012 based upon the Framework for the FY13 Operating Plan and Budget, community consultation, and consultations with the Board Finance Committee. <http://www.icann.org/en/public-comment/#op-budget-fy12.>

Whereas, ICANN has actively solicited further community feedback and consultation with the ICANN community through online conference calls, meetings in San Jose, and email communication.

Whereas, the ICANN Board Finance Committee has discussed, and guided staff on, the development of the FY13 Operating Plan and Budget at each of its regularly scheduled meetings.

Whereas, the ICANN Board Finance Committee met in Prague on 23 June 2012 to discuss the FY13 Operating Plan and Budget, and recommended that the Board adopt the FY13 Operating Plan and Budget.

Resolved (2012.06.23.21), the Board adopts the FY13 Operating Plan and Budget <http://www.icann.org/en/about/financials/adopted-opplan-budget-fy13-24jun12-en.pdf> [PDF, 5.11 MB].

Resolved (2012.06.23.22), the Board recognizes that there are some reply comments that have not been responded to and directs the BFC to consider those reply comments, and recommend changes to the FY13 Budget if, after consideration of those reply comments, the BFC determines changes are warranted.

Rationale for Resolution: 

In accordance with Article XVI, Section 4 of the ICANN Bylaws, the Board is to adopt an annual budget and publish it on the ICANN website. On 1 May 2012, a proposed annual budget was drafted and posted based on discussions with the Executive team, and extensive consultations with ICANN Supporting Organizations, Advisory Committees, and other stakeholder groups throughout the prior several months.

In addition to the day-to-day operational requirements, the draft budget includes amounts allocated to various FY13 budget requests received from community leadership. The annual budget discloses the impacts of the new gTLD application process, in direct response to community concerns of the budget framework, which was posted in February 2012. Further, all other comments received on the Framework, have been considered and discussed, and when appropriate and feasible have been adopted. A detailed Operating Plan is included in the budget indicating the major projects and initiatives that staff and community will undertake during the 2012-2013 fiscal year.

This budget will have a positive impact in that it provides a proper framework by which the Strategic Plan will be managed and fulfilled. This will have a fiscal impact on ICANN and the community as is intended. This should not have anything but a positive impact on the security, stability and resiliency of the domain name system (DNS) with respect to any funding that is dedicated to those aspects of the DNS.

Additional Information: