Historical Resolution Tracking Feature » Emergency Back-End Registry Operator Program (EBERO) Contracts Approval

Important note: The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.

Emergency Back-End Registry Operator Program (EBERO) Contracts Approval


Resolution of the ICANN Board
Meeting Date: 
Sun, 23 Jun 2019
Resolution Number: 
2019.06.23.02 – 2019.06.23.03
Resolution Text: 

Whereas, in conjunction with the community-designed New gTLD Program, the ICANN org developed the Emergency Back-End Registry Operator (EBERO) program, providing for a temporary transition process for registry operators at risk of failing to sustain any of the five critical registry functions.

Whereas, in September 2011, ICANN org published its initial Request for Information and the EBERO program has been in operation since September 2013.

Whereas, ICANN org published a Request for Proposal in October 2018 to identify Emergency Back-end Registry Operators to meet the updated needs of the EBERO program.

Whereas, the ICANN org evaluated the Request for Proposal and determined a short-list of bidders have demonstrated its capability to support the EBERO program.

Whereas, the Board Finance Committee considered the costs of the proposed EBERO program contracts and recommended Board approval.

Resolved (2019.06.23.02), the Board authorizes the President and CEO, or his designee(s), to enter into, and make disbursements in furtherance of, multiple contracts for terms of at least 60 months with total costs not to exceed [REDACTED FOR NEGOTIATION PURPOSES].

Resolved (2019.06.23.03), specific items within this resolution shall remain confidential for negotiation purposes pursuant to Article 3, Sections 3.5(b) and (d) of the ICANN Bylaws until the President and CEO determines that the confidential information may be released.

Rationale for Resolution: 

The ICANN Global Domains Division understands that since the original Request for Information in 2011, the industry has significantly matured and there is a need to better align existing registry operator requirements to an EBERO provider as well as gain efficiencies in the process, while offering geographic diversity. ICANN org issued a request for proposal on 17 October 2018 to identify one or more providers capable to service the EBERO program. ICANN org intended to find providers in regions where the largest number of gTLD registries are currently based — the Asia Pacific, European, and North American regions.

As a result, ICANN org identified several bidders that have a clear understanding of the work involved, and the capability and infrastructure to perform at the appropriate service levels. In addition, these providers understand the current industry and ICANN's multistakeholder model.

Taking this step towards contracting is in fulfilment of ICANN's mission and in the public interest to ensure that ICANN org is utilizing the right third-party providers, and to ensure that it is maximizing available resources in a cost-efficient and effective manner. This action will benefit ICANN's mission to ensure the security, stability and resiliency of the domain name system.

This action will have a fiscal impact on the organization as each EBERO results in an additional fixed cost. The EBEROs provide ICANN org greater geographic diversity of available service providers while achieving a more competitive pricing model. Currently, ICANN pays [REDACTED FOR NEGOTIATION PURPOSES] for three EBERO providers over five years. The selection of providers through the RFP process will result in a savings of approximately 30%, while also achieving an increased level of technical support for the EBERO program.

This is an Organizational Administrative Function for which no public comment was necessary.