Dispute Resolution Procedures (a) In the event a dispute arises about the interpretation, application, calculation of Loss, or calculation of payments or otherwise with respect to this Single Family Shared-Loss Agreement (“SF Shared-Loss Dispute Item”), then the Receiver and the Assuming Bank shall make every attempt in good faith to resolve such items within sixty (60) days following the receipt of a written description of the SF Shared-Loss Dispute Item, with notification of the possibility of taking the matter to arbitration (the date on which such 60-day period expires, or any extension of such period as the parties hereto may mutually agree to in writing, herein called the “Resolution Deadline Date”). If the Receiver and the Assuming Bank resolve all such items to their mutual satisfaction by the Resolution Deadline Date, then within thirty (30) days following such resolution, any payment arising out such resolution shall be made arising from the settlement of the SF Shared-Loss Dispute.
(b) If the Receiver and the Assuming Bank fail to resolve any outstanding SF Shared- Loss Dispute Items by the Resolution Deadline Date, then either party may notify the other of its intent to submit the SF Shared-Loss Dispute Item to arbitration pursuant to the provisions of this Article VII. Failure of either party to notify the other of its intent to submit any unresolved SF Shared-Loss Dispute Item to arbitration within thirty (30) days following the Resolution Deadline Date (the date on which such thirty (30) day period expires is herein called the “Arbitration Deadline Date”) shall be deemed an acceptance of such SF Shared-Loss Dispute not submitted to arbitration, as well as a waiver of the submitting party’s right to dispute such non- submitted SF Shared-Loss Dispute Item but not a waiver of any similar claim which may arise in the future.
(c) If a SF Shared-Loss Dispute Item is submitted to arbitration, it shall be governed by the rules of the American Arbitration Association (the “AAA”), except as otherwise provided herein. Either party may submit a matter for arbitration by delivering a notice, prior to the Arbitration Deadline Date, to the other party in writing setting forth:
(i) A brief description of each SF Shared-Loss Dispute Item submitted for arbitration;
(ii) A statement of the moving party’s position with respect to each SF Shared-Loss Dispute Item submitted for arbitration;
(iii) The value sought by the moving party, or other relief requested regarding each SF Shared-Loss Dispute Item submitted for arbitration, to the extent reasonably calculable; and
(iv) The name and address of the arbiter selected by the moving party (the “Moving Arbiter”), who shall be a neutral, as determined by the AAA. Failure to adequately include any information above shall not be deemed to be a waiver of the parties right to arbitrate so long as after notification of such failure the moving party cures such failure as promptly as reasonably practicable.
(d) The non-moving party shall, within thirty (30) days following receipt of a notice of arbitration pursuant to this Section 7.1, deliver a notice to the moving party setting forth:
(i) The name and address of the arbiter selected by the non-moving party (the “Respondent Arbiter”), who shall be a neutral, as determined by the AAA;
(ii) A statement of the position of the respondent with respect to each Dispute Item; and
(iii) The ultimate resolution sought by the respondent or other relief, if any, the respondent deems is due the moving party with respect to each SF Shared-Loss Dispute Item. Failure to adequately include any information above shall not be deemed to be a waiver of the non-moving party’s right to defend such arbitration so long as after notification of such failure the non-moving party cures such failure as promptly as reasonably practicable
(e) The Moving Arbiter and Respondent Arbiter shall select a third arbiter from a list furnished by the AAA. In accordance with the rules of the AAA, the three (3) arbiters shall constitute the arbitration panel for resolution of each SF Loss-Share Dispute Item. The concurrence of any two (2) arbiters shall be deemed to be the decision of the arbiters for all purposes hereunder. The arbitration shall proceed on such time schedule and in accordance with the Rules of Commercial Arbitration of the AAA then in effect, as modified by this Section 7.1. The arbitration proceedings shall take place at such location as the parties thereto may mutually agree, but if they cannot agree, then they will take place at the offices of the Corporation in Washington, DC, or Arlington, Virginia.
(f) The Receiver and Assuming Bank shall facilitate the resolution of each outstanding SF Shared-Loss Dispute Item by making available in a prompt and timely manner to one another and to the arbiters for examination and copying, as appropriate, all documents, books, and records under their respective control and that would be discoverable under the Federal Rules of Civil Procedure.
Dispute Resolution Mechanisms Registry Operator will comply with the following dispute resolution mechanisms as they may be revised from time to time: the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) and the Registration Restriction Dispute Resolution Procedure (RRDRP) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/pddrp and xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, respectively). Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PDDRP or RRDRP panel and to be bound by any such determination; and the Uniform Rapid Suspension system (“URS”) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/urs), including the implementation of determinations issued by URS examiners. CONTINUED OPERATIONS INSTRUMENT The Continued Operations Instrument shall (a) provide for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6th) anniversary of the Effective Date, and (b) be in the form of either (i) an irrevocable standby letter of credit, or (ii) an irrevocable cash escrow deposit, each meeting the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof (which is hereby incorporated by reference into this Specification 8). Registry Operator shall use its best efforts to take all actions necessary or advisable to maintain in effect the Continued Operations Instrument for a period of six (6) years from the Effective Date, and to maintain ICANN as a third party beneficiary thereof. If Registry Operator elects to obtain an irrevocable standby letter of credit but the term required above is unobtainable, Registry Operator may obtain a letter of credit with a one-year term and an “evergreen provision,” providing for annual extensions, without amendment, for an indefinite number of additional periods until the issuing bank informs ICANN of its final expiration or until ICANN releases the letter of credit as evidenced in writing, if the letter of credit otherwise meets the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof; provided, however, that if the issuing bank informs ICANN of the expiration of such letter of credit prior to the sixth (6th) anniversary of the Effective Date, such letter of credit must provide that ICANN is entitled to draw the funds secured by the letter of credit prior to such expiration. The letter of credit must require the issuing bank to give ICANN at least thirty (30) calendar days’ notice of any such expiration or non-renewal. If the letter of credit expires or is terminated at any time prior to the sixth (6th) anniversary of the Effective Date, Registry Operator will be required to obtain a replacement Continued Operations Instrument. ICANN may draw the funds under the original letter of credit, if the replacement Continued Operations Instrument is not in place prior to the expiration of the original letter of credit. Registry Operator shall provide to ICANN copies of all final documents relating to the Continued Operations Instrument and shall keep ICANN reasonably informed of material developments relating to the Continued Operations Instrument. Registry Operator shall not agree to, or permit, any amendment of, or waiver under, the Continued Operations Instrument or other documentation relating thereto without the prior written consent of ICANN (such consent not to be unreasonably withheld). If, notwithstanding the use of best efforts by Registry Operator to satisfy its obligations under the preceding paragraph, the Continued Operations Instrument expires or is terminated by another party thereto, in whole or in part, for any reason, prior to the sixth anniversary of the Effective Date, Registry Operator shall promptly (i) notify ICANN of such expiration or termination and the reasons therefor and (ii) arrange for an alternative instrument that provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date (an “Alternative Instrument”). Any such Alternative Instrument shall be on terms no less favorable to ICANN than the Continued Operations Instrument and shall otherwise be in form and substance reasonably acceptable to ICANN. Notwithstanding anything to the contrary contained in this Specification 8, at any time, Registry Operator may replace the Continued Operations Instrument with an Alternative Instrument that (i) provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date, and (ii) contains terms no less favorable to ICANN than the Continued Operations Instrument and is otherwise in form and substance reasonably acceptable to ICANN. In the event Registry Operator replaces the Continued Operations Instrument either pursuant to paragraph 2 or this paragraph 3, the terms of this Specification 8 shall no longer apply with respect to the original Continuing Operations Instrument, but shall thereafter apply with respect to such Alternative Instrument(s), and such instrument shall thereafter be considered the Continued Operations Instrument for purposes of this Agreement. REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to: directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and subject to substantially similar conditions; register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may (a) reserve names from registration pursuant to Section 2.6 of the Agreement and (b) may withhold from registration or allocate to Registry Operator up to one hundred (100) names pursuant to Section 3.2 of Specification 5; register names in the TLD or sub-domains of the TLD based upon proprietary access to information about searches or resolution requests by consumers for domain names not yet registered (commonly known as, “front-running”); or allow any Affiliated registrar to disclose Personal Data about registrants to Registry Operator or any Registry Related Party, except as reasonably necessary for the management and operations of the TLD, unless all unrelated third parties (including other registry operators) are given equivalent access to such user data on substantially similar terms and subject to substantially similar conditions. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will, or will cause such Registry Related Party to, ensure that such services are offered through a legal entity separate from Registry Operator, and maintain separate books of accounts with respect to its registrar or registrar-reseller operations. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to an address to be provided by ICANN. (ICANN may specify in the future the form and contents of such reports or that the reports be delivered by other reasonable means.) Registry Operator agrees that ICANN may publicly post such results and certification; provided, however, ICANN shall not disclose Confidential Information contained in such results except in accordance with Section 7.15 of the Agreement. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct. Nothing set forth herein shall limit the ability of Registry Operator or any Registry Related Party, to enter into arms-length transactions in the ordinary course of business with a registrar or reseller with respect to products and services unrelated in all respects to the TLD. Registry Operator may request an exemption to this Code of Conduct, and such exemption may be granted by ICANN in ICANN’s reasonable discretion, if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for the exclusive use of Registry Operator or its Affiliates, (ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest. REGISTRY PERFORMANCE SPECIFICATIONS DNS. Refers to the Domain Name System as specified in RFCs 1034, 1035, and related RFCs. DNSSEC proper resolution. There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.
