Tag Archives: Internet Assigned Numbers Authority

IANA Naming Function Review Team Community Webinar

Monday, the Internet Assigned Numbers Authority (IANA) Naming Function Review Team (IFRT) has announced that it is in the final stages of completing its Initial Report. The IFRT will be holding a webinar for the community regarding one of their proposed recommendations that would require an amendment to the IANA Naming Functions Contract between ICANN and its affiliate Public Technical Identifiers (PTI). This amendment may be of particular interest to country code top-level domain (ccTLD) and generic top-level domain (gTLD) registry operators.

Continue reading IANA Naming Function Review Team Community Webinar

ICANN: PTI and IANA FY22 Budget Webinar

ICANN announced Wednesday that its affiliate, Public Technical Identifiers (PTI), is inviting the community to participate in a webinar with Internet Assigned Numbers Authority (IANA) staff and members of the PTI Board to discuss PTI’s Fiscal Year 2022 (FY22) Operating Plan and Budget (PTI OP&B) for delivering the IANA functions.

Continue reading ICANN: PTI and IANA FY22 Budget Webinar

ICANN: Webinar Invitation: PTI FY21-FY24 Strategic Plan

ICANN Thursday announced that its affiliate, Public Technical Identifiers (PTI), invites the community to engage with Internet Assigned Numbers Authority (IANA) staff and members of the PTI Board to discuss the development of its first comprehensive strategic plan.

Continue reading ICANN: Webinar Invitation: PTI FY21-FY24 Strategic Plan

ICANN: Proposed IANA SLAs for Publishing LGRs/IDN Tables

Brief Overview

Purpose: As required by the IANA Naming Function Process for Amending the IANA Naming SLAs, the purpose of this public comment proceeding is to obtain community input on a proposed change to one SLA and three proposed new SLAs which would define expectations of request processing timeliness for ccTLD creation and ccTLD transfers.

If adopted, the changed SLA and new requirements will be added to the performance metrics as defined in the Service Level Agreements for the IANA Naming Functions Contract. The ccTLD delegation and transfer process is designed to assign or re-assign a ccTLD to a manager, taking into account a number of technical and public interest criteria. There is currently a single measurement of staff processing time for ccTLD delegation and transfer requests, representing the cumulative time the request is being processed by the IANA team for the life of a request. However, the processing time for this type of request varies greatly from several weeks to several months. the CSC and PTI determined that perhaps identifying new SLAs that measure these transactions in a totally different manner is necessary.

Current Status: According to the Process for Amending the IANA Naming SLAs, the Customer Standing Committee and PTI have agreed upon the new metrics, and now seek community consultation through this public comment process.

Next Steps: Feedback from this public comment period will be considered for the final SLA recommendation.

Section I: Description and Explanation

The ccTLD delegation and transfer process is designed to assign or re-assign a ccTLD to a manager, taking into account a number of technical and public interest criteria. The processing time for this type of request varies greatly from several weeks to several months. Key factors in the process time include how well-documented the request is when first submitted, the overall complexity of the circumstances of the change and the proposed operations, and how quickly any missing or deficient documentation is cured.

There is currently only one measurement of staff processing time for ccTLD delegation and transfer requests which measures the total time the request is with the IANA team from beginning to end. The current SLA for this metric, “Time to complete all other validations and reviews by Contractor and release request for implementation” for “Creating or Transferring a ccTLD” is 60 days.

In reviewing data from March 2016 to today, the current measurement of 60 days did not prove to be a representative measure of IANA performance given that this type of request is low volume, highly complex, and extremely varied based on the quality of the request submission. The goal in defining the SLA metrics was to create indicators where current actual performance was considered acceptable, given community satisfaction with those levels.

Further consideration of the materials suggests it would be more meaningful to divide the manual processing into more discrete processing steps and focus on measuring performance through new metrics, such as:

  1. Time for staff to evaluate and respond to each submission of supporting documentation by the requester.
  2. Time for staff to produce a completed delegation or transfer report for review by the ICANN Board of Directors after all materials provided by the requester have been deemed sufficient.
  3. The number of interactions with the customer as an indication of the quality of the request (to be provided as information only).

On 7 May 2019 the SLA amendment process was established through an amendment to the IANA Naming Function Contract. Subsequently this proposal has been developed for public comment.

The proposed SLA metrics can be found in the document “Service Levels for the ccTLD Creation and Transfer Process Change Analysis.”

Section II: Background

The IANA Naming Function Contract specifies a set of Service Level Agreements (SLAs) the IANA Naming Functions operator PTI must adhere to and that the Customer Standing Committee (CSC) is empowered to oversee. The “Process for Amending the IANA Naming Service Level Agreements” was utilized in determining the need for these proposed SLA amendments. This process also defines the method for approving a change, as well as the appropriate consultation level needed to finalize a change. This process contains safeguards and mechanisms to ensure that due diligence will be followed in making changes to the SLAs.

