Porcupine Site Highway 11 and the City of Timmins Thunder Bay and District Toronto/York-Peel
Return or Destruction Upon termination of this Agreement or upon any earlier written request by Sponsor at any time, Institution shall return to Sponsor, or destroy, at Sponsor’s option, all Confidential Information other than Study Data.
No Release; Return or Destruction Each Party agrees not to release or disclose, or permit to be released or disclosed, any information addressed in Section 6.9(a) to any other Person, except its Representatives who need to know such information in their capacities as such (who shall be advised of their obligations hereunder with respect to such information), and except in compliance with Section 6.10. Without limiting the foregoing, when any such information is no longer needed for the purposes contemplated by this Agreement or any Ancillary Agreement, and is no longer subject to any legal hold or other document preservation obligation, each Party will promptly after request of the other Party either return to the other Party all such information in a tangible form (including all copies thereof and all notes, extracts or summaries based thereon) or notify the other Party in writing that it has destroyed such information (and such copies thereof and such notes, extracts or summaries based thereon); provided, that the Parties may retain electronic back-up versions of such information maintained on routine computer system backup tapes, disks or other backup storage devices; provided further, that any such information so retained shall remain subject to the confidentiality provisions of this Agreement or any Ancillary Agreement.
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.
6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇▇/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1.
6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <▇▇▇▇▇://▇▇▇.▇▇▇-‐▇▇▇▇.▇▇▇/▇▇▇▇/▇▇▇▇/▇▇▇▇>.
6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released.
6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Appellate Court Orders to Vacate, Reverse, or Materially Modify Judgment If the reviewing Court vacates, reverses, or modifies the Judgment in a manner that requires a material modification of this Agreement (including, but not limited to, the scope of release to be granted by Class Members), this Agreement shall be null and void. The Parties shall nevertheless expeditiously work together in good faith to address the appellate court’s concerns and to obtain Final Approval and entry of Judgment, sharing, on a 50-50 basis, any additional Administration Expenses reasonably incurred after remittitur. An appellate decision to vacate, reverse, or modify the Court’s award of the Class Representative Service Payment or any payments to Class Counsel shall not constitute a material modification of the Judgment within the meaning of this paragraph, as long as the Gross Settlement Amount remains unchanged.
