Termination by ICANN. (a) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if EBERO Service Provider fails to cure any fundamental and material breach of EBERO Service Provider’s representations and warranties set forth in Article 1 or obligations set forth in Article 2 within thirty (30) calendar days after ICANN gives EBERO Service Provider notice of such breach, which notice describes with reasonable specificity the details of the alleged breach. (b) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if (i) EBERO Service Provider fails to complete the transition of any Failed TLD in any material respect Event Activation Order, or (ii) EBERO Service Provider fails to comply with any obligations, processes or procedure set forth in the CTP Manual in any material respect. (c) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if EBERO Service Provider refuses to provide EBERO Services for a TLD not previously identified in Exhibit C. (d) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if (i) EBERO Service Provider makes an assignment for the benefit of creditors or similar act, (ii) attachment, garnishment or similar proceedings are commenced against EBERO Service Provider, which proceedings are a material threat to EBERO Service Provider’s ability to provide EBERO Services, and are not dismissed within sixty (60) calendar days of their commencement, (iii) a trustee, receiver, liquidator or equivalent is appointed in place of EBERO Service Provider or maintains control over any of EBERO Service Provider’s property, (iv) execution is levied upon any of EBERO Service Provider’s property, (v) proceedings are instituted by or against EBERO Service Provider under any bankruptcy, insolvency, reorganization or other laws relating to the relief of debtors and such proceedings are not dismissed within thirty
Appears in 3 contracts
Sources: Emergency Back End Registry Operator Agreement, Emergency Back End Registry Operator Agreement, Emergency Back End Registry Operator Agreement
Termination by ICANN. (a) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if EBERO Service Provider fails to cure any fundamental and material breach of EBERO Service Provider’s representations and warranties set forth in Article 1 or obligations set forth in Article 2 Articles 2, 4 or 6 within thirty (30) calendar days after ICANN gives EBERO Service Provider notice of such breach, which notice describes with reasonable specificity the details of the alleged breach.
(b) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if (i) EBERO Service Provider fails to complete the transition of any Failed TLD in any material respect Event Activation Orderrespect, or (ii) EBERO Service Provider fails to comply with any obligations, processes or procedure procedures set forth in the CTP Manual in any material respectrespect with respect to any Failed TLD.
(c) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if EBERO Service Provider refuses to provide EBERO Services for a any Failed TLD not previously identified in Exhibit C.
(d) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if EBERO Service Provider refuses or otherwise fails to agree to incorporate the Additional Data Protection Requirements as required under Section 2.7(e) of the Agreement within 90 days after an Amendment Triggering Event occurred.
(e) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if (i) EBERO Service Provider makes an assignment for the benefit of creditors or similar act, (ii) attachment, garnishment or similar proceedings are commenced against EBERO Service Provider, which proceedings are a material threat to EBERO Service Provider’s ability to provide EBERO Services, and are not dismissed within sixty (60) calendar days of their commencement, (iii) a trustee, receiver, liquidator or equivalent is appointed in place of EBERO Service Provider or maintains control over any of EBERO Service Provider’s property, (iv) execution is levied upon any of EBERO Service Provider’s property, (v) proceedings are instituted by or against EBERO Service Provider under any bankruptcy, insolvency, reorganization or other laws relating to the relief of debtors and such proceedings are not dismissed within thirtysixty
Appears in 3 contracts
Sources: Emergency Back End Registry Operator Agreement, Emergency Back End Registry Operator Agreement, Emergency Back End Registry Operator Agreement
Termination by ICANN. (a) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if EBERO Service Provider fails to cure any fundamental and material breach of EBERO Service Provider’s representations and warranties set forth in Article 1 or obligations set forth in Article 2 Articles 2, 4 or 6 within thirty (30) calendar days after ICANN gives EBERO Service Provider notice of such breach, which notice describes with reasonable specificity the details of the alleged breach.
(b) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if (i) EBERO Service Provider fails to complete the transition of any Failed TLD in any material respect Event Activation Orderrespect, or (ii) EBERO Service Provider fails to comply with any obligations, processes or procedure procedures set forth in the CTP Manual in any material respectrespect with respect to any Failed TLD.
(c) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if EBERO Service Provider refuses or otherwise fails to provide EBERO Services for a TLD not previously identified in Exhibit C.agree to incorporate the Additional Data Protection Requirements as required under Section 2.6(d) of the Agreement within 90 days after an Amendment Triggering Event occurred.
(d) ICANN may, upon notice to EBERO Service Provider, terminate this Agreement and/or any or all Event Activation Orders if (i) EBERO Service Provider makes an assignment for the benefit of creditors or similar act, (ii) attachment, garnishment or similar proceedings are commenced against EBERO Service Provider, which proceedings are a material threat to EBERO Service Provider’s ability to provide EBERO Services, and are not dismissed within sixty (60) calendar days of their commencement, (iii) a trustee, receiver, liquidator or equivalent is appointed in place of EBERO Service Provider or maintains control over any of EBERO Service Provider’s property, (iv) execution is levied upon any of EBERO Service Provider’s property, (v) proceedings are instituted by or against EBERO Service Provider under any bankruptcy, insolvency, reorganization or other laws relating to the relief of debtors and such proceedings are not dismissed within thirtysixty
Appears in 1 contract