Historical Resolution Tracking Feature » SO/AC FY17 Additional Budget Requests Approval
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.
SO/AC FY17 Additional Budget Requests Approval
Board approves committing $643,700 during Fiscal Year 2017 to cover the costs associated with the adopted SO/AC additional budget requests.
Whereas, prior discussions between community members and ICANN staff members identified the need for an earlier decision on the funding of additional budget requests from ICANN's Supporting Organizations (SO) and Advisory Committees (AC).
Whereas, the staff created an SO/AC additional budget requests process, to collect, review and submit for Board approval funding requests from the SOs and ACs.
Whereas, requests were submitted by the ICANN community by the set deadline, and were reviewed by a panel of staff members representing the Policy, Stakeholder Engagement and Finance departments.
Whereas, the review panel recommended the approval of requests representing $643,700 for approval.
Whereas the Board Finance Committee, reviewed the process followed and the staff proposal, and has recommended that the Board approve the staff recommendation.
Resolved (2016.05.15.09), the Board approves committing $643,700 during Fiscal Year 2017 to cover the costs associated with the adopted SO/AC additional budget requests.
The budget approval earlier in the year is a reasonable accommodation of the established budget approval process and timeline, that facilitate the work of the ICANN community and of the ICANN staff, and does not create additional expenses. The amount of the committed expenses resulting from this resolution is considered sufficiently small to not require that funding resources are specifically identified for each request.
There is no anticipated impact from this decision on the security, stability and resiliency of the domain name system as a result of this decision.
The approval process is an Organizational Administrative process that has already been subject to significant input from the community