EBERO Services Clause Samples
The EBERO Services clause defines the responsibilities and procedures for an Emergency Back-End Registry Operator (EBERO) to step in and maintain critical registry functions if the primary operator fails to do so. This typically involves the EBERO taking over essential services such as domain name resolution, data escrow, and DNS management to ensure continuity of operations. By establishing a clear framework for emergency intervention, the clause ensures that domain registries remain operational and secure, protecting registrants and the stability of the domain name system in the event of a registry failure.
EBERO Services. In the event ICANN declares an emergency event (“EBERO Event”) and ICANN designates EBERO Service Provider as the EBERO for such Failed TLD in an Event Activation Order, EBERO Service Provider shall provide the following back---end registry functions in respect of that Failed TLD: DNS, DNSSEC, RDDS, SRS/EPP, and will execute Data Escrow registry deposits and support services (including, without limitation, those in Sections 3.7 and 3.8 of the CTP ▇▇▇▇▇▇), all as provided hereunder and in the CTP Manual (collectively all such functions and services shall be referred to herein as the “EBERO Services”). The EBERO Services shall be provided and implemented in the manner specified in Section 11 of the CTP Manual.
EBERO Services. In the event a registry operator for a TLD in the New gTLD Program is temporarily unable to perform certain critical functions and ICANN declares an emergency event (“Emergency Event”), EBERO Service Provider shall provide the following back-‐end registry functions in respect of that Failed TLD registry when requested by ICANN in an Event Activation Order: DNS, DNSSEC, Whois, SRS/EPP, and Data Escrow registry services (collectively, the “EBERO Services”). The EBERO Services shall be provided and implemented in the manner specified in the Section 11 of the CTP Manual. ICANN shall be responsible for providing the centralized zone file to the EBERO Service Provider.
EBERO Services. In the event ICANN declares an emergency event (“EBERO Event”) and EBERO Service Provider is designated as the EBERO for such Failed TLD by accepting an Event Activation Order:
(a) EBERO Service Provider shall provide the following back---end registry functions in respect of that Failed TLD: DNS, DNSSEC, RDDS, SRS/EPP, and will execute Data Escrow registry deposits and support services (including, without limitation, those in Sections 3.7 and 3.8 of the CTP ▇▇▇▇▇▇), all as provided hereunder and in the CTP Manual (collectively all such functions and services shall be referred to herein as the “EBERO Services”). The EBERO Services shall be provided and implemented in the manner specified in Section 11 of the CTP Manual.
(b) EBERO Service Provider shall have at least two Anycast networks to distribute the DNS service in respect of that Failed TLD, provided that at least one of these Anycast networks shall be managed by a third party that is not an Affiliate (as defined in Section 6.12)
