AT-LARGE GATEWAY

At-Large Website

ALAC

RALOs

At-Large Regional Policy Engagement Program (ARPEP)

At-Large Governance

At-Large Reports

Policy Comments & Advice

Working Groups

ICANN Meetings

At-Large Summit (ATLAS III)

At-Large Review Implementation Plan Development

ALAC and RALO Elections, Selections, and Appointments

At-Large Priority Activities - 2021

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

Compare with Current View Page History

« Previous Version 7 Next »

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

DRAFT PTI and IANA FY21 Operating Plan and Budgets

COMMENT

Ricardo Holmquist

22 November 2019

26 November 2019

Shani Quidwai
planning@icann.org

Hide the information below, please click here 

Brief Overview

Purpose: To obtain public comments on the Draft FY21 Public Technical Identifiers (PTI) Operating Plan and Budget and the DRAFT FY21 Internet Assigned Numbers Authority (IANA) Operating Plan and Budget.

Current Status: These DRAFT Plans have been prepared and published for public review and comment.

Next Steps: ICANN community participants should submit questions for clarification about details in the draft plans to planning@icann.org by 18 October 2019. The organization will provide responses by 25 October 2019.

The organization will then:

  1. Consult the community as-needed to ensure understanding of the comments submitted and prepare a report of public comments.
  2. Incorporate changes to the draft plans based on suggestions and comments.
  3. Propose the revised FY21 PTI Operating Plan and Budget for PTI Board Adoption in December 2019.
  4. Propose the revised FY21 IANA Budget for IANA for ICANN Board Adoption in January 2020.

Section I: Description and Explanation

Two documents are presented for community discussion and public comment: 1) the Draft PTI FY21 Operating Plan and Budget and 2) the Draft FY21 IANA Operating Plan and Budget ("IANA Budget"). These budgets have been presented in separate documents as they are adopted by different organizations at separate times.

The PTI Board will be asked to adopt the PTI Draft FY21 Operating Plan and Budget in December 2019. The ICANN Board will be asked to adopt the IANA Budget in January 2020.

The Empowered Community has a right over the IANA Budget. An overview of the Empowered Community's powers is published on the Empowered Community website.

Section II: Background

PTI was incorporated in August 2016, the second month of ICANN's FY17 budget. The PTI Board was seated during September 2016. It performs the work required to deliver the IANA Services through contracts with ICANN. Excellence in delivering the IANA Services is a key goal in ICANN's Strategic Plan and PTI is working to fulfill that goal.

Section III: Relevant Resources

Document

Purpose

Draft FY21 PTI Operating Plan and Budget

This is a draft document being consulted on. It describes the IANA Services and PTI's planned work for FY21.

Draft FY21 IANA Operating Plan and Budget ("IANA Budget")

This is a draft document being consulted on. The IANA Budget references the PTI Operating Plan and Budget and includes aspects of fulfilling the IANA functions contracted by ICANN, such as the contract with the Root Zone Maintainer.

Section IV: Additional Information

The FY21 Operating Plan and Budget for PTI is scheduled to be adopted by the PTI Board before public comment begins on the ICANN Draft FY21 Operating Plan and Budget.

The revised FY21 Budget for IANA will be reviewed by the ICANN Board Finance Committee, then recommended to the ICANN Board for adoption, and followed by an Empowered Community review period of 28 days.

Section V: Reports

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.

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 FY21, PTI expects to deliver a comprehensive set of systems and tools to support protocol parameter assignment workflows following a multi-year development effort. This 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 demand, as 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 (TLDs) and 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?


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 FY21, PTI expects to deliver a comprehensive set of systems and tools to support protocol parameter assignment workflows following a multi-year development effort. This 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 demand, as 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 (TLDs) and 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. 

  • No labels