Common use of Change in Control; Assignment and Subcontracting Clause in Contracts

Change in Control; Assignment and Subcontracting. Neither party may assign this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. Notwithstanding the foregoing, ICANN may assign this Agreement in conjunction with a reorganization or re-incorporation of ICANN to another nonprofit corporation or similar entity organized in the same legal jurisdiction in which ICANN is currently organized for the same or substantially the same purposes. For purposes of this Section 7.5, a direct or indirect change of control of Registry Operator or any material subcontracting arrangement with respect to the operation of the registry for the TLD shall be deemed an assignment. ICANN shall be deemed to have reasonably withheld its consent to any such a direct or indirect change of control or subcontracting arrangement in the event that ICANN reasonably determines that the person or entity acquiring control of Registry Operator or entering into such subcontracting arrangement (or the ultimate parent entity of such acquiring or subcontracting entity) does not meet the ICANN-adopted registry operator criteria or qualifications then in effect. In addition, without limiting the foregoing, Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any material subcontracting arrangements, and any agreement to subcontract portions of the operations of the TLD must mandate compliance with all covenants, obligations and agreements by Registry Operator hereunder, and Registry Operator shall continue to be bound by such covenants, obligations and agreements. Without limiting the foregoing, Registry Operator must also provide no less than thirty (30) calendar days advance notice to ICANN prior to the consummation of any transaction anticipated to result in a direct or indirect change of control of Registry Operator. Such change of control notification shall include a statement that affirms that the ultimate parent entity of the party acquiring such control meets the ICANN-adopted specification or policy on registry operator criteria then in effect, and affirms that Registry Operator is in compliance with its obligations under this Agreement. Within thirty (30) calendar days of such notification, ICANN may request additional information from Registry Operator establishing compliance with this Agreement, in which case Registry Operator must supply the requested information within fifteen (15) calendar days. If ICANN fails to expressly provide or withhold its consent to any direct or indirect change of control of Registry Operator or any material subcontracting arrangement within thirty (30) (or, if ICANN has requested additional information from Registry Operator as set forth above, sixty (60)) calendar days of the receipt of written notice of such transaction from Registry Operator, ICANN shall be deemed to have consented to such transaction. In connection with any such transaction, Registry Operator shall comply with the Registry Transition Process.

Appears in 3 contracts

Samples: Registry Agreement, Registry Agreement, Registry Agreement

AutoNDA by SimpleDocs

Change in Control; Assignment and Subcontracting. Neither party may assign this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. Notwithstanding the foregoing, ICANN may assign this Agreement in conjunction with a reorganization or re-incorporation of ICANN to another nonprofit corporation or similar entity organized in the same legal jurisdiction in which ICANN is currently organized for the same or substantially the same purposes. For purposes of this Section 7.5, a direct or indirect change of control of Registry Operator or any material subcontracting arrangement with respect to the operation of the registry for the TLD shall be deemed an assignment. ICANN shall be deemed to have reasonably withheld its consent to any such a direct or indirect change of control or subcontracting arrangement in the event that ICANN reasonably determines that the person or entity acquiring control of Registry Operator or entering into such subcontracting arrangement (or the ultimate parent entity of such acquiring or subcontracting entity) does not meet the ICANN-adopted registry operator criteria or qualifications then in effect. In addition, without limiting the foregoing, Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any material subcontracting arrangements, and any agreement to subcontract portions of the operations of the TLD must mandate compliance with all covenants, obligations and agreements by Registry Operator hereunder, and Registry Operator shall continue to be bound by such covenants, obligations and agreements. Without limiting the foregoing, Registry Operator must also provide no less than thirty (30) calendar days advance notice to ICANN prior to the consummation of any transaction anticipated to result in a direct or indirect change of control of Registry Operator. Such change of control notification shall include a statement that affirms that the ultimate parent entity of the party acquiring such control meets the ICANN-adopted specification or policy on registry operator criteria then in effect, and affirms that Registry Operator is in compliance with its obligations under this * Final text will be posted on ICANN website; agreement reference to be replaced by hyperlink. Agreement. Within thirty (30) calendar days of such notification, ICANN may request additional information from Registry Operator establishing compliance with this Agreement, in which case Registry Operator must supply the requested information within fifteen (15) calendar days. If ICANN fails to expressly provide or withhold its consent to any direct or indirect change of control of Registry Operator or any material subcontracting arrangement within thirty (30) (or, if ICANN has requested additional information from Registry Operator as set forth above, sixty (60)) calendar days of the receipt of written notice of such transaction from Registry Operator, ICANN shall be deemed to have consented to such transaction. In connection with any such transaction, Registry Operator shall comply with the Registry Transition Process.

Appears in 1 contract

Samples: Registry Agreement