Per the process, “If the CSC and PTI reach a mutual decision to proceed with the SLA change, PTI should draft a change recommendation, which includes an impact analysis that expands with further detail based on their earlier discussions during the ‘procedure for determining that a SLA needs amending’ stage.” In accordance with the SLA change process requirement, PTI provided the attached “Service Levels for the ccTLD Creation and Transfer Process Change Analysis” document, which provides a description of the proposed change and additional new SLAs and an implementation analysis. It was determined to move forward with these SLA recommendations

Section III: Relevant Resources

Public Technical Identifiers (PTI)

IANA Naming Functions Contract

IANA Naming Functions Contract Service Level Agreements

IANA Naming Function Process for Amending the IANA Naming SLAs

Section IV: Additional Information

Service Levels for the ccTLD Creation and Transfer Process Change Analysis 

  • Open Date: 14 Oct 2019 23:59 UTC
  • Close Date: 25 Nov 2019 23:59 UTC
  • Staff Report Due: 9 Dec 2019 23:59 UTC

This ICANN announcement was sourced from: https://www.icann.org/public-comments/proposed-sla-for-cctld-creation-transfer-2019-10-14-en

ICANN: DRAFT PTI and IANA FY21 Operating Plan and Budgets

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

DocumentPurpose
Draft FY21 PTI Operating Plan and BudgetThis 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.

  • Open Date: 14 Oct 2019 23:59 UTC
  • Close Date: 27 Nov 2019 23:59 UTC
  • Staff Report Due: 10 Dec 2019 23:59 UTC

This ICANN announcement was sourced from: https://www.icann.org/public-comments/draft-pti-iana-fy21-op-budget-2019-10-14-en

ICANN: IANA Functions Customer Survey Results Available

IANA logoICANN published the results of an annual survey that measures the perception of satisfaction among Internet Assigned Numbers Authority (IANA) functions customers regarding the services they receive. This survey is the first completed since the ICANN organization affiliate Public Technical Identifiers (PTI) started performing IANA functions on behalf of the ICANN org and accounts for transactions completed between September 2016 and August 2017.

The IANA Services Customer Survey measured satisfaction in relation to documentation quality, process quality, transparency, timeliness, accuracy, reporting, and courtesy. In the 2017 survey, customers identified accuracy as the most important measure of performance for the fifth consecutive year. Notably, 94 percent of respondents reported being satisfied with the accuracy of their transactions. Timeliness and process quality, were identified as the second and third most important measures by customers, both stayed consistent with the previous year with 89 percent satisfaction.

View the IANA Services Customer Satisfaction Survey Report [PDF, 1.33 MB].

While the results of the survey are generally positive, the ICANN org continues to explore opportunities for improvement, including on the survey format and methodology. In response to conversations with key stakeholders within the community, an option to select “not applicable” was added to each question in the survey and open-ended questions were introduced to better capture feedback. There were also improvements to capture the geographical location of the IANA functions customers, and to further segment the top-level domain (TLD) operators.

“Over the years we have refined our approach to surveying our customers, and we’ve received increasing feedback that it can be difficult to recall the details of their PTI interactions up to a year later. This feedback has prompted us to start planning to survey our customers shortly after our interactions, to obtain more timely and actionable feedback,” said Kim Davies, Vice President of IANA and President, PTI.

The ICANN org commissioned Ebiquity, a leading independent marketing and media consultancy, to administer the survey, analyze the results and compile an independent third-party report, to keep with PTI’s goal to improve transparency in its processes. This year, Ebiquity issued 4,070 invitations during the survey period to IANA functions customers — top-level domain operators, regional Internet registries, RFC authors and other protocol parameter registrants, Internet Engineering Steering Group members, DNSSEC KSK trusted community representatives, and .INT domain registrants — and 7 percent responded.

About ICANN

ICANN‘s mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world.

This ICANN announcement was sourced from:
https://www.icann.org/news/announcement-2018-01-18-en

Kim Davies Appointed VP, IANA Functions and President, PTI

