Transition-In State. Transition-In describes real, widely visible changes to the behavior of the Internet’s system of unique identifiers. Transition-In is triggered by the order of the Event Director. The Event Director will be advised by ICANN SSR, Compliance, technical liaison, Registrar and Registry Engagement teams, and the EBERO as to the readiness of the zone for transition. Once authorization to proceed is given, the processes should proceed to stable operation without blocking decision points. Declaring an EBERO Event will trigger ICANN processes for communication to registrars and the community; in addition, compliance notifications should be sent. 1 Declare EBERO Event Initial event Event Director 2 Acknowledge Service Order 1 Event Manager 3 3.5.1 Retrieve Zone File and Prepare DNS and DNSSEC for Re-delegation 2 +4 hours EBERO 4 Prepare root zone update request 2 +4 hours ICANN 5 Prepare escrow release order 2 +4 hours ICANN 6 Authorize Transition-In 3,4 Event Director 7 3.5.2 Update Root Zone 6 +4 hours IANA, Root Management Partners 8 3.5.3 Escrow Release 5,6 +24 hours Registry Escrow Agent, ICANN 9 DNS/DNSSEC Operational 7 10 3.5.4 Escrow Release to EBERO 8 +2 hours ICANN, EBERO 11 Acknowledge receipt of escrow release 10 Event Manager
Appears in 3 contracts
Sources: Emergency Back End Registry Operator Agreement, Emergency Back End Registry Operator Agreement, Emergency Back End Registry Operator Agreement
Transition-In State. Transition-In describes real, widely visible changes to the behavior of the Internet’s system of unique identifiers. Transition-In is triggered by the order of the Event Director. The Event Director will be advised by ICANN SSR, Compliance, technical liaison, Registrar and Registry Engagement teams, and the EBERO as to the readiness of the zone for transition. Once authorization to proceed is given, the processes should proceed to stable operation without blocking decision points. Declaring an EBERO Event will trigger ICANN processes for communication to registrars and the community; in addition, compliance notifications should be sent. 1 Declare EBERO Event Initial event Event Director 2 Acknowledge Service Order 1 Event Manager
3 3.5.1 Retrieve Zone File and Prepare DNS and DNSSEC for Re-delegation 2 +4 hours EBERO 4 Prepare root zone update request 2 +4 hours ICANN 5 Prepare escrow release order 2 +4 hours ICANN 6 Authorize Transition-In 3,4 Event Director
7 3.5.2 Update Root Zone 6 +4 hours IANA, Root Management Partners 8 3.5.3 Escrow Release 5,6 +24 hours Registry Escrow Agent, ICANN 9 DNS/DNSSEC Operational 7 10 3.5.4 Escrow Release to EBERO 8 +2 hours ICANN, EBERO 11 Acknowledge receipt of escrow release 10 Event Manager
Appears in 1 contract