Change in Control; Assignment and Subcontracting. Neither party may assign this Agreement without the prior written approval of the other party, which approval will not be * Final text will be posted on ICANN website; agreement reference to be replaced by hyperlink. unreasonably withheld. Notwithstanding the foregoing, ICANN may assign this Agreement in conjunction with a reorganization or re-incorporation of ICANN to another nonprofit corporation or similar entity organized in the same legal jurisdiction in which ICANN is currently organized for the same or substantially the same purposes. For purposes of this Section 7.5, a direct or indirect change of ownership or control of Registry Operator or any material subcontracting arrangement with respect to the operation of the registry for the TLD shall be deemed an assignment. ICANN shall be deemed to have reasonably withheld its consent to any such a direct or indirect change of ownership or control or subcontracting arrangement in the event that ICANN reasonably determines that the person or entity acquiring ownership or control of Registry Operator or entering into such subcontracting arrangement (or the ultimate parent entity of such acquiring or subcontracting entity) does not meet the ICANN-adopted registry operator criteria or qualifications then in effect. In addition, without limiting the foregoing, Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any material subcontracting arrangements, and any agreement to subcontract portions of the operations of the TLD must mandate compliance with all covenants, obligations and agreements by Registry Operator hereunder, and Registry Operator shall continue to be bound by such covenants, obligations and agreements. Without limiting the foregoing, Registry Operator must willmust also provide no less than thirty tenthirty (301030) calendar days advance notice to ICANN prior to the consummation of any transaction anticipated to result in a direct or indirect change of ownership or control of Registry Operator. Such change of ownership or control notification shall include a statement that affirms that the ultimate parent entity of the party acquiring such ownership or control meets the ICANN-adopted specification or policy on registry operator criteria then in effect, and affirms that Registry Operator is in compliance with its obligations under this Agreement. Within thirty (30) calendar days of such notification, ICANN may request additional information from Registry Operator establishing compliance with this Agreement, in which case Registry Operator must supply the requested information within fifteen (15) calendar days. If ICANN fails to expressly provide or withhold its consent to any direct or indirect change of control of Registry Operator or any material subcontracting arrangement within thirty (30) (or, if ICANN has requested additional information from Registry Operator as set forth above, sixty (60)) calendar days of the receipt of written notice of such transaction from Registry Operator, ICANN shall be deemed to have consented to such transaction. In connection with any such transaction, Registry Operator shall comply with the Registry Transition Process.

Appears in 1 contract

Samples: Registry Agreement

Change in Control; Assignment and Subcontracting. Neither party may assign this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. Notwithstanding the foregoing, ICANN may assign this Agreement in conjunction with a reorganization or re-incorporation of ICANN to another nonprofit corporation or similar entity organized in the same legal jurisdiction in which * Final text will be posted on ICANN is currently organized website; agreement reference to be replaced by hyperlink. for the same or substantially the same purposes. For purposes of this Section 7.5, a direct or indirect change of ownership or control of Registry Operator or any material subcontracting arrangement with respect to the operation of the registry for the TLD shall be deemed an assignment. ICANN shall be deemed to have reasonably withheld its consent to any such a direct or indirect change of ownership or control or subcontracting arrangement in the event that ICANN reasonably determines that the person or entity acquiring ownership or control of Registry Operator or entering into such subcontracting arrangement (or the ultimate parent entity of such acquiring or subcontracting entity) does not meet the ICANN-adopted registry operator criteria or qualifications then in effect. In addition, without limiting the foregoing, Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any material subcontracting arrangements, and any agreement to subcontract portions of the operations of the TLD must mandate compliance with all covenants, obligations and agreements by Registry Operator hereunder, and Registry Operator shall continue to be bound by such covenants, obligations and agreements. Without limiting the foregoing, Registry Operator must also provide no less than thirty (30) calendar days advance notice to ICANN prior to the consummation of any transaction anticipated to result in a direct or indirect change of ownership or control of Registry Operator. Such change of ownership or control notification shall include a statement that affirms that the ultimate parent entity of the party acquiring such ownership or control meets the ICANN-adopted specification or policy on registry operator criteria then in effect, and affirms that Registry Operator is in compliance with its obligations under this Agreement. Within thirty (30) calendar days of such notification, ICANN may request additional information from Registry Operator establishing compliance with this Agreement, in which case Registry Operator must supply the requested information within fifteen (15) calendar days. If ICANN fails to expressly provide or withhold its consent to any direct or indirect change of control of Registry Operator or any material subcontracting arrangement within thirty (30) (or, if ICANN has requested additional information from Registry Operator as set forth above, sixty (60)) calendar days of the receipt of written notice of such transaction from Registry Operator, ICANN shall be deemed to have consented to such transaction. In connection with any such transaction, Registry Operator shall comply with the Registry Transition Process.

Appears in 1 contract

