Common use of Generate Transition Clause in Contracts

Generate Transition. Out Data This step only applies to Successor Operators that are not the EBERO. The EBERO will use the data escrow deposit format to provide the necessary data for a Transition-Out. In addition to the current status (as described in an escrow deposit) of the transitioned registry, the EBERO should be expected to provide copies of the original escrow deposits and zone file that it used to perform the Transition-In, as well as a copy of the first full escrow deposit representing the EBERO’s initial state. Because only the EBERO can authoritatively state what data was used by the EBERO, the EBERO will be the source of data to the Successor Operator; however, duplicate data may also be provided by ICANN. Data Type Provided by EBERO to Successor Operator Provided by ICANN to Successor Operator Released Escrow deposit from originating registry Yes Yes Zone file used for Transition-In Yes Yes Report of discrepancies and how they were handled during Transition-In Yes Yes Initial Escrow-formatted status of registry taken when Transition-In was completed Yes No Escrow-formatted current status of registry at time of Transition-Out Yes No Data Type Provided by EBERO to Successor Operator Provided by ICANN to Successor Operator Read-only access to EBERO SRS for a period of no less than 30 days Yes No Copy of each manual change request made by ICANN to the EBERO No Yes Log of detailed transform transactions on a specific domain name for a period of no less than 30 days for any domain name associated with a discrepancy during Transition-In or subject to any manual change requested by ICANN. Figure 13: Data Sources for Transition-Out Yes No

Generate Transition. Out Data Data‌ This step only applies to Successor Operators successor registries that are not the EBERO. The EBERO will use the data escrow deposit format to provide the necessary data for a an EBERO Transition-Out. In addition to the current status (as described in an escrow deposit) of the transitioned registry, the EBERO should be expected to provide copies of the original escrow deposits and zone file that it used to perform the Transition-In, as well as a copy of the first full escrow deposit representing the EBERO’s initial state. Because only the EBERO can authoritatively state what data was used by the EBERO, the EBERO will it must be the source of data to the Successor Operatorreceiving registry; however, duplicate data may also be provided by ICANN. Data Type Provided by EBERO to Successor Operator receiving registry Provided by ICANN to Successor Operator receiving registry Released Escrow deposit from originating registry Yes Yes Zone file used for Transition-In Yes Yes Report of discrepancies and how they were handled during Transition-In Yes Yes Initial Escrow-formatted status of registry taken when Transition-Transition- In was completed Yes No Escrow-formatted current status of registry at time of Transition-Transition- Out Yes No Data Type Provided by EBERO to Successor Operator Provided by ICANN to Successor Operator Read-only access to EBERO SRS for a period of no less than 30 days Yes No Copy of each manual change request made by ICANN to the EBERO No Yes Log of detailed transform transactions on a specific domain name for a period of no less than 30 days for any domain name associated with a discrepancy during Transition-In or subject to any manual change requested by ICANN. Yes No Figure 1312: Data Sources for Transition-Out Yes NoOut