Archive for ICANN Meeting

Report on Public Comments on Draft FY17 Operating Plan and Budget and Five-Year Operating Plan Update Now Available

ICANN has published its report on public comments [PDF, 1.83 MB] for the draft plans for FY17, including an update to its Five-Year Operating Plan.

The development process has included a 57-day public comment period, 35 days of response drafting, and several public calls held to review the comments received in-depth. ICANN has published a detailed report to respond to over 150 separate comments from 12 community groups and people. This is an increase of over 80% on the number of comments received for the draft FY16 plans.

The publication date for the report was changed from 31 May 2016 to 6 June 2016 so that ICANN was able to develop full responses to the comments provided. The report has been structured thematically and is accompanied by a sortable spreadsheet, to help readers find the comments and responses they are most interested in.

The budget is scheduled for adoption when the ICANN Board meets during ICANN56 in Helsinki.

The Chairman’s Blog: An Update From the May 2016 Board Workshop in Amsterdam

Three times a year, between ICANN meetings, the ICANN Board meets in a workshop format. During these intensive workshops, the Board, supported by senior ICANN team members, comes together for in-depth consideration of important and timely ICANN issues. On behalf of the Board, Markus Kummer and George Sadowsky report on our recent meeting, 13-15 May in Amsterdam.

This meeting took place at a critical time for ICANN and the Board. We welcomed our incoming CEO and President Göran Marby to his first workshop, as well as Becky Burr, our Board member-in-waiting who is taking over Bruce Tonkin’s seat at the end of ICANN57 in October. We were delighted to have them both with us.

As you can imagine, we focused on topics related to the IANA Stewardship Transition. We received an update from ICANN management on the status of the transition and all its various parts – including the status of implementation pre-planning for Post Transition IANA (PTI) and the contracts and Service Level Agreements (SLA) with our partners.

We devoted one session to understanding the new Bylaws and the public comments received thus far. We’ve been paying careful attention to this critical area, to ensure that the Board is ready to vote on them after the Public Comment closes.

While we focused on the elements leading up the transition, we also devoted time to understanding the work of the organization post-transition. How does the transition affect what we do and how we do it? How do we bring the core values into ICANN and the organization? How do we communicate and engage differently as a post-transition ICANN? This is part of an ongoing discussion that the Board takes seriously – it’s our responsibility to make sure we, and the organization, are ready for the future.

As part of looking to the future, we asked Göran to share his early observations about the organization, as well as his initial approach, priorities and plans. While we will leave it to Göran to talk about this once he formally takes over later this month, this discussion led us to think about the various roles and responsibilities of the ICANN Board, ICANN management, and the ICANN community in a post-Transition world. We also talked about ways to structure Board-CEO communications, to best serve the organization and the community going forward.

We’ve all been talking about trust lately, and the workshop gave the Board an opportunity to take a hard look at what we can do to build trust between ICANN as an organization and all of its stakeholders. This is also an ongoing discussion, and one that we all have a stake in. During the workshop, we considered concrete steps that the Board could take to increase our transparency and accountability. We agreed to post the transcripts and/or recordings of our deliberative sessions and, as a result of this discussion, passed a resolution asking Göran and his team to develop a plan for the implementation of this new procedure, also making sure that we respect confidentiality, as necessary. We know there is a lot of interest in our meetings and discussions, and we look forward to reviewing Göran’s proposal in Helsinki.

In addition to a detailed review of the Draft FY17 Budget, we discussed the status of KSK Rollover planning and the planning underway to anticipate and mitigate associated risks. We discussed the current efforts to update ICANN’s Expected Standards of Behavior, and also looked at the Draft Framework of Principles for Cross Community Working Groups.

Our agenda for this Workshop was ambitious, and we didn’t get to everything on the agenda. For example, we had planned to discuss ICANN’s volunteer model, including the volunteer pool, volunteer fatigue, and ways to help our growing community work together more effectively. We will pick this up at our next opportunity.

We also held a formal Board meeting (you can find the formal details on our Board page) and a range of Committee meetings, from Audit, Risk and Finance to Governance and Organizational Effectiveness. The Board meeting included a lengthy discussion about the location of ICANN57 and the challenges we all saw in staying and in relocating. Akram sums up our collective feelings well in his blog. We are all very sorry not to be going to Puerto Rico this October, but are very much look forward to getting back there soon.

ICANN 53 To Be Held in Buenos Aires

According to the news from 1(1)on December 9th,the Internet Corporation for Assigned Names and Numbers (ICANN) has recently picked Buenos Aires for its 53rd meeting.

Buenos Aires, Argentina was approved for ICANN’s 53rd meeting by the ICANN Board last week.

