Modifications and Updates to the Wire Center List and Subsequent Transition Periods 5.4.6.1 In the event AT&T identifies additional wire centers that meet the criteria set forth in Sections 5.4.2.1 or 5.4.2.2 above, but that were not included in the Master List of Unimpaired Wire Centers or AT&T’s List of Unimpaired Wire Centers, AT&T shall include such additional wire centers in a CNL. Each such list of additional wire centers shall be considered a Subsequent Wire Center List. AT&T will follow any limitations on the frequency with which it may issue such lists and notification procedures set forth in applicable Commission orders.
5.4.6.2 TWTC shall have thirty (30) business days to dispute the additional wire centers listed on AT&T’s CNL. Absent such dispute, effective thirty (30) business days after the date of a AT&T CNL providing a Subsequent Wire Center List, AT&T shall not be required to provide DS1 and DS3 Dedicated Transport, as applicable, in such additional wire center(s), except pursuant to the self-certification process as set forth in Section 1.9.1 of this Attachment.
5.4.6.3 For purposes of Section 5.4.6.1 above, AT&T shall make available DS1 and DS3 Dedicated Transport that were in service for TWTC in a wire center on the Subsequent Wire Center List as of the thirtieth (30th) business day after the date of AT&T’s CNL identifying the Subsequent Wire Center List (Subsequent Embedded Base) until one hundred eighty (180) days after the thirtieth (30th) business day Version: 4Q06 Standard ICA 11/30/06 from the date of AT&T’s CNL identifying the Subsequent Wire Center List (Subsequent Transition Period).
5.4.6.4 The rates set forth in Exhibit B shall apply to the Subsequent Embedded Base during the Subsequent Transition Period.
5.4.6.5 No later than one hundred eighty (180) days from AT&T’s CNL identifying the Subsequent Wire Center List, TWTC shall submit an LSR(s) or spreadsheet(s) as applicable, identifying the Subsequent Embedded Base of circuits to be disconnected or converted to other AT&T services.
5.4.6.5.1 In the case of disconnection, the applicable disconnect charges set forth in this Agreement shall apply.
5.4.6.5.2 If TWTC chooses to convert DS1 and/or DS3 Dedicated Transport to special access circuits in existence as of the Effective Date of this Agreement, AT&T will include such DS1 and/or DS3 Dedicated Transport within TWTC’s total special access circuits, and apply any discounts to which TWTC is entitled from the transition period of 3/11/2006 to the conversion date. Conversions will be subject to the switch-as-is charge set forth in Exhibit A to this Attachment 2.
5.4.6.5.3 AT&T shall not impose disconnect or nonrecurring installation charges when transitioning the Subsequent Embedded Base of DS1 and DS3 Dedicated Transport in existence as of the Effective Date of this Agreement.
5.4.6.6 If TWTC fails to submit the LSR(s) or spreadsheet(s) for all of its Subsequent Embedded Base by one hundred eighty (180) days after the date of AT&T’s CNL identifying the Subsequent Wire Center List, AT&T will identify TWTC’s remaining Subsequent Embedded Base, if any, and will transition such circuits to the equivalent tariffed AT&T service(s), or in the case of Georgia, to the equivalent 271 service(s) set forth in Exhibit 1. In the states of Florida, Kentucky, Mississippi and South Carolina, those circuits identified and transitioned by AT&T shall be subject to the applicable disconnect charges as set forth in this Agreement and the full nonrecurring charges for installation of the equivalent tariffed AT&T service as set forth in AT&T’s tariffs. In the states of Alabama, Georgia, North Carolina and Tennessee, those circuits identified and transitioned by AT&T shall be subject to the applicable switch-as-is rates set forth in Exhibit A of Attachment
Change of Control; Assignment and Subcontracting Except as set forth in this Section 7.5, neither party may assign any of its rights and obligations under this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. For purposes of this Section 7.5, a direct or indirect change of control of Registry Operator or any subcontracting arrangement that relates to any Critical Function (as identified in Section 6 of Specification 10) for the TLD (a “Material Subcontracting Arrangement”) shall be deemed an assignment.
(a) Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any assignment or Material Subcontracting Arrangement, and any agreement to assign or subcontract any portion of the operations of the TLD (whether or not a Material Subcontracting Arrangement) 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. 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.
(b) Within thirty (30) calendar days of either such notification pursuant to Section 7.5(a), ICANN may request additional information from Registry Operator establishing (i) compliance with this Agreement and (ii) that the party acquiring such control or entering into such assignment or Material Subcontracting Arrangement (in any case, the “Contracting Party”) and the ultimate parent entity of the Contracting Party meets the ICANN-‐adopted specification or policy on registry operator criteria then in effect (including with respect to financial resources and operational and technical capabilities), in which case Registry Operator must supply the requested information within fifteen (15) calendar days.
(c) Registry Operator agrees that ICANN’s consent to any assignment, change of control or Material Subcontracting Arrangement will also be subject to background checks on any proposed Contracting Party (and such Contracting Party’s Affiliates).
(d) If ICANN fails to expressly provide or withhold its consent to any assignment, direct or indirect change of control of Registry Operator or any Material Subcontracting Arrangement within thirty (30) calendar days of ICANN’s receipt of notice of such transaction (or, if ICANN has requested additional information from Registry Operator as set forth above, thirty (30) calendar days of the receipt of all requested written information regarding such transaction) from Registry Operator, ICANN shall be deemed to have consented to such transaction.
(e) In connection with any such assignment, change of control or Material Subcontracting Arrangement, Registry Operator shall comply with the Registry Transition Process.
(f) Notwithstanding the foregoing, (i) any consummated change of control shall not be voidable by ICANN; provided, however, that, if ICANN reasonably determines to withhold its consent to such transaction, ICANN may terminate this Agreement pursuant to Section 4.3(g), (ii) ICANN may assign this Agreement without the consent of Registry Operator upon approval of the ICANN Board of Directors in conjunction with a reorganization, reconstitution or re-‐incorporation of ICANN upon such assignee’s express assumption of the terms and conditions of this Agreement, (iii) Registry Operator may assign this Agreement without the consent of ICANN directly to a wholly-‐owned subsidiary of Registry Operator, or, if Registry Operator is a wholly-‐owned subsidiary, to its direct parent or to another wholly-‐owned subsidiary of its direct parent, upon such subsidiary’s or parent’s, as applicable, express assumption of the terms and conditions of this Agreement, and (iv) ICANN shall be deemed to have consented to any assignment, Material Subcontracting Arrangement or change of control transaction in which the Contracting Party is an existing operator of a generic top-‐level domain pursuant to a registry agreement between such Contracting Party and ICANN (provided that such Contracting Party is then in compliance with the terms and conditions of such registry agreement in all material respects), unless ICANN provides to Registry Operator a written objection to such transaction within ten (10) calendar days of ICANN’s receipt of notice of such transaction pursuant to this Section 7.5. Notwithstanding Section 7.5(a), in the event an assignment is made pursuant to clauses (ii) or (iii) of this Section 7.5(f), the assigning party will provide the other party with prompt notice following any such assignment.
