You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Comment Close
Date
Statement
Name 

Status

Assignee(s)

Call for
Comments Open
Call for
Comments
Close 
Vote OpenVote CloseDate of SubmissionStaff Contact and EmailStatement Number
 

Draft ICANN FY17 Operating Plan & Budget and Five-Year Operating Plan Update

DRAFTING

Tijani Ben Jemaa

TBCTBCTBCTBCTBC
Xavier Calvez controller@icann.org
TBC

For information about this Public Comment, please click here 

 

FINAL VERSION TO BE SUBMITTED IF RATIFIED

The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote. 



FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.

 


FIRST DRAFT SUBMITTED

The At-Large Advisory Committee (ALAC) reviewed the draft FY17 Operating Plan & Budget, and find it in general well done, with more clarity compared to the previous years. We especially appreciate the planning process that evolved year over year. We do hope that for the upcoming years, there will be more interaction with the community at all steps of the plan and budget development.

That’s said, the ALAC would like to make the following remarks:

As for the community Support Request, the table on page 11 doe not give any information since it is comparing the $0.6M FY17 estimation to nothing; the FY16 Forecast has been allocated to the expense categories based on the nature of the request. It would be better to reconstitute it and put it in the table for the comparison purpose.

In the draft FY17 Operating Plan & Budget, it is considered that the PTI is there for the IANA naming function only, and that there will be an IANA department in ICANN other than the PTI that will be in charge of the 2 other IANA Functions (Numbering and Protocol Parameters). To the best of our knowledge, this is not accurate. 

Regarding the new gTLD Program variance analysis, we may notice that for FY14, the prior estimated revenues (March 2015) are different from the current estimated ones (February 2016), while FY14 ends on 30 June 2014, much before the date of March 2015. Thus, the prior and current estimation should be both equal to the actual amount. 

The ALAC do not know for what reason it was allocated $0.3M for travel and meetings related to Strategic and Operational Planning. 

As for the “Support Operations” defined as the various programs and projects that support functional operations, the ALAC would prefer to see these programs and projects detailed especially because their cost is quite important ($22.1M).

  • No labels