The meeting will be held 21-25 June,2015 .The venue has not yet been disclosed. However, ICANN may return to a previous venue, the Sheraton Hotel.

This is the third time the Internet Corporation for Assigned Names and Numbers (ICANN) has chosen Buenos Aires for one of its public meetings. The first meeting held in Buenos Aires was held in 2005 and the second one was held last year.


Initial Evaluation Results Released for First Set of Applications

From ICANN,22 March 2013

Today marks a major milestone in the New gTLD Program: Initial Evaluation (IE) results for the first set of newgTLD applications have been released to applicants and the general public.

This achievement is the result of many years of policy development and implementation work to bring diversity, competition, and innovation to the Domain Name System. Applicants, along with the greater ICANN community have dedicated countless hours toward reaching this goal. This is not only an important and exciting moment in the New gTLD Program but also in the continuing evolution of the Internet.

To view Initial Evaluation results for applications with priority numbers 1 through 30, go to the Current Application Status page of the new gTLD microsite. Results are posted under the IE Results column. Clicking on the result will take you to the Initial Evaluation report for that application.

There are three possible outcomes of Initial Evaluation: Pass, Eligible for Extended Evaluation, or Ineligible for Further Review.

  • Pass – The evaluation panels determined that the application is consistent with the requirements in the Applicant Guidebook and can advance to the next phase of the Program.
  • Eligible for Extended Evaluation – The Financial, Technical/Operational, Registry Services, or Geographic Names evaluation panels determined that the application did not provide sufficient information to award a passing score. The application is eligible for extended evaluation.
  • Ineligible for Further Review – The DNS Stability, String Similarity, Background Screening, and/or Geographic Names evaluation panels determined that the application did not meet the relevant criteria in the Applicant Guidebook, and the application is ineligible for further review.

For some applications Initial Evaluation results were not yet available for one or more possible reasons such as: pending change requests, clarifying questions, or follow-up with applicants regarding missing information. The results for these applications will be published as soon as the relevant processes are completed.

As communicated previously, ICANN is releasing Initial Evaluation results in priority order, in increments of 30 per week, with plans to increase to 100 per week. ICANN anticipates having Initial Evaluation results for all applications published by the end of August 2013.

Next Steps

Applications that pass Initial Evaluation (and that do not face any objections or string contention) will be eligible to proceed to contracting, with execution of the Registry Agreement as early as 23 April 2013.

Visit the New gTLD microsite to stay up-to-date on the latest Initial Evaluation releases and news about the Program.

Implementation of Expired Registration Recovery Policy

from ICANN, 28 February 2013

ICANN is pleased to announce the implementation of the Expired Registration Recovery Policy (“ERRP”). This policy was developed from the Generic Name Supporting Organization (“GNSO“)’s Post Expiration Domain Name Recovery (“PEDNR“) recommendations, which were adopted by ICANN‘s Board of Directors on 28 October 2011. The policy was drafted in consultation with the GNSO‘s PEDNR Implementation Review Team and was posted for public comment on 11 October 2012.

The ERRP is expected to promote better understanding of registrants’ options and help alleviate common issues related to the expiration of gTLD registrations. This policy is intended to help align registrant expectations with registrar practices by establishing certain minimum communications requirements and making renewal and redemption of domain name registrations uniformly available in prescribed circumstances.

Some of the most notable provisions of the ERRP include the following i:

  1. To help prevent unintended non-renewal of domain name registrations, registrars will be required to notify registered name holders of the expiration of their registrations at least two times: approximately one month prior to the expiration date and, again, approximately one week prior to the expiration date.
  2. All gTLD registries must offer a Redemption Grace Period of 30 days immediately following the deletion of a registration. (Sponsored gTLDs are exempt, and not required to offer a Redemption Grace Period.) During the Redemption Grace Period, the registrant must be permitted by its registrar to restore the deleted registration.
  3. To promote consumer choice and awareness, registrars must make their renewal and redemption fees reasonably available to registered name holders and prospective registered name holders at the time of registration of a domain name.
  4. As in the past, registrars may delete registrations at any time after they expire, subject to applicable consensus policies and provisions of the Registrar Accreditation Agreement. However, the ERRP requires that resolution of the domain name be interrupted for a period of time after expiration, but before deletion, of the name to help make the registrant aware of the expiration of its name. Additionally, any parking page hosted by the registrar at the expired domain name must include or point to renewal instructions.

All ICANN-accredited registrars and gTLD registries are required to comply with the Expired Registration Recovery Policy by no later than 31 August 2013.

Consistent with the recommendations of the GNSO‘s PEDNR Working Group, ICANN is in the process of developing educational materials in consultation with interested stakeholders to help the community better understand this policy and how it applies to them.

A link to the ERRP can be found here:

Welcome to Beijing

Welcome to Beijing