ICANN logoICANN announced today [[15 Dec] that Kim Davies, Director of Technical Services, Internet Assigned Numbers Authority (IANA), has been appointed to the position of Vice President, IANA Services and President, PTI.

Public Technical Identifiers (PTI) is responsible for the operational aspects of coordinating the Internet’s unique identifiers and maintaining the trust of the community to provide these services in an unbiased, responsible and effective manner.

Following Elise Gerich’s departure announcement, the ICANN organization, in conjunction with the PTI Board, conducted an extensive and exhaustive search for a replacement. The opening attracted a wide array of applicants, many of which were well qualified.

As VP of IANA Services, Davies will be reporting to the President of ICANN‘s Global Domains Division (GDD), Akram Atallah. “Kim was a natural choice for this position. He has a deep and wide understanding of both IANA and PTI, which he has cultivated during his long tenure as Director of Technical Services,” said Atallah. “I’d also like to extend our gratitude to Elise, who was pivotal in establishing the IANA Department as an example of reliability and customer service.”

In this role, Davies will be responsible for ensuring that the IANA functions are performed in a secure, stable, and efficient manner with a commitment towards operational excellence. As President of PTI, he will also serve as one of the five directors on the PTI Board.

“The IANA team has worked hard to establish themselves as a leader within the technical community,” said Davies. “As we move forward, I want us to focus on continuing to optimize our business process and solidifying the community’s confidence in our ability to deliver on the services we provide.”

Davies will be assuming the role starting 1 January 2018, following Gerich’s official departure from the organization.

Davies joined the organization in 2005, serving as Manager of Root Zone Services and Technical Liaison prior to his role as Director of Technical Services. Prior to joining ICANN, he worked as Technical Policy Advisor at the Council of European National Top Level Domain Registries, and has been involved in various facets of the ICANN community since the mid-1990s.

About ICANN

ICANN‘s mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world.

This ICANN announcement was sourced from:
https://www.icann.org/news/announcement-2017-12-15-en

ICANN Publishes Report of Public Comments on PTI and IANA Draft FY19 Plans

ICANN logoICANN today [14 Dec] published the Report of Public Comments [PDF, 128 KB] on draft FY19 operating and budget plans for Public Technical Identifiers (PTI) and the Internet Assigned Numbers Authority (IANA). This detailed report includes responses to each of the 16 individual comments submitted. The report has been structured by comment theme and is accompanied by a sortable spreadsheet, to make it easier to find related comments and responses.

The PTI Board will consider PTI’s budget at its January 2018 meeting and the ICANN Board will consider IANA‘s budget at its February 2018 meeting.

The Draft FY19 PTI and IANA operating plans and budgets documents are published here.

About ICANN

ICANN‘s mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world.

This ICANN announcement was sourced from:
https://www.icann.org/news/announcement-2-2017-12-14-en

ICANN: Empowered Community Powers Triggered: FY18 Operating Plan and Budget, and Updates to Five-Year Operating Plan

ICANN logoOn 24 June 2017, the ICANN Board adopted ICANN‘s FY18 Operating Plan and Budget, the FY18 IANA Budget, and updates to the Five-Year Operating Plan. Under ICANN‘s post-IANA Stewardship Transition Bylaws, the Empowered Community has the power to consider and, if they choose, to reject these documents before they go into effect.

ICANN‘s FY18 Operating Plan and Budget, the FY18 IANA Budget, and updates to the Five-Year Operating Plan are the result of 11 months of collaborative work by the organization, community, PTI Board, and ICANN Board Finance Committee. They include:

  • Highlights of all ICANN Operations
  • Overview of ICANN‘s FY18 Budget
  • Detailed FY18 Operating Plan
  • Detailed descriptions of portfolios of activities to support the goals and objectives described in the ICANN Strategic Plan for Fiscal Years 2016–2020, and the updated Five-Year Operating Plan
  • Detailed lists of projects for each portfolio, with project-level budgeted costs
  • Summary of changes from the Draft FY18 Operating Plan and Budget

The community’s continuously increasing participation in the planning process is a cornerstone of ICANN‘s transparency and accountability to the global multistakeholder community. ICANN thanks all community members who contributed to the development of the budget. Budget documents for FY18 and previous years are published here.

In accordance with the ICANN Bylaws Annex D, Section 6.2, the Empowered Community now has the opportunity to trigger the following three actions:

  • Rejection of the ICANN FY18 Operating Plan and Budget
  • Rejection of the FY18 IANA Budget
  • Rejection of updates to the Five-Year Operating Plan

Each of these documents will come into effect only after giving the Empowered Community time to consider whether it will raise a petition rejecting the budgets and/or operating plans. Decisional Participants of the Empowered Community have 28 days to bring forth a petition to reject any of these documents.

If the Empowered Community does not raise a petition, both budgets will go into effect on 22 July 2017. In accordance with the ICANN Bylaws Sections 22.4(a)(ix) and 22.4(b)(ix), until the budgets are adopted, including throughout an Empowered Community Petition Process, both IANA and ICANN will operate under separate Caretaker Budgets during the period of FY18.

With the FY18 Caretaker Budget in effect, the ICANN organization will manage with limited operational impact. As noted in the FY18 Operating Plan and Budget, the ICANN FY18 Caretaker Budget prohibits ICANN from posting new positions and reduces travel and professional fees by 10%. The IANA Caretaker Budget is equal to the FY18 IANA Budget to ensure the stability of the IANA functions.

What Is the Empowered Community?

The Empowered Community is the mechanism through which ICANN‘s Supporting Organizations (SOs) and Advisory Committees (ACs) can organize under California law to legally enforce community powers. The community powers and rules that govern the Empowered Community are defined in the ICANN Articles of Incorporation and Bylaws.

Who Can Participate in the Empowered Community?

All of ICANN‘s SOs, as well as the At-Large and Governmental ACs, are Decisional Participants, and can participate in the Empowered Community, including:

  • Address Supporting Organization (ASO)
  • Country Code Names Supporting Organization (ccNSO)
  • Generic Names Supporting Organization (GNSO)
  • At-Large Advisory Committee (ALAC)
  • Governmental Advisory Committee (GAC)

How Does the Empowered Community Use Its powers?

The Empowered Community has an escalation process to reject ICANN‘s FY18 Operating Plan and Budget, the FY18 IANA Budget, and updates to the Five-Year Operating Plan. This escalation process gives SOs and ACs opportunities to discuss solutions with the ICANN Board.

For more information on the Empowered Community, click here.
For more information on ongoing Empowered Community petitions, click here.
For more information on upcoming Empowered Community opportunities, click here.

This page is available in:

This ICANN announcement was sourced from:
https://www.icann.org/news/announcement-2017-06-24-en

Denmark’s Minister of Culture Remarks on the Success of ICANN’s Multistakeholder Model

ICANN58 Copenhagen logo[news release] ICANN‘s 58th public meeting, taking place from 11 to 16 March in Copenhagen, Denmark, has attracted more than 2500 registered participants. The meeting, hosted by the Danish Business Authority and the Danish Internet Forum, is being held six months after the IANA Stewardship Transition, a milestone in the history of ICANN‘s multistakeholder community.

Stakeholders from around the world, including people from businesses, governments, academia, and civil society, have convened in Denmark to discuss various topics such as the next steps after the IANA Stewardship Transition, enhancements to ICANN‘s accountability and the new generic top level domain (gTLD) program.

At the opening ceremony, Denmark’s Minister of Culture, Mette Bock, commented on the IANA Stewardship Transition and ICANN‘s multistakeholder model, stating “The IANA Stewardship Transition only happened because the whole ICANN community, and that is you, was able to work together and to develop proposals that received a very broad support. It was, indeed, a masterpiece and showcase for how the multistakeholder model can function and deliver sustainable results.”

Chairman of DIFO and DK-Hostmaster, Professor Henrik Udsen, also commented on the importance of this model. “Like ICANN, DIFO is based on a multistakeholder model, ensuring that all interest of the Danish Internet society is represented in the continuing efforts to make the .dk zone attractive and security,” said Udsen. “We believe that this multistakeholder model both at a national and international level is a vital component in creating robust solutions to the many challenges we face.”

ICANN‘s President and CEO, Göran Marby, stressed the importance of diversity with respect to the future Internet users, saying “To be able to support the next generation of Internet users, we need to be diverse enough to understand the nodes going forward.”

ICANN Board Chair, Dr. Stephen Crocker, remarked on the importance of working together globally to maintain the Internet. “We’re all different parts of one entity united by a common purpose to help maintain an amazing global network of networks,” said Crocker. “If we do our mission well, we will facilitate communication and the flow of information around the globe, but the only way that we can do that is if we work together and the work that we do together is framed by compassion and respect.”

At the ceremony, ICANN‘s Chief Technology Officer David Conrad announced the launch of a test bed for the upcoming Key Signing Key (KSK) Rollover. “On 11 October 2017, relatively soon, we are going to be changing the root key signing key. Before that time, DNS operators, who have enabled DNSSEC validation, must update their configurations. So what we’re announcing today is a test bed for DNS operators to determine the readiness to support automatic updates..”

ICANN is in the process of performing a Root Zone DNS Security Extensions (DNSSEC) Key Signing Key (KSK) rollover. The KSK is used to cryptographically sign the Zone Signing Key (ZSK), which is used by the Root Zone Maintainer to DNSSEC-sign the root zone of the Internet’s DNS. Maintaining an up-to-date KSK is essential to ensuring DNSSEC-signed domain names continue to validate following the rollover. Internet service providers, enterprise network operators and others who operate DNSSEC validation must update their systems with the public part of the new key signing key.

Those unable to attend ICANN58 in person are highly encouraged to participate remotely. Details for remote participation in any of the sessions can be found here.

Photos of the meeting can be found here.

BACKGROUND: Held three times a year, ICANN‘s public meetings convene members of the global, multistakeholder Internet community, made up of individual users, businesses, civil society, governments, research institutions and non-government organizations, to discuss issues impacting the Domain Name System (DNS) and develop relevant policies.

This ICANN news release was sourced from:
https://www.icann.org/resources/press-material/release-2017-03-13-en