Emergency Back-End Registry Operator: Difference between revisions
No edit summary |
m added Category:Backend Registries using HotCat |
||
| (One intermediate revision by one other user not shown) | |||
| Line 15: | Line 15: | ||
==Selection Process== | ==Selection Process== | ||
The initial application | The initial application process began on 2011 September, when ICANN called for a Request for Information (RFI), and providers from around the world submitted their responses. ICANN received 14 RFI responses and underwent an extensive and detailed process, wherein the respondents had to demonstrate the ways in which their organizations met all necessary requirements. Geographic location also played a role in the selection process.<ref name="ebero"></ref> | ||
The three selected organizations met stringent technical requirements and demonstrated years of experience in operating domain name services, registration data directory services and extensible provisioning protocol services.<ref name="icann"></ref> | The three selected organizations met stringent technical requirements and demonstrated years of experience in operating domain name services, registration data directory services and extensible provisioning protocol services.<ref name="icann"></ref> | ||
==References== | ==References== | ||
[[Category:Backend Registries]] | |||
Latest revision as of 15:26, 18 July 2022
Emergency Back-End Registry Operators, or EBEROs, are organizations under three-to-five-year contracts with ICANN to provide critical registry functions, in the event of a TLD registry operator failure. As of 2016 April, the currently contracted EBERO service providers are China Internet Network Information Center (CNNIC), CORE Internet Council of Registrars, and Nominet.[1]
EBEROs were first activated in Q4 2013.[1]
Usage & Services[edit | edit source]
EBEROs are only activated if a registry operator fails to provide or is unable to sustain five critical registry functions, or in the case of a transition from one registry operator to another. However, EBEROs have limited capabilities. They maintain critical registry functions but are not authorized to offer additional services a TLD operator may have offered its customers, such as web hosting or networks analytics.[2]
The critical functions covered by EBEROs are:[2]
- DNS resolution for registered domain names
- Operation of Shared Registration System
- Provision of WHOIS service
- Registry data escrow deposits
- Maintenance of a properly signed zone in accordance with DNSSEC requirements
Selection Process[edit | edit source]
The initial application process began on 2011 September, when ICANN called for a Request for Information (RFI), and providers from around the world submitted their responses. ICANN received 14 RFI responses and underwent an extensive and detailed process, wherein the respondents had to demonstrate the ways in which their organizations met all necessary requirements. Geographic location also played a role in the selection process.[1]
The three selected organizations met stringent technical requirements and demonstrated years of experience in operating domain name services, registration data directory services and extensible provisioning protocol services.[2]
References[edit | edit source]
- ↑ 1.0 1.1 1.2 FAQ About Emergency Back-end Registry Operators, ICANN.org. Retrieved 2016 April 17.
- ↑ 2.0 2.1 2.2 ICANN Names Back-up Registry Operators for New gTLDs, ICANN.org. Published 2013 April 2. Retrieved 2016 April 17.