Public Comment CloseStatement
Name 

Status

Assignee(s)

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

27 November 2019

COMMENT

Shani Quidwai
planning@icann.org


Hide the information below, please click here 

FINAL VERSION 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.




DRAFT SUBMITTED FOR DISCUSSION

The first draft submitted will be placed here before the call for comments begins. The Draft should be preceded by the name of the person submitting the draft and the date/time. If, during the discussion, the draft is revised, the older version(S) should be left in place and the new version along with a header line identifying the drafter and date/time should be placed above the older version(s), separated by a Horizontal Rule (available + Insert More Content control).

The proposed PTI and IANA FY21 Operating Plan and Budgets are aligned with the strategic plan of ICANN, and also very similar to previous years' budgets. An adjustment in the PTI budget is noticeable, including adjustments in salaries, services and other administrative cross-charges from ICANN to PTI or IANA.

However, the last paragraph of the executive summary reads:

"In FY21PTI expectto deliver a comprehensive set of systems and tools to support protocol parameter assignment workflows following a multi-year development effortThis investment will enhance the way service is delivered to the Internet standards community by providing modern interfaces and request management. Other areas of activity include continued evolution of the Root Zone Management System (RZMS) to cater for customer demandas well as ongoing enhancement to the IANA website and continuous iteration on the root zone key management software and facilities. ICANN initiatives and their timing will inform aspects of this work that contain a significant IANA component, such as variant top level domains (TLDsand the subsequent procedures for new generic TLD (gTLD) delegations."

In August of this year, community comment was requested regarding the evolution of the Root Zone Management System, based on RSSAC 037 and RSSAC 038. The ALAC provided a statement in response to the ICANN Public Comment on Evolving the Governance of the Root Server System accordingly. 

This evolution involves a big change in the ownership and maintenance of the Root Servers. But these changes are not reflected in the proposed PTI and IANA FY21 Operating Plan and Budgets, which will ultimately handle these servers. There is not even a notice that this evolution might occur, nor a warning of increases in special capital expenses, human resource additions or professional services required to implement this change. 

3 Comments

  1. Quote: This evolution involves a big change in the ownership and maintenance of the Root Servers.But these changes are not reflected in the proposed PTI and IANA FY21 Operating Plan and Budgets, which will ultimately handle these servers.


    believe the big change with Root Servers has to do with mostly with its governance  and not ownership. Also, It is my understanding that IANA does not handle any of these servers. These are independently managed. So, this statement needs work since is not 100% correct. 

  2. I think Eduardo is right.

    Maybe we can turn that to a question?

    Proposal

    "This evolution involves a big change in the governance of the Root Servers. Did these changes can have any consequences (short, medium or long term) to the PTI and IANA Operating Plan and Budgets? DID ICANN, PTI and IANA need to be ready to take on board any additional Root Server?"

  3. Based on the previous comments:


    The proposed PTI and IANA FY21 Operating Plan and Budgets are aligned with the strategic plan of ICANN, and also very similar to previous years' budgets. An adjustment in the PTI budget is noticeable, including adjustments in salaries, services and other administrative cross-charges from ICANN to PTI or IANA.

    However, the last paragraph of the executive summary reads:

    "In FY21PTI expectto deliver a comprehensive set of systems and tools to support protocol parameter assignment workflows following a multi-year development effortThis investment will enhance the way service is delivered to the Internet standards community by providing modern interfaces and request management. Other areas of activity include continued evolution of the Root Zone Management System (RZMS) to cater for customer demandas well as ongoing enhancement to the IANA website and continuous iteration on the root zone key management software and facilities. ICANN initiatives and their timing will inform aspects of this work that contain a significant IANA component, such as variant top level domains (TLDsand the subsequent procedures for new generic TLD (gTLD) delegations."

    In August of this year, community comment was requested regarding the evolution of the Root Zone Management System, based on RSSAC 037 and RSSAC 038. The ALAC provided a statement in response to the ICANN Public Comment on Evolving the Governance of the Root Server System accordingly. 

    This evolution involves a big change in the governance of the Root Servers. But these changes are not reflected in the proposed PTI and IANA FY21 Operating Plan and Budgets. Did these changes can have any consequences (short, medium or long term) to the PTI and IANA Operating Plan and Budgets? Did ICANN, PTI and IANA need to be ready to take on board any additional Root Server?