Samples: Registry Agreement

AutoNDA by SimpleDocs

Change in Control; Assignment and Subcontracting. Neither party may assign this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. Notwithstanding the foregoing, ICANN may assign this Agreement in conjunction with a reorganization or re-incorporation of ICANN to another nonprofit corporation or similar entity organized in the same legal jurisdiction in which ICANN is currently organized for the same or substantially the same purposes. For purposes of this Section 7.5, a direct or indirect change of control of Registry Operator or any material subcontracting arrangement with respect to the operation of the registry for the TLD shall be deemed an assignment. ICANN shall be deemed to have reasonably withheld its consent to any such a direct or indirect change of control or subcontracting arrangement in the event that ICANN reasonably determines that the person or entity acquiring control of Registry Operator or entering into such subcontracting arrangement (or the ultimate parent entity of such acquiring or subcontracting entity) does not meet the ICANN-adopted registry operator criteria or qualifications then in effect. In addition, without limiting the foregoing, Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any material subcontracting arrangements, and any agreement to subcontract portions of the operations of the TLD must mandate compliance with all covenants, obligations and agreements by Registry Operator hereunder, and Registry Operator shall continue to be bound by such covenants, obligations and agreements. Without limiting the foregoing, Registry Operator must also provide no less than thirty (30) calendar days advance notice to ICANN prior to the consummation of any transaction anticipated to result in a direct or indirect change of control of Registry Operator. Such change of control notification shall include a statement that affirms that the ultimate parent entity of the party acquiring such control meets the ICANN-adopted specification or policy on registry operator criteria then in effect, and affirms that Registry Operator is in compliance with its obligations under this Agreement. Within thirty (30) calendar days of such notification, ICANN may request additional information from Registry Operator establishing compliance with this Agreement, in which case Registry Operator must supply the requested information within fifteen (15) calendar days. If ICANN fails to expressly provide or withhold its consent to any direct or indirect change of control of Registry Operator or any material subcontracting arrangement within thirty (30) (or, if ICANN has requested additional information from Registry Operator as set forth above, sixty (60)) calendar days of the receipt of written notice of such transaction from Registry Operator, ICANN shall be deemed to have consented to such * Final text will be posted on ICANN website; agreement reference to be replaced by hyperlink. transaction. In connection with any such transaction, Registry Operator shall comply with the Registry Transition Process.

Appears in 1 contract

Samples: Registry Agreement

Change in Control; Assignment and Subcontracting. Neither party may assign this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. Notwithstanding the foregoing, ICANN may assign this Agreement in conjunction with a reorganization or re-incorporation of ICANN to another nonprofit corporation or similar entity organized in the same legal jurisdiction in which ICANN is currently organized for the same or substantially the same purposes. For purposes of this Section 7.5, a direct or indirect change of ownership or control of Registry Operator or any material subcontracting arrangement with respect to the operation of the registry for the TLD shall be deemed an assignment. ICANN shall be deemed to have reasonably withheld its consent to any such a direct or indirect change of ownership or control or subcontracting arrangement in the event that ICANN reasonably determines that the person or entity acquiring ownership or control of Registry Operator or entering into such subcontracting arrangement (or the ultimate parent entity of such acquiring or subcontracting entity) does not meet the ICANN-adopted registry operator criteria or qualifications then in effect. In addition, without limiting the foregoing, Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any material subcontracting arrangements, and any agreement to subcontract portions of the operations of the TLD must mandate compliance with all covenants, obligations and agreements by Registry Operator hereunder, and Registry Operator shall continue to be bound by such covenants, obligations and agreements. Without limiting the foregoing, Registry Operator must also provide no less than thirty (30) calendar days advance notice to ICANN prior to the consummation of any transaction anticipated to result in a direct or indirect change of ownership or control of Registry Operator. Such change of ownership or control notification shall include a statement that affirms that the ultimate parent entity of the party acquiring such ownership or control meets the ICANN-adopted specification or policy on registry operator criteria then in effect, and affirms that Registry Operator is in compliance with its obligations under this Agreement. Within thirty (30) calendar days of such notification, ICANN may request additional information from Registry Operator establishing compliance with this Agreement, in which case Registry Operator must supply the requested information within fifteen (15) calendar days. If ICANN fails to expressly provide or withhold its consent to any direct or indirect change of control of Registry Operator or any material subcontracting arrangement within thirty (30) (or, if ICANN has requested additional information from Registry Operator as set forth above, sixty (60)) calendar days of the receipt of written notice of such transaction from Registry Operator, ICANN shall be deemed to have consented to such transaction. In connection with any such transaction, Registry Operator shall comply with the Registry Transition Process.

Appears in 1 contract

Samples: Registry Agreement

Time is Money Join Law Insider Premium to draft better contracts faster.