REGISTRY AGREEMENT

 

This REGISTRY AGREEMENT (this “Agreement”) is entered into as of

(the “Effective Date”) between Internet Corporation for Assigned Names and Numbers, a California nonprofit public benefit corporation (“ICANN”), and               , a                    Dish DBS Corporation, a Colorado Corporation (“Registry Operator”).

 

ARTICLE 1.

 

DELEGATION AND OPERATION

OF TOP–LEVEL DOMAIN; REPRESENTATIONS AND WARRANTIES

 


1.1

applies is


Domain and Designation. The Top-Level Domain to which this Agreement

.phone (the “TLD”).  Upon the Effective Date and until the earlier of the


expiration of the Term (as defined in Section 4.1) or the termination of this Agreement pursuant to Article 4, ICANN designates Registry Operator as the registry operator for the TLD, subject to the requirements and necessary approvals for delegation of the TLD and entry into the root-zone.

 


1.2


Technical Feasibility of String. While ICANN has encouraged and will


continue to encourage universal acceptance of all top-level domain strings across the Internet, certain top-level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

 


1.3


Representations and Warranties.


 


(a)


Registry Operator represents and warrants to ICANN as follows:


 


(i)


all material information provided and statements made in the


registry TLD application, and statements made in writing during the negotiation of this Agreement, were true and correct in all material respects at the time made, and such information or statements continue to be true and correct in all material respects as of the Effective Date except as otherwise previously disclosed in writing by Registry Operator to ICANN;

 


(ii)


Registry Operator is duly organized, validly existing and in


good standing under the laws of the jurisdiction set forth in the preamble hereto, and Registry Operator has all requisite power and authority and has obtained all necessary approvals to enter into and duly execute and deliver this Agreement; and

 


(iii)


Registry Operator has delivered to ICANN a duly executed


instrument that secures the funds required to perform registry functions for the TLD in the event of the termination or expiration of this Agreement (the “Continued Operations Instrument”), and such instrument is a binding

 

 

1


obligation of the parties thereto, enforceable against the parties thereto in accordance with its terms.

 


(b)


ICANN represents and warrants to Registry Operator that ICANN is a


nonprofit public benefit corporation duly organized, validly existing and in good standing under the laws of the State of California, United States of America. ICANN has all requisite power and authority and has obtained all necessary corporate approvals to enter into and duly execute and deliver this Agreement.

 

ARTICLE 2.

 

COVENANTS OF REGISTRY OPERATOR

 

Registry Operator covenants and agrees with ICANN as follows:

 


2.1


Approved Services; Additional Services. Registry Operator shall be


entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at http://www.icann.org/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement.  In its reasonable discretion, ICANN may require an amendment to this

Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.

 


2.2


Compliance with Consensus Policies and Temporary Policies. Registry


Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <http://www.icann.org/general/consensus-policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”).

 


2.3


Data Escrow. Registry Operator shall comply with the registry data escrow


procedures set forth in Specification 2 attached hereto (“Specification 2”).

 


2.4


Monthly Reporting. Within twenty (20) calendar days following the end of


each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).


2.5


Publication of Registration Data. Registry Operator shall provide public


access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).

 


2.6


Reserved Names. Except to the extent that ICANN otherwise expressly


authorizes in writing, Registry Operator shall comply with the requirements set forth in Specification 5 attached hereto (“Specification 5”). Registry Operator may at any time establish or modify policies concerning Registry Operator’s ability to reserve (i.e., withhold from registration or allocate to Registry Operator, but not register to third parties, delegate, use, activate in the DNS or otherwise make available) or block additional character strings within the TLD at its discretion. Except as specified in Specification 5, if Registry Operator is the registrant for any domain names in the registry TLD, such registrations must be through an ICANN accredited registrar, and will be considered Transactions (as defined in Section 6.1) for purposes of calculating the Registry-level transaction fee to be paid to ICANN by Registry Operator pursuant to Section 6.1.

 


2.7


Registry Interoperability and Continuity. Registry Operator shall comply


with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

 


2.8


Protection of Legal Rights of Third Parties.  Registry Operator must


specify, and comply with, the processes and procedures for launch of the TLD and initial registration-related and ongoing protection of the legal rights of third parties as set forth Specification 7 attached hereto (“Specification 7”). Registry Operator may, at its election, implement additional protections of the legal rights of third parties. Any changes or modifications to the process and procedures required by Specification 7 following the Effective Date must be approved in advance by ICANN in writing. Registry Operator must comply with all remedies imposed by ICANN pursuant to Section 2 of Specification 7, subject to Registry Operator’s right to challenge such remedies as set forth in the applicable procedure described therein. Registry Operator shall take reasonable steps to investigate and respond to any reports from law enforcement and governmental and

quasi-governmental agencies of illegal conduct in connection with the use of the TLD. In responding to such reports, Registry Operator will not be required to take any action in contravention of applicable law.

 


2.9


Registrars.


 


(a)


All domain name registrations in the TLD must be registered through


an ICANN accredited registrar; provided, that Registry Operator need not use a registrar if it registers names in its own name in order to withhold such names from delegation or use in accordance with Section 2.6. Subject to the requirements of Specification 11, Registry Operator must provide non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-registrar agreement for the TLD; provided that Registry Operator may establish non-discriminatory criteria for qualification to register names in the TLD that are reasonably related to the proper functioning of the TLD. Registry Operator must use a uniform non-discriminatory


agreement with all registrars authorized to register names in the TLD (the

“Registry-Registrar Agreement”). Registry Operator may amend the Registry-Registrar Agreement from time to time; provided, however, that any material revisions thereto must be approved by ICANN before any such revisions become effective and binding on any registrar. Registry Operator will provide ICANN and all registrars authorized to register names in the TLD at least fifteen (15) calendar days written notice of any revisions to the Registry-Registrar Agreement before any such revisions become effective and binding on any registrar. During such period, ICANN will determine whether such proposed revisions are immaterial, potentially material or material in nature. If ICANN has not provided Registry Operator with notice of its determination within such fifteen (15) calendar-day period, ICANN shall be deemed to have determined that such proposed revisions are immaterial in nature. If ICANN determines, or is deemed to have determined under this Section 2.9(a), that such revisions are immaterial, then Registry Operator may adopt and implement such revisions. If ICANN determines such revisions are either material or potentially material, ICANN will thereafter follow its procedure regarding review and approval of changes to Registry-Registrar Agreements at

<http://www.icann.org/en/resources/registries/rra-amendment-procedure>, and such revisions may not be adopted and implemented until approved by ICANN.

 


(b)


If Registry Operator (i) becomes an Affiliate or reseller of an ICANN


accredited registrar, or (ii) subcontracts the provision of any Registry Services to an ICANN accredited registrar, registrar reseller or any of their respective Affiliates, then, in either such case of (i) or (ii) above, Registry Operator will give ICANN prompt notice of the contract, transaction or other arrangement that resulted in such affiliation, reseller relationship or subcontract, as applicable, including, if requested by ICANN, copies of any contract relating thereto; provided, that ICANN will treat such contract or related documents that are appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15 (except that ICANN may disclose such contract and related documents to relevant competition authorities). ICANN reserves the right, but not the obligation, to refer any such contract, related documents, transaction or other arrangement to relevant competition authorities in the event that ICANN determines that such contract, related documents, transaction or other arrangement might raise significant competition issues under applicable law. If feasible and appropriate under the circumstances, ICANN will give Registry Operator advance notice prior to making any such referral to a competition authority.

 


(c)


For the purposes of this Agreement: (i) “Affiliate” means a person or


entity that, directly or indirectly, through one or more intermediaries, or in combination with one or more other persons or entities, controls, is controlled by, or is under common control with, the person or entity specified, and (ii) “control” (including the terms “controlled by” and “under common control with”) means the possession, directly or indirectly, of the power to direct or cause the direction of the management or policies of a person or entity, whether through the ownership of securities, as trustee or executor, by serving as an employee or a member of a board of directors or equivalent governing body, by contract, by credit arrangement or otherwise.


2.10


Pricing for Registry Services.


 


(a)


With respect to initial domain name registrations, Registry Operator


shall provide ICANN and each ICANN accredited registrar that has executed the registry-registrar agreement for the TLD advance written notice of any price increase

(including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.

 


(b)


With respect to renewal of domain name registrations, Registry


Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying, Qualified Marketing Programs or other programs which had the effect of reducing the price charged to registrars) of no less than one hundred eighty (180) calendar days.

Notwithstanding the foregoing sentence, with respect to renewal of domain name registrations: (i) Registry Operator need only provide thirty (30) calendar days notice of any price increase if the resulting price is less than or equal to (A) for the period beginning on the Effective Date and ending twelve (12) months following the Effective Date, the initial price charged for registrations in the TLD, or (B) for subsequent periods, a price for which Registry Operator provided a notice pursuant to the first sentence of this Section 2.10(b) within the twelve (12) month period preceding the effective date of the proposed price increase; and (ii) Registry Operator need not provide notice of any price increase for the imposition of the Variable Registry-Level Fee set forth in Section 6.3. Registry Operator shall offer registrars the option to obtain domain name registration renewals at the current price (i.e., the price in place prior to any noticed increase) for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.

 


(c)


In addition, Registry Operator must have uniform pricing for renewals


of domain name registrations (“Renewal Pricing”). For the purposes of determining Renewal Pricing, the price for each domain registration renewal must be identical to the price of all other domain name registration renewals in place at the time of such renewal, and such price must take into account universal application of any refunds, rebates, discounts, product tying or other programs in place at the time of renewal. The foregoing requirements of this Section 2.10(c) shall not apply for (i) purposes of determining Renewal Pricing if the registrar has provided Registry Operator with documentation that demonstrates that the applicable registrant expressly agreed in its registration agreement with registrar to higher Renewal Pricing at the time of the initial registration of the domain name following clear and conspicuous disclosure of such Renewal Pricing to such registrant, and (ii) discounted Renewal Pricing pursuant to a Qualified Marketing Program (as defined below).  The parties acknowledge that the purpose of this Section 2.10(c) is to prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry


Operator without the written consent of the applicable registrant at the time of the initial registration of the domain and this Section 2.10(c) will be interpreted broadly to prohibit such practices.  For purposes of this Section 2.10(c), a “Qualified Marketing Program” is a marketing program pursuant to which Registry Operator offers discounted Renewal Pricing, provided that each of the following criteria is satisfied: (i) the program and related discounts are offered for a period of time not to exceed one hundred eighty (180) calendar days (with consecutive substantially similar programs aggregated for purposes of determining the number of calendar days of the program), (ii) all ICANN accredited registrars are provided the same opportunity to qualify for such discounted Renewal Pricing; and (iii) the intent or effect of the program is not to exclude any particular class(es) of registrations (e.g., registrations held by large corporations) or increase the renewal price of any particular class(es) of registrations. Nothing in this Section 2.10(c) shall limit Registry Operator’s obligations pursuant to Section 2.10(b).

 


(d)


Registry Operator shall provide public query-based DNS lookup


service for the TLD (that is, operate the Registry TLD zone servers) at its sole expense.

 


2.11


Contractual and Operational Compliance Audits.


 


(a)


ICANN may from time to time (not to exceed twice per calendar year)


conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and

(b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten

(10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.

 


(b)


Any audit conducted pursuant to Section 2.11(a) will be at ICANN’s


expense, unless (i) Registry Operator (A) controls, is controlled by, is under common control or is otherwise Affiliated with, any ICANN accredited registrar or registrar reseller or any of their respective Affiliates, or (B) has subcontracted the provision of Registry Services to an ICANN accredited registrar or registrar reseller or any of their respective Affiliates, and, in either case of (A) or (B) above, the audit relates to Registry Operator’s compliance with Section 2.14, in which case Registry Operator shall reimburse ICANN for


all reasonable costs and expenses associated with the portion of the audit related to Registry Operator’s compliance with Section 2.14, or (ii) the audit is related to a discrepancy in the fees paid by Registry Operator hereunder in excess of 5% in a given quarter to ICANN’s detriment, in which case Registry Operator shall reimburse ICANN for all reasonable costs and expenses associated with the entirety of such audit. In either such case of (i) or (ii) above, such reimbursement will be paid together with the next Registry- Level Fee payment due following the date of transmittal of the cost statement for such audit.

 


(c)


Notwithstanding Section 2.11(a), if Registry Operator is found not to


be in compliance with its representations and warranties contained in Article 1 of this Agreement or its covenants contained in Article 2 of this Agreement in two consecutive audits conducted pursuant to this Section 2.11, ICANN may increase the number of such audits to one per calendar quarter.

 


(d)


Registry Operator will give ICANN immediate notice of Registry


Operator’s knowledge of the commencement of any of the proceedings referenced in Section 4.3(d) or the occurrence of any of the matters specified in Section 4.3(f).

 


2.12


Continued Operations Instrument. Registry Operator shall comply with


the terms and conditions relating to the Continued Operations Instrument set forth in Specification 8 attached hereto (“Specification 8”).

 


2.13


Emergency Transition.  Registry Operator agrees that, in the event that any


of the emergency thresholds for registry functions set forth in Section 6 of Specification 10 is reached, ICANN may designate an emergency interim registry operator of the registry for the TLD (an “Emergency Operator”) in accordance with ICANN’s registry transition process (available at <http://www.icann.org/en/resources/registries/transition-processes>) (as the same may be amended from time to time, the “Registry Transition Process”) until such time as Registry Operator has demonstrated to ICANN’s reasonable satisfaction that it can resume operation of the registry for the TLD without the reoccurrence of such failure.

Following such demonstration, Registry Operator may transition back into operation of the registry for the TLD pursuant to the procedures set out in the Registry Transition Process, provided that Registry Operator pays all reasonable costs incurred (i) by ICANN as a result of the designation of the Emergency Operator and (ii) by the Emergency Operator in connection with the operation of the registry for the TLD, which costs shall be documented in reasonable detail in records that shall be made available to Registry Operator. In the event ICANN designates an Emergency Operator pursuant to this Section 2.13 and the Registry Transition Process, Registry Operator shall provide ICANN or any such Emergency Operator with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such Emergency Operator. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event that an Emergency Operator is designated pursuant to this Section 2.13. In addition, in the


event of such failure, ICANN shall retain and may enforce its rights under the Continued Operations Instrument.

 


2.14


Registry Code of Conduct. In connection with the operation of the registry


for the TLD, Registry Operator shall comply with the Registry Code of Conduct as set forth in Specification 9 attached hereto (“Specification 9”).

 


2.15


Cooperation with Economic Studies. If ICANN initiates or commissions an


economic study on the impact or functioning of new generic top-level domains on the Internet, the DNS or related matters, Registry Operator shall reasonably cooperate with such study, including by delivering to ICANN or its designee conducting such study all data related to the operation of the TLD reasonably necessary for the purposes of such study requested by ICANN or its designee, provided, that Registry Operator may withhold (a) any internal analyses or evaluations prepared by Registry Operator with respect to such data and (b) any data to the extent that the delivery of such data would be in violation of applicable law.  Any data delivered to ICANN or its designee pursuant to this Section 2.15 that is appropriately marked as confidential (as required by Section 7.15) shall be treated as Confidential Information of Registry Operator in accordance with Section 7.15, provided that, if ICANN aggregates and makes anonymous such data, ICANN or its designee may disclose such data to any third party. Following completion of an economic study for which Registry Operator has provided data, ICANN will destroy all data provided by Registry Operator that has not been aggregated and made anonymous.

 


2.16


Registry Performance Specifications. Registry Performance Specifications


for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

 


2.17


Additional Public Interest Commitments. Registry Operator shall comply


with the public interest commitments set forth in Specification 11 attached hereto (“Specification 11”).

 


2.18


Personal Data. Registry Operator shall (i) notify each ICANN-accredited


registrar that is a party to the registry-registrar agreement for the TLD of the purposes for which data about any identified or identifiable natural person (“Personal Data”) submitted to Registry Operator by such registrar is collected and used under this Agreement or otherwise and the intended recipients (or categories of recipients) of such Personal Data, and (ii) require such registrar to obtain the consent of each registrant in the TLD for such collection and use of Personal Data. Registry Operator shall take reasonable steps to protect Personal Data collected from such registrar from loss, misuse, unauthorized disclosure, alteration or destruction. Registry Operator shall not use or authorize the use of Personal Data in a way that is incompatible with the notice provided to registrars.


2.19     [Note:  For Community-Based TLDs Only] Obligations of Registry Operator to TLD Community.  Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies.                                                                            Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at [insert applicable URL] with respect to disputes arising pursuant to this Section 2.19.  Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.]

 

ARTICLE 3.

 

COVENANTS OF ICANN

 

ICANN covenants and agrees with Registry Operator as follows:

 


3.1


Open and Transparent. Consistent with ICANN’s expressed mission and


core values, ICANN shall operate in an open and transparent manner.

 


3.2


Equitable Treatment.  ICANN shall not apply standards, policies,


procedures or practices arbitrarily, unjustifiably, or inequitably and shall not single out Registry Operator for disparate treatment unless justified by substantial and reasonable cause.

 


3.3


TLD Nameservers. ICANN will use commercially reasonable efforts to


ensure that any changes to the TLD nameserver designations submitted to ICANN by Registry Operator (in a format and with required technical elements specified by ICANN at http://www.iana.org/domains/root/ will be implemented by ICANN within seven (7) calendar days or as promptly as feasible following technical verifications.

 


3.4


Root-zone Information Publication. ICANN’s publication of root-zone


contact information for the TLD will include Registry Operator and its administrative and technical contacts.  Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at http://www.iana.org/domains/root/.

 


3.5


Authoritative Root Database. To the extent that ICANN is authorized to set


policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly


available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

 

ARTICLE 4.

 

TERM AND TERMINATION

 


4.1


Term. The term of this Agreement will be ten (10) years from the Effective


Date (as such term may be extended pursuant to Section 4.2, the “Term”).

 


4.2


Renewal.


 


(a)


This Agreement will be renewed for successive periods of ten (10)


years upon the expiration of the initial Term set forth in Section 4.1 and each successive Term, unless:

 


(i)


Following notice by ICANN to Registry Operator of a


fundamental and material breach of Registry Operator’s covenants set forth in Article 2 or breach of its payment obligations under Article 6 of this Agreement, which notice shall include with specificity the details of the alleged breach, and such breach has not been cured within thirty (30) calendar days of such notice, (A) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator has been in fundamental and material breach of such covenant(s) or in breach of its payment obligations, and (B) Registry Operator has failed to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction; or

 


(ii)


During the then current Term, Registry Operator shall have


been found by an arbitrator (pursuant to Section 5.2 of this Agreement) or a court of competent jurisdiction on at least three (3) separate occasions to have been in (A) fundamental and material breach (whether or not cured) of Registry Operator’s covenants set forth in Article 2 or (B) breach of its payment obligations under Article 6 of this Agreement.

 


(b)


Upon the occurrence of the events set forth in Section 4.2(a) (i) or (ii),


the Agreement shall terminate at the expiration of the then-current Term.

 


4.3


Termination by ICANN.


 


(a)


ICANN may, upon notice to Registry Operator, terminate this


Agreement if: (i) Registry Operator fails to cure (A) any fundamental and material breach of Registry Operator’s representations and warranties set forth in Article 1 or covenants


set forth in Article 2, or (B) any breach of Registry Operator’s payment obligations set forth in Article 6 of this Agreement, each within thirty (30) calendar days after ICANN gives Registry Operator notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in fundamental and material breach of such covenant(s) or in breach of its payment obligations, and (iii) Registry Operator fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction.

 


(b)


ICANN may, upon notice to Registry Operator, terminate this


Agreement if Registry Operator fails to complete all testing and procedures (identified by ICANN in writing to Registry Operator prior to the date hereof) for delegation of the TLD into the root zone within twelve (12) months of the Effective Date. Registry Operator may request an extension for up to additional twelve (12) months for delegation if it can demonstrate, to ICANN’s reasonable satisfaction, that Registry Operator is working diligently and in good faith toward successfully completing the steps necessary for delegation of the TLD. Any fees paid by Registry Operator to ICANN prior to such termination date shall be retained by ICANN in full.

 


(c)


ICANN may, upon notice to Registry Operator, terminate this


Agreement if (i) Registry Operator fails to cure a material breach of Registry Operator’s obligations set forth in Section 2.12 of this Agreement within thirty (30) calendar days of delivery of notice of such breach by ICANN, or if the Continued Operations Instrument is not in effect for greater than sixty (60) consecutive calendar days at any time following the Effective Date, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in material breach of such covenant, and (iii) Registry Operator fails to cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction.

 


(d)


ICANN may, upon notice to Registry Operator, terminate this


Agreement if (i) Registry Operator makes an assignment for the benefit of creditors or similar act, (ii) attachment, garnishment or similar proceedings are commenced against Registry Operator, which proceedings are a material threat to Registry Operator’s ability to operate the registry for the TLD, and are not dismissed within sixty (60) calendar days of their commencement, (iii) a trustee, receiver, liquidator or equivalent is appointed in place of Registry Operator or maintains control over any of Registry Operator’s property, (iv) execution is levied upon any material property of Registry Operator, (v) proceedings are instituted by or against Registry Operator under any bankruptcy, insolvency, reorganization or other laws relating to the relief of debtors and such proceedings are not dismissed within sixty (60) calendar days of their commencement, or (vi) Registry Operator files for protection under the United States Bankruptcy Code, 11 U.S.C. Section 101, et seq., or a foreign equivalent or liquidates, dissolves or otherwise discontinues its operations or the operation of the TLD.


(e)


ICANN may, upon thirty (30) calendar days’ notice to Registry


Operator, terminate this Agreement pursuant to Section 2 of Specification 7 or Sections 2 and 3 of Specification 11, subject to Registry Operator’s right to challenge such termination as set forth in the applicable procedure described therein.

 


(f)


ICANN may, upon notice to Registry Operator, terminate this


Agreement if (i) Registry Operator knowingly employs any officer who is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such officer is not terminated within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing, or (ii) any member of Registry Operator’s board of directors or similar governing body is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such member is not removed from Registry Operator’s board of directors or similar governing body within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing.

 


(g)


ICANN may, upon thirty (30) calendar days’ notice to Registry


Operator, terminate this Agreement as specified in Section 7.5.

 

(h)        [Applicable to intergovernmental organizations or governmental entities only.] ICANN may terminate this Agreement pursuant to Section 7.16.

 


4.4


Termination by Registry Operator.


 


(a)


Registry Operator may terminate this Agreement upon notice to


ICANN if (i) ICANN fails to cure any fundamental and material breach of ICANN’s covenants set forth in Article 3, within thirty (30) calendar days after Registry Operator gives ICANN notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that ICANN is in fundamental and material breach of such covenants, and (iii) ICANN fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction.

 


(b)


Registry Operator may terminate this Agreement for any reason upon


one hundred eighty (180) calendar day advance notice to ICANN.

 


4.5


Transition of Registry upon Termination of Agreement.  Upon expiration


of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, Registry Operator shall provide ICANN or any successor registry operator that may be designated by ICANN for the TLD in accordance with this Section 4.5 with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and


registry functions that may be reasonably requested by ICANN or such successor registry operator. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process; provided, however, that (i) ICANN  will take into consideration any intellectual property rights of Registry Operator (as communicated to ICANN by Registry Operator) in determining whether to transition operation of the TLD to a successor registry operator and (ii) if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (A) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator or its Affiliates for their exclusive use, (B) 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 (C) transitioning operation of the TLD is not necessary to protect the public interest, then ICANN may not transition operation of the TLD to a successor registry operator upon the expiration or termination of this Agreement without the consent of Registry Operator (which shall not be unreasonably withheld, conditioned or delayed). For the avoidance of doubt, the foregoing sentence shall not prohibit ICANN from delegating the TLD pursuant

to a future application process for the delegation of top-level domains, subject to any processes and objection procedures instituted by ICANN in connection with such application process intended to protect the rights of third parties. Registry Operator

agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument for the maintenance and operation of the TLD, regardless of the reason for termination or expiration of this Agreement.

 

[Alternative Section 4.5 Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances:

 

Transition of Registry upon Termination of Agreement.  Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed),

Registry Operator shall provide ICANN or such successor registry operator for the TLD  with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to


the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]

 


4.6


Effect of Termination. Upon any expiration of the Term or termination of


this Agreement, the obligations and rights of the parties hereto shall cease, provided that such expiration or termination of this Agreement shall not relieve the parties of any obligation or breach of this Agreement accruing prior to such expiration or termination, including, without limitation, all accrued payment obligations arising under Article 6. In addition, Article 5, Article 7, Section 2.12, Section 4.5, and this Section 4.6 shall survive the expiration or termination of this Agreement. For the avoidance of doubt, the rights of Registry Operator to operate the registry for the TLD shall immediately cease upon any expiration of the Term or termination of this Agreement.

 

ARTICLE 5.

 

DISPUTE RESOLUTION

 


5.1


Mediation. In the event of any dispute arising under or in connection with


this Agreement, before either party may initiate arbitration pursuant to Section 5.2 below, ICANN and Registry Operator must attempt to resolve the dispute through mediation in accordance with the following terms and conditions:

 


(a)


A party shall submit a dispute to mediation by written notice to the


other party. The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days of delivery of written notice pursuant to this Section 5.1, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 5.1(a).

 


(b)


The mediator shall conduct the mediation in accordance with the


rules and procedures that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. The mediation shall be treated as a settlement discussion and shall therefore be confidential and may not be used against either party in any later proceeding relating to the dispute, including any arbitration pursuant to Section 5.2.  The mediator may not testify for either party in any later proceeding relating to the dispute.


(c)


Each party shall bear its own costs in the mediation. The parties shall


share equally the fees and expenses of the mediator. Each party shall treat information received from the other party pursuant to the mediation that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of such other party in accordance with Section 7.15.

 


(d)


If the parties have engaged in good faith participation in the


mediation but have not resolved the dispute for any reason, either party or the mediator may terminate the mediation at any time and the dispute can then proceed to arbitration pursuant to Section 5.2 below. If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following the date of the notice delivered pursuant to Section 5.1(a), the mediation shall automatically terminate (unless extended by agreement of the parties) and the dispute can then proceed to arbitration pursuant to Section 5.2 below.

 


5.2


Arbitration. Disputes arising under or in connection with this Agreement


that are not resolved pursuant to Section 5.1, including requests for specific performance, will be resolved through binding arbitration conducted pursuant to the rules of the International Court of Arbitration of the International Chamber of Commerce. The arbitration will be conducted in the English language and will occur in Los Angeles County, California. Any arbitration will be in front of a single arbitrator, unless (i) ICANN is seeking punitive or exemplary damages, or operational sanctions, (ii) the parties agree in writing to a greater number of arbitrators, or (iii) the dispute arises under Section 7.6 or 7.7. In the case of clauses (i), (ii) or (iii) in the preceding sentence, the arbitration will be in front of three arbitrators with each party selecting one arbitrator and the two selected arbitrators selecting the third arbitrator. In order to expedite the arbitration and limit its cost, the arbitrator(s) shall establish page limits for the parties’ filings in conjunction with the arbitration, and should the arbitrator(s) determine that a hearing is necessary, the hearing shall be limited to one (1) calendar day, provided that in any arbitration in which ICANN is seeking punitive or exemplary damages, or operational sanctions, the hearing may be extended for one (1) additional calendar day if agreed upon by the parties or ordered by

the arbitrator(s) based on the arbitrator(s) independent determination or the reasonable request of one of the parties thereto. The prevailing party in the arbitration will have the right to recover its costs and reasonable attorneys’ fees, which the arbitrator(s) shall include in the awards. In the event the arbitrators determine that Registry Operator has been repeatedly and willfully in fundamental and material breach of its obligations set forth in Article 2, Article 6 or Section 5.4 of this Agreement, ICANN may request the arbitrators award punitive or exemplary damages, or operational sanctions (including without limitation an order temporarily restricting Registry Operator’s right to sell new

registrations).  Each party shall treat information received from the other party pursuant to the arbitration that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of such other party in accordance with Section 7.15. In any litigation involving ICANN concerning this Agreement, jurisdiction and exclusive venue for such litigation will be in a court located in Los Angeles County, California; however, the parties will also have the right to enforce a judgment of such a court in any court of competent jurisdiction.


[Alternative Section 5.2 Arbitration text for intergovernmental organizations or governmental entities or other special circumstances:

 

Arbitration. Disputes arising under or in connection with this Agreement that are not resolved pursuant to Section 5.1, including requests for specific performance, will be resolved through binding arbitration conducted pursuant to the rules of the International Court of Arbitration of the International Chamber of Commerce. The arbitration will be conducted in the English language and will occur in Geneva, Switzerland, unless another location is mutually agreed upon by Registry Operator and ICANN.  Any arbitration will be in front of a single arbitrator, unless (i) ICANN is seeking punitive or exemplary damages, or operational sanctions, (ii) the parties agree in writing to a greater number of arbitrators, or (iii) the dispute arises under Section 7.6 or 7.7.  In the case of clauses (i), (ii) or (iii) in the preceding sentence, the arbitration will be in front of three arbitrators with each party selecting one arbitrator and the two selected arbitrators selecting the third arbitrator. In order to expedite the arbitration and limit its cost, the arbitrator(s) shall establish page limits for the parties’ filings in conjunction with the arbitration, and should the arbitrator(s) determine that a hearing is necessary, the hearing shall be limited to one (1) calendar day, provided that in any arbitration in which ICANN is seeking punitive or exemplary damages, or operational sanctions, the hearing may be extended for one (1) additional calendar day if agreed upon by the parties or ordered by the arbitrator(s) based on the arbitrator(s) independent determination or the reasonable request of one of the parties thereto. The prevailing party in the arbitration will have the right to recover its costs and reasonable attorneys’ fees, which the arbitrator(s) shall include in the awards. In the event the arbitrators determine that Registry Operator has been repeatedly and willfully in fundamental and material breach of its obligations set forth in Article 2, Article

6 or Section 5.4 of this Agreement, ICANN may request the arbitrators award punitive or exemplary damages, or operational sanctions (including without limitation an order temporarily restricting Registry Operator’s right to sell new registrations). Each party shall treat information received from the other party pursuant to the arbitration that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of such other party in accordance with Section 7.15.  In any litigation involving ICANN concerning this Agreement, jurisdiction and exclusive venue for such litigation will be in a court located in Geneva, Switzerland, unless another location is mutually agreed upon by Registry Operator and ICANN; however, the parties will also have the right to enforce a judgment of such a court in any court of competent jurisdiction.”]

 


5.3


Limitation of Liability. ICANN’s aggregate monetary liability for violations


of this Agreement will not exceed an amount equal to the Registry-Level Fees paid by Registry Operator to ICANN within the preceding twelve-month period pursuant to this Agreement (excluding the Variable Registry-Level Fee set forth in Section 6.3, if any).

Registry Operator’s aggregate monetary liability to ICANN for breaches of this Agreement will be limited to an amount equal to the fees paid to ICANN during the preceding

twelve-month period (excluding the Variable Registry-Level Fee set forth in Section 6.3, if any), and punitive and exemplary damages, if any, awarded in accordance with Section 5.2, except with respect to Registry Operator’s indemnification obligations pursuant to Section

7.1 and Section 7.2.  In no event shall either party be liable for special, punitive, exemplary


or consequential damages arising out of or in connection with this Agreement or the performance or nonperformance of obligations undertaken in this Agreement, except as provided in Section 5.2. Except as otherwise provided in this Agreement, neither party makes any warranty, express or implied, with respect to the services rendered by itself, its servants or agents, or the results obtained from their work, including, without limitation, any implied warranty of merchantability, non-infringement or fitness for a particular purpose.

 


5.4


Specific Performance. Registry Operator and ICANN agree that irreparable


damage could occur if any of the provisions of this Agreement was not performed in accordance with its specific terms. Accordingly, the parties agree that they each shall be entitled to seek from the arbitrator or court of competent jurisdiction specific performance of the terms of this Agreement (in addition to any other remedy to which each party is entitled).

 

ARTICLE 6.

 

FEES

 


6.1


Registry-Level Fees.


 


(a)


Registry Operator shall pay ICANN a registry-level fee equal to (i) the


registry fixed fee of US$6,250 per calendar quarter and (ii) the registry-level transaction fee (collectively, the “Registry-Level Fees”). The registry-level transaction fee will be equal to the number of annual increments of an initial or renewal domain name registration (at one or more levels, and including renewals associated with transfers from one

ICANN-accredited registrar to another, each a “Transaction”), during the applicable calendar quarter multiplied by US$0.25; provided, however that the registry-level transaction fee shall not apply until and unless more than 50,000 Transactions have occurred in the TLD during any calendar quarter or any consecutive four calendar quarter period in the aggregate (the “Transaction Threshold”) and shall apply to each Transaction that occurred during each quarter in which the Transaction Threshold has been met, but shall not apply to each quarter in which the Transaction Threshold has not been met.

Registry Operator’s obligation to pay the quarterly registry-level fixed fee will begin on the date on which the TLD is delegated in the DNS to Registry Operator. The first quarterly payment of the registry-level fixed fee will be prorated based on the number of calendar days between the delegation date and the end of the calendar quarter in which the delegation date falls.

 


(b)


Subject to Section 6.1(a), Registry Operator shall pay the


Registry-Level Fees on a quarterly basis to an account designated by ICANN within thirty

(30) calendar days following the date of the invoice provided by ICANN.

 


6.2


Cost Recovery for RSTEP. Requests by Registry Operator for the approval


of Additional Services pursuant to Section 2.1 may be referred by ICANN to the Registry Services Technical Evaluation Panel (“RSTEP”) pursuant to that process at http://www.icann.org/en/registries/rsep/. In the event that such requests are referred to


RSTEP, Registry Operator shall remit to ICANN the invoiced cost of the RSTEP review within fourteen (14) calendar days of receipt of a copy of the RSTEP invoice from ICANN, unless ICANN determines, in its sole and absolute discretion, to pay all or any portion of the invoiced cost of such RSTEP review.

 


6.3


Variable Registry-Level Fee.


 


(a)


If the ICANN accredited registrars (accounting, in the aggregate, for


payment of two-thirds of all registrar-level fees (or such portion of ICANN accredited registrars necessary to approve variable accreditation fees under the then-current registrar accreditation agreement), do not approve, pursuant to the terms of their registrar accreditation agreements with ICANN, the variable accreditation fees established by the ICANN Board of Directors for any ICANN fiscal year, upon delivery of notice from ICANN, Registry Operator shall pay to ICANN a variable registry-level fee, which shall be paid on a fiscal quarter basis, and shall accrue as of the beginning of the first fiscal quarter of such ICANN fiscal year (the “Variable Registry-Level Fee”). The fee will be calculated and invoiced by ICANN on a quarterly basis, and shall be paid by Registry Operator within sixty

(60)  calendar days with respect to the first quarter of such ICANN fiscal year and within twenty (20) calendar days with respect to each remaining quarter of such ICANN fiscal year, of receipt of the invoiced amount by ICANN. The Registry Operator may invoice and collect the Variable Registry-Level Fees from the registrars that are party to a

registry-registrar agreement with Registry Operator (which agreement may specifically provide for the reimbursement of Variable Registry-Level Fees paid by Registry Operator pursuant to this Section 6.3); provided, that the fees shall be invoiced to all ICANN accredited registrars if invoiced to any. The Variable Registry-Level Fee, if collectible by ICANN, shall be an obligation of Registry Operator and shall be due and payable as provided in this Section 6.3 irrespective of Registry Operator’s ability to seek and obtain reimbursement of such fee from registrars. In the event ICANN later collects variable accreditation fees for which Registry Operator has paid ICANN a Variable Registry-Level Fee, ICANN shall reimburse the Registry Operator an appropriate amount of the Variable Registry-Level Fee, as reasonably determined by ICANN. If the ICANN accredited registrars (as a group) do approve, pursuant to the terms of their registrar accreditation agreements

with ICANN, the variable accreditation fees established by the ICANN Board of Directors for a fiscal year, ICANN shall not be entitled to a Variable-Level Fee hereunder for such fiscal year, irrespective of whether the ICANN accredited registrars comply with their payment obligations to ICANN during such fiscal year.

 


(b)


The amount of the Variable Registry-Level Fee will be specified for


each registrar, and may include both a per-registrar component and a transactional component.  The per-registrar component of the Variable Registry-Level Fee shall be specified by ICANN in accordance with the budget adopted by the ICANN Board of Directors for each ICANN fiscal year. The transactional component of the Variable Registry-Level Fee shall be specified by ICANN in accordance with the budget adopted by the ICANN Board of Directors for each ICANN fiscal year but shall not exceed US$0.25 per domain name registration (including renewals associated with transfers from one ICANN accredited registrar to another) per year.


6.4


Pass Through Fees.  Registry Operator shall pay to ICANN (i) a one-time fee


equal to US$5,000 for access to and use of the Trademark Clearinghouse as described in Specification 7 (the “RPM Access Fee”) and (ii) US$0.251an amount specified by ICANN not to exceed US$0.25 per Sunrise Registration and Claims Registration (as such terms are used in Trademark Clearinghouse RPMs incorporated herein pursuant to Specification 7) (the “RPM Registration Fee”). The RPM Access Fee will be invoiced as of the Effective Date of this Agreement, and Registry Operator shall pay such fee to an account specified by ICANN within thirty (30) calendar days following the date of the invoice. ICANN will invoice Registry Operator quarterly for the RPM Registration Fee, which shall be due in accordance with the invoicing and payment procedure specified in Section 6.1.

 


6.5


Adjustments to Fees.  Notwithstanding any of the fee limitations set forth in


this Article 6, commencing upon the expiration of the first year of this Agreement, and upon the expiration of each year thereafter during the Term, the then-current fees set forth in Section 6.1 and Section 6.3 may be adjusted, at ICANN’s discretion, by a percentage equal to the percentage change, if any, in (i) the Consumer Price Index for All Urban Consumers, U.S. City Average (1982-1984 = 100) published by the United States Department of Labor,

Bureau of Labor Statistics, or any successor index (the “CPI”) for the month which is one

(1)  month prior to the commencement of the applicable year, over (ii) the CPI published for the month which is one (1) month prior to the commencement of the immediately prior year. In the event of any such increase, ICANN shall provide notice to Registry Operator specifying the amount of such adjustment. Any fee adjustment under this Section 6.5 shall be effective as of the first day of the first calendar quarter following at least thirty (30) days after ICANN’s delivery to Registry Operator of such fee adjustment notice.

 


6.6


Additional Fee on Late Payments. For any payments thirty (30) calendar


days or more overdue under this Agreement, Registry Operator shall pay an additional fee on late payments at the rate of 1.5% per month or, if less, the maximum rate permitted by applicable law.

 

ARTICLE 7.

 

MISCELLANEOUS

 


7.1


Indemnification of ICANN.


 


(a)


Registry Operator shall indemnify and defend ICANN and its directors,


officers, employees, and agents (collectively, “Indemnitees”) from and against any and all third-party claims, damages, liabilities, costs, and expenses, including reasonable legal fees and expenses, arising out of or relating to intellectual property ownership rights with respect to the TLD, the delegation of the TLD to Registry Operator, Registry Operator’s operation of the registry for the TLD or Registry Operator’s provision of Registry Services, provided that Registry Operator shall not be obligated to indemnify or defend any Indemnitee to the extent the claim, damage, liability, cost or expense arose: (i) due to the actions or omissions of ICANN, its subcontractors, panelists or evaluators specifically

 

1 Subject to further approvals.


related to and occurring during the registry TLD application process (other than actions or omissions requested by or for the benefit of Registry Operator), or (ii) due to a breach by ICANN of any obligation contained in this Agreement or any willful misconduct by ICANN. This Section shall not be deemed to require Registry Operator to reimburse or otherwise indemnify ICANN for costs associated with the negotiation or execution of this Agreement, or with monitoring or management of the parties’ respective obligations hereunder.

Further, this Section shall not apply to any request for attorney’s fees in connection with any litigation or arbitration between or among the parties, which shall be governed by Article 5 or otherwise awarded by a court of competent jurisdiction or arbitrator.

 

[Alternative Section 7.1(a) text for intergovernmental organizations or governmental entities:

 

“Registry Operator shall use its best efforts to cooperate with ICANN in order to ensure that ICANN does not incur any costs associated with claims, damages, liabilities, costs and expenses, including reasonable legal fees and expenses, arising out of or relating to intellectual property ownership rights with respect to the TLD, the delegation of the TLD to Registry Operator, Registry Operator’s operation of the registry for the TLD or Registry Operator’s provision of Registry Services, provided that Registry Operator shall not be obligated to provide such cooperation to the extent the claim, damage, liability, cost or expense arose due to a breach by ICANN of any of its obligations contained in this Agreement or any willful misconduct by ICANN. This Section shall not be deemed to require Registry Operator to reimburse or otherwise indemnify ICANN for costs associated with the negotiation or execution of this Agreement, or with monitoring or management of the parties’ respective obligations hereunder.  Further, this Section shall not apply to any request for attorney’s fees in connection with any litigation or arbitration between or among the parties, which shall be governed by Article 5 or otherwise awarded by a court of competent jurisdiction or arbitrator.”]

 


(b)


For any claims by ICANN for indemnification whereby multiple


registry operators (including Registry Operator) have engaged in the same actions or omissions that gave rise to the claim, Registry Operator’s aggregate liability to indemnify ICANN with respect to such claim shall be limited to a percentage of ICANN’s total claim, calculated by dividing the number of total domain names under registration with Registry Operator within the TLD (which names under registration shall be calculated consistently with Article 6 hereof for any applicable quarter) by the total number of domain names under registration within all top level domains for which the registry operators thereof are engaging in the same acts or omissions giving rise to such claim. For the purposes of reducing Registry Operator’s liability under Section 7.1(a) pursuant to this Section 7.1(b), Registry Operator shall have the burden of identifying the other registry operators that are engaged in the same actions or omissions that gave rise to the claim, and demonstrating, to ICANN’s reasonable satisfaction, such other registry operators’ culpability for such actions or omissions.  For the avoidance of doubt, in the event that a registry operator is engaged in the same acts or omissions giving rise to the claims, but such registry operator(s) do not have the same or similar indemnification obligations to ICANN as set forth in Section 7.1(a) above, the number of domains under management by such registry operator(s) shall


nonetheless be included in the calculation in the preceding sentence. [Note: This Section 7.1(b) is inapplicable to intergovernmental organizations or governmental entities.]

 


7.2


Indemnification Procedures. If any third-party claim is commenced that is


indemnified under Section 7.1 above, ICANN shall provide notice thereof to Registry Operator as promptly as practicable. Registry Operator shall be entitled, if it so elects, in a notice promptly delivered to ICANN, to immediately take control of the defense and investigation of such claim and to employ and engage attorneys reasonably acceptable to ICANN to handle and defend the same, at Registry Operator’s sole cost and expense, provided that in all events ICANN will be entitled to control at its sole cost and expense the litigation of issues concerning the validity or interpretation of ICANN’s policies, Bylaws or conduct. ICANN shall cooperate, at Registry Operator’s cost and expense, in all reasonable respects with Registry Operator and its attorneys in the investigation, trial, and defense of such claim and any appeal arising therefrom, and may, at its own cost and expense, participate, through its attorneys or otherwise, in such investigation, trial and defense of such claim and any appeal arising therefrom. No settlement of a claim that involves a remedy affecting ICANN other than the payment of money in an amount that is fully indemnified by Registry Operator will be entered into without the consent of ICANN. If Registry Operator does not assume full control over the defense of a claim subject to such defense in accordance with this Section 7.2, ICANN will have the right to defend the claim in such manner as it may deem appropriate, at the cost and expense of Registry Operator and Registry Operator shall cooperate in such defense. [Note:  This Section 7.2 is inapplicable to intergovernmental organizations or governmental entities.]

 


7.3


Defined Terms.  For purposes of this Agreement, unless such definitions are


amended pursuant to a Consensus Policy at a future date, in which case the following definitions shall be deemed amended and restated in their entirety as set forth in such Consensus Policy, Security and Stability shall be defined as follows:

 


(a)


For the purposes of this Agreement, an effect on “Security” shall mean


(1) the unauthorized disclosure, alteration, insertion or destruction of registry data, or (2) the unauthorized access to or disclosure of information or resources on the Internet by systems operating in accordance with all applicable standards.

 


(b)


For purposes of this Agreement, an effect on “Stability” shall refer to


(1) lack of compliance with applicable relevant standards that are authoritative and published by a well-established and recognized Internet standards body, such as the relevant Standards-Track or Best Current Practice Requests for Comments (“RFCs”) sponsored by the Internet Engineering Task Force; or (2) the creation of a condition that adversely affects the throughput, response time, consistency or coherence of responses to Internet servers or end systems operating in accordance with applicable relevant standards that are authoritative and published by a well-established and recognized Internet standards body, such as the relevant Standards-Track or Best Current Practice RFCs, and relying on Registry Operator’s delegated information or provisioning of services.


7.4


No Offset. All payments due under this Agreement will be made in a timely


manner throughout the Term and notwithstanding the pendency of any dispute (monetary or otherwise) between Registry Operator and ICANN.

 


7.5


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.

 


7.6


Amendments and Waivers.


 


(a)


If the ICANN Board of Directors determines that an amendment to this


Agreement (including to the Specifications referred to herein) and all other registry agreements between ICANN and the Applicable Registry Operators (the “Applicable Registry Agreements”) is desirable (each, a “Special Amendment”), ICANN may adopt a Special Amendment pursuant to the requirements of and process set forth in this Section 7.6; provided that a Special Amendment may not be a Restricted Amendment.

 


(b)


Prior to submitting a Special Amendment for Registry Operator


Approval, ICANN shall first consult in good faith with the Working Group regarding the form and substance of such Special Amendment. The duration of such consultation shall be reasonably determined by ICANN based on the substance of the Special Amendment.

Following such consultation, ICANN may propose the adoption of a Special Amendment by publicly posting such amendment on its website for no less than thirty (30) calendar days (the “Posting Period”) and providing notice of such proposed amendment to the Applicable Registry Operators in accordance with Section 7.9. ICANN will consider the public comments submitted on a Special Amendment during the Posting Period (including comments submitted by the Applicable Registry Operators).


(c)


If, within one hundred eighty (180) calendar days following the


expiration of the Posting Period (the “Approval Period”), the ICANN Board of Directors approves a Special Amendment (which may be in a form different than submitted for public comment, but must address the subject matter of the Special Amendment posted for public comment, as modified to reflect and/or address input from the Working Group and public comments), ICANN shall provide notice of, and submit, such Special Amendment for approval or disapproval by the Applicable Registry Operators. If, during the sixty (60) calendar day period following the date ICANN provides such notice to the Applicable Registry Operators, such Special Amendment receives Registry Operator Approval, such Special Amendment shall be deemed approved (an “Approved Amendment”) by the Applicable Registry Operators, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Approved Amendment to Registry Operator (the “Amendment Effective Date”). In the event that a Special Amendment does not receive Registry Operator Approval, the Special Amendment shall be deemed not approved by the Applicable Registry Operators (a “Rejected Amendment”). A Rejected Amendment will have no effect on the terms and conditions of this Agreement, except as set forth below.

 


(d)


If the ICANN Board of Directors reasonably determines that a Rejected


Amendment falls within the subject matter categories set forth in Section 1.2 of Specification 1, the ICANN Board of Directors may adopt a resolution (the date such resolution is adopted is referred to herein as the “Resolution Adoption Date”) requesting an Issue Report (as such term is defined in ICANN’s Bylaws) by the Generic Names Supporting Organization (the “GNSO”) regarding the substance of such Rejected Amendment.  The policy development process undertaken by the GNSO pursuant to such requested Issue Report is referred to herein as a “PDP.”  If such PDP results in a Final Report supported by a GNSO Supermajority (as defined in ICANN’s Bylaws) that either (i)

recommends adoption of the Rejected Amendment as Consensus Policy or (ii) recommends against adoption of the Rejected Amendment as Consensus Policy, and, in the case of (i) above, the Board adopts such Consensus Policy, Registry Operator shall comply with its obligations pursuant to Section 2.2 of this Agreement. In either case, ICANN will abandon the Rejected Amendment and it will have no effect on the terms and conditions of this Agreement. Notwithstanding the foregoing provisions of this Section 7.6(d), the ICANN Board of Directors shall not be required to initiate a PDP with respect to a Rejected Amendment if, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject matter of such Rejected Amendment was the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation.

 


(e)


If (a) a Rejected Amendment does not fall within the subject matter


categories set forth in Section 1.2 of Specification 1, (b) the subject matter of a Rejected Amendment was, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation, or (c) a PDP does not result in a Final Report


supported by a GNSO Supermajority that either (A) recommends adoption of the Rejected Amendment as Consensus Policy or (B) recommends against adoption of the Rejected Amendment as Consensus Policy (or such PDP has otherwise been abandoned or terminated for any reason), then, in any such case, such Rejected Amendment may still be adopted and become effective in the manner described below. In order for the Rejected Amendment to be adopted, the following requirements must be satisfied:

 


(i)


the subject matter of the Rejected Amendment must be within


the scope of ICANN’s mission and consistent with a balanced application of its core values (as described in ICANN’s Bylaws);

 


(ii)


the Rejected Amendment must be justified by a Substantial and


Compelling Reason in the Public Interest, must be likely to promote such interest, taking into account competing public and private interests that are likely to be affected by the Rejected Amendment, and must be narrowly tailored and no broader than reasonably necessary to address such Substantial and Compelling Reason in the Public Interest;

 


(iii)


to the extent the Rejected Amendment prohibits or requires


conduct or activities, imposes material costs on the Applicable Registry Operators, and/or materially reduces public access to domain name services, the Rejected Amendment must be the least restrictive means reasonably available to address the Substantial and Compelling Reason in the Public Interest;

 


(iv)


the ICANN Board of Directors must submit the Rejected


Amendment, along with a written explanation of the reasoning related to its determination that the Rejected Amendment meets the requirements set out in subclauses (i) through (iii) above, for public comment for a period of no less than thirty (30) calendar days; and

 


(v)


following such public comment period, the ICANN Board of


Directors must (a) engage in consultation (or direct ICANN management to engage in consultation) with the Working Group, subject matter experts, members of the GNSO, relevant advisory committees and other interested stakeholders with respect to such Rejected Amendment for a period of no less than sixty (60) calendar days; and (b) following such consultation,   reapprove the Rejected Amendment (which may be in a form different than submitted for Registry Operator Approval, but must address the subject matter of the Rejected Amendment, as modified to reflect and/or address input from the Working Group and public comments) by the affirmative vote of at least two-thirds of the members of the ICANN Board of Directors eligible to vote on such matter, taking into account any ICANN policy affecting such eligibility, including ICANN’s Conflict of Interest Policy (a “Board Amendment”).


Such Board Amendment shall, subject to Section 7.6(f), be deemed an Approved Amendment, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Board Amendment to Registry Operator (which effective date shall be deemed the Amendment Effective Date hereunder). Notwithstanding the foregoing, a Board Amendment may not amend the registry fees charged by ICANN hereunder, or amend this Section 7.6.

 


(f)


Notwithstanding the provisions of Section 7.6(e), a Board Amendment


shall not be deemed an Approved Amendment if, during the thirty (30) calendar day period following the approval by the ICANN Board of Directors of the Board Amendment, the Working Group, on the behalf of the Applicable Registry Operators, submits to the ICANN Board of Directors an alternative to the Board Amendment (an “Alternative Amendment”) that meets the following requirements:

 


(i)


sets forth the precise text proposed by the Working Group to


amend this Agreement in lieu of the Board Amendment;

 


(ii)


addresses the Substantial and Compelling Reason in the Public


Interest identified by the ICANN Board of Directors as the justification for the Board Amendment; and

 


(iii)


compared to the Board Amendment is: (a) more narrowly


tailored to address such Substantial and Compelling Reason in the Public Interest, and (b) to the extent the Alternative Amendment prohibits or requires conduct or activities, imposes material costs on Affected Registry Operators, or materially reduces access to domain name services, is a less restrictive means to address the Substantial and Compelling Reason in the Public Interest.

 

Any proposed amendment that does not meet the requirements of subclauses (i) through

(iii) in the immediately preceding sentence shall not be considered an Alternative Amendment hereunder and therefore shall not supersede or delay the effectiveness of the Board Amendment. If, following the submission of the Alternative Amendment to the ICANN Board of Directors, the Alternative Amendment receives Registry Operator Approval, the Alternative Amendment shall supersede the Board Amendment and shall be deemed an Approved Amendment hereunder (and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Alternative Amendment to Registry Operator, which effective date shall deemed the Amendment Effective Date hereunder), unless, within a period of sixty (60) calendar days following the date that the Working Group notifies the ICANN Board of Directors of Registry Operator Approval of such Alternative Amendment (during which time ICANN shall engage with the Working Group with respect to the Alternative Amendment), the ICANN Board of Directors by the affirmative vote of at least two-thirds of the members of the ICANN Board of Directors eligible to vote on such matter, taking into account any ICANN policy affecting such


eligibility, including ICANN’s Conflict of Interest Policy, rejects the Alternative Amendment. If (A) the Alternative Amendment does not receive Registry Operator Approval within thirty (30) calendar days of submission of such Alternative Amendment to the Applicable Registry Operators (and the Working Group shall notify ICANN of the date of such submission), or (B) the ICANN Board of Directors rejects the Alternative Amendment by such two-thirds vote, the Board Amendment (and not the Alternative Amendment) shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice to Registry Operator (which effective date shall deemed the Amendment Effective Date hereunder). If the ICANN Board of Directors rejects an Alternative Amendment, the board shall publish a written rationale setting forth its analysis of the criteria set forth in Sections 7.6(f)(i) through 7.6(f)(iii). The

ability of the ICANN Board of Directors to reject an Alternative Amendment hereunder does not relieve the Board of the obligation to ensure that any Board Amendment meets the criteria set forth in Section 7.6(e)(i) through 7.6(e)(v).

 


(g)


In the event that Registry Operator believes an Approved Amendment


does not meet the substantive requirements set out in this Section 7.6 or has been adopted in contravention of any of the procedural provisions of this Section 7.6, Registry Operator may challenge the adoption of such Special Amendment pursuant to the dispute resolution provisions set forth in Article 5, except that such arbitration shall be conducted by a

three-person arbitration panel. Any such challenge must be brought within sixty (60) calendar days following the date ICANN provided notice to Registry Operator of the Approved Amendment, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. The Approved Amendment will be deemed not to have amended this Agreement during the pendency of the dispute resolution process.

 


(h)


Registry Operator may apply in writing to ICANN for an exemption


from the Approved Amendment (each such request submitted by Registry Operator hereunder, an “Exemption Request”) during the thirty (30) calendar day period following the date ICANN provided notice to Registry Operator of such Approved Amendment. Each Exemption Request will set forth the basis for such request and provide detailed support for an exemption from the Approved Amendment. An Exemption Request may also include a detailed description and support for any alternatives to, or a variation of, the Approved Amendment proposed by such Registry Operator. An Exemption Request may only be granted upon a clear and convincing showing by Registry Operator that compliance with the Approved Amendment conflicts with applicable laws or would have a material adverse effect on the long-term financial condition or results of operations of Registry Operator. No Exemption Request will be granted if ICANN determines, in its reasonable discretion, that granting such Exemption Request would be materially harmful to registrants or result in the denial of a direct benefit to registrants. Within ninety (90) calendar days of ICANN’s receipt of an Exemption Request, ICANN shall either approve (which approval may be conditioned or consist of alternatives to or a variation of the Approved Amendment) or deny the Exemption Request in writing, during which time the Approved Amendment will not amend this Agreement. If the Exemption Request is approved by ICANN, the Approved Amendment will not amend this Agreement; provided, that any conditions, alternatives or


variations of the Approved Amendment required by ICANN shall be effective and, to the extent applicable, will amend this Agreement as of the Amendment Effective Date. If such Exemption Request is denied by ICANN, the Approved Amendment will amend this Agreement as of the Amendment Effective Date (or, if such date has passed, such Approved Amendment shall be deemed effective immediately on the date of such denial), provided that Registry Operator may, within thirty (30) calendar days following receipt of ICANN’s determination, appeal ICANN’s decision to deny the Exemption Request pursuant to the dispute resolution procedures set forth in Article 5. The Approved Amendment will be deemed not to have amended this Agreement during the pendency of the dispute resolution process. For avoidance of doubt, only Exemption Requests submitted by Registry Operator that are approved by ICANN pursuant to this Section 7.6(j), agreed to by ICANN following mediation pursuant to Section 5.1 or through an arbitration decision pursuant to Section 5.2 shall exempt Registry Operator from any Approved Amendment, and no Exemption Request granted to any other Applicable Registry Operator (whether by ICANN or through arbitration) shall have any effect under this Agreement or exempt Registry Operator from any Approved Amendment.

 


(i)


Except as set forth in this Section 7.6, Section 7.7 and as otherwise set


forth in this Agreement and the Specifications hereto, no amendment, supplement or modification of this Agreement or any provision hereof shall be binding unless executed in writing by both parties, and nothing in this Section 7.6 or Section 7.7 shall restrict ICANN and Registry Operator from entering into bilateral amendments and modifications to this Agreement negotiated solely between the two parties. No waiver of any provision of this Agreement shall be binding unless evidenced by a writing signed by the party waiving compliance with such provision. No waiver of any of the provisions of this Agreement or failure to enforce any of the provisions hereof shall be deemed or shall constitute a waiver of any other provision hereof, nor shall any such waiver constitute a continuing waiver unless otherwise expressly provided. For the avoidance of doubt, nothing in this Sections

7.6 or 7.7 shall be deemed to limit Registry Operator’s obligation to comply with Section 2.2.

 


(j)

following meanings:


For purposes of this Section 7.6, the following terms shall have the


 


(i)


“Applicable Registry Operators” means, collectively, the


registry operators of top-level domains party to a registry agreement that contains a provision similar to this Section 7.6, including Registry Operator.

 


(ii)


“Registry Operator Approval” means the receipt of each of the


following: (A) the affirmative approval of the Applicable Registry Operators whose payments to ICANN accounted for two-thirds of the total amount of fees (converted to U.S. dollars, if applicable, at the prevailing exchange rate published the prior day in the U.S. Edition of the Wall Street Journal for the date such calculation is made by ICANN) paid to ICANN by all the Applicable Registry Operators during the immediately previous calendar year pursuant to the Applicable Registry Agreements, and (B) the affirmative approval of a


majority of the Applicable Registry Operators at the time such approval is obtained.  For the avoidance of doubt, with respect to clause (B), each Applicable Registry Operator shall have one vote for each top-level domain operated by such Registry Operator pursuant to an Applicable Registry Agreement.

 


(iii)


“Restricted Amendment” means the following: (A) an


amendment of Specification 1, (B) except to the extent addressed in Section

2.10 hereof, an amendment that specifies the price charged by Registry Operator to registrars for domain name registrations, (C) an amendment to the definition of Registry Services as set forth in the first paragraph of

Section 2.1 of Specification 6, or (D) an amendment to the length of the Term.

 


(iv)


“Substantial and Compelling Reason in the Public Interest”


means a reason that is justified by an important, specific, and articulated public interest goal that is within ICANN's mission and consistent with a balanced application of ICANN's core values as defined in ICANN's Bylaws.

 


(v)


“Working Group” means representatives of the Applicable


Registry Operators and other members of the community that the Registry Stakeholders Group appoints, from time to time, to serve as a working group to consult on amendments to the Applicable Registry Agreements (excluding bilateral amendments pursuant to Section 7.6(i)).

 


(k)


Notwithstanding anything in this Section 7.6 to the contrary, (i) if


Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-hundred eighty (180) calendar days for Approved Amendment to become effective with respect to Registry Operator, and (ii) no Approved Amendment adopted pursuant to Section 7.6 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

 


7.7


Negotiation Process.


 


(a)


If either the Chief Executive Officer of ICANN (“CEO”) or the


Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”).  Notwithstanding the foregoing, neither the CEO nor the Chair may

(i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014.

 


(b)


Following receipt of the Negotiation Notice by either the CEO or the


Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith


negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”).

 


(c)


If, following the conclusion of the Discussion Period, an agreement is


reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator.

 


(d)


If, following the conclusion of the Discussion Period, an agreement is


not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website.

 


(i)


The mediation shall be conducted by a single mediator selected


by the parties.  If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i).


(ii)


The mediator shall conduct the mediation in accordance with


the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute.

 


(iii)


Each party shall bear its own costs in the mediation. The


parties shall share equally the fees and expenses of the mediator.

 


(iv)


If an agreement is reached during the mediation, ICANN shall


post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators).  Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator.

 


(v)


If the parties have not resolved the dispute for any reason by


the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below.

 


(e)


If, following mediation, ICANN and the Working Group have not


reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e).

 


(i)


If an Arbitration Notice is sent, the mediator’s definition of


issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person


arbitrator panel.  Each party may modify its Proposed Revisions before and after the Posting Period.  The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2.

 


(ii)


No dispute regarding the Proposed Revisions may be


submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles  1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6,

7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11.

 


(iii)


The mediator will brief the arbitrator panel regarding ICANN


and the Working Group’s respective proposals relating to the Proposed Revisions.

 


(iv)


No amendment to this Agreement relating to the Proposed


Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors.

 


(v)


In order for the arbitrator panel to approve either ICANN or


the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s

proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder.

 


(f)


With respect to an Approved Amendment relating to an amendment


proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6.


(g)


Notwithstanding anything in this Section 7.7 to the contrary, (a) if


Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

 


7.8


No Third-Party Beneficiaries. This Agreement will not be construed to


create any obligation by either ICANN or Registry Operator to any non-party to this Agreement, including any registrar or registered name holder.

 


7.9


General Notices. Except for notices pursuant to Sections 7.6 and 7.7, all


notices to be given under or in relation to this Agreement will be given either (i) in writing at the address of the appropriate party as set forth below or (ii) via facsimile or electronic mail as provided below, unless that party has given a notice of change of postal or email address, or facsimile number, as provided in this Agreement. All notices under Sections 7.6 and 7.7 shall be given by both posting of the applicable information on ICANN’s web site and transmission of such information to Registry Operator by electronic mail. Any change in the contact information for notice below will be given by the party within thirty (30) calendar days of such change. Other than notices under Sections 7.6 or 7.7, any notice required by this Agreement will be deemed to have been properly given (i) if in paper form, when delivered in person or via courier service with confirmation of receipt or (ii) if via facsimile or by electronic mail, upon confirmation of receipt by the recipient’s facsimile machine or email server, provided that such notice via facsimile or electronic mail shall be followed by a copy sent by regular postal mail service within three (3) calendar days. Any notice required by Sections 7.6 or 7.7 will be deemed to have been given when electronically posted on ICANN’s website and upon confirmation of receipt by the email server.  In the event other means of notice become practically achievable, such as notice via a secure website, the parties will work together to implement such notice means under this Agreement.

 

If to ICANN, addressed to:

Internet Corporation for Assigned Names and Numbers 12025 Waterfront Drive, Suite 300

Los Angeles, CA 90094-2536 USA

Telephone: +1-310-301-5800

Facsimile: +1-310-823-8649 Attention: President and CEO

 

With a Required Copy to: General Counsel Email:  (As specified from time to time.)

 

If to Registry Operator, addressed to:


[                        ]

[                        ]

[                        ]

Dish DBS Corporation 9601 S. Meridian Blvd. Englewood, CO 80112 USA

Telephone: +1-303-723-1725  With a Required Copy to:

Email: (As specified from time to time.)

 

Attention: James Hanft, Director and Sr. Corporate Counsel, IP

 Email: ipdept@dishnetwork.com

 

 


7.10


Entire Agreement.  This Agreement (including those specifications and


documents incorporated by reference to URL locations which form a part of it) constitutes the entire agreement of the parties hereto pertaining to the operation of the TLD and supersedes all prior agreements, understandings, negotiations and discussions, whether oral or written, between the parties on that subject.

 


7.11


English Language Controls. Notwithstanding any translated version of this


Agreement and/or specifications that may be provided to Registry Operator, the English language version of this Agreement and all referenced specifications are the official versions that bind the parties hereto. In the event of any conflict or discrepancy between any translated version of this Agreement and the English language version, the English language version controls. Notices, designations, determinations, and specifications made under this Agreement shall be in the English language.

 


7.12


Ownership Rights. Nothing contained in this Agreement shall be construed


as (a) establishing or granting to Registry Operator any property ownership rights or interests of Registry Operator in the TLD or the letters, words, symbols or other characters making up the TLD string, or (b) affecting any existing intellectual property or ownership rights of Registry Operator.

 


7.13


Severability; Conflicts with Laws. This Agreement shall be deemed


severable; the invalidity or unenforceability of any term or provision of this Agreement shall not affect the validity or enforceability of the balance of this Agreement or of any

other term hereof, which shall remain in full force and effect. If any of the provisions hereof are determined to be invalid or unenforceable, the parties shall negotiate in good faith to modify this Agreement so as to effect the original intent of the parties as closely as possible. ICANN and the Working Group will mutually cooperate to develop an ICANN procedure for ICANN’s review and consideration of alleged conflicts between applicable laws and

non-WHOIS related provisions of this Agreement. Until such procedure is developed and implemented by ICANN, ICANN will review and consider alleged conflicts between


applicable laws and non-WHOIS related provisions of this Agreement in a manner similar to ICANN’s Procedure For Handling WHOIS Conflicts with Privacy Law.

 


7.14


Court Orders. ICANN will respect any order from a court of competent


jurisdiction, including any orders from any jurisdiction where the consent or non-objection of the government was a requirement for the delegation of the TLD. Notwithstanding any other provision of this Agreement, ICANN’s implementation of any such order will not be a breach of this Agreement

 


7.15


Confidentiality


 


(a)


Subject to Section 7.15(c), during the Term and for a period of three


(3) years thereafter, each party shall, and shall cause its and its Affiliates’ officers, directors, employees and agents to, keep confidential and not publish or otherwise disclose to any third party, directly or indirectly, any information that is, and the disclosing party has marked as, or has otherwise designated in writing to the receiving party as, “confidential trade secret,” “confidential commercial information” or “confidential financial information” (collectively, “Confidential Information”), except to the extent such disclosure is permitted by the terms of this Agreement.

 


(b)


The confidentiality obligations under Section 7.15(a) shall not apply


to any Confidential Information that (i) is or hereafter becomes part of the public domain by public use, publication, general knowledge or the like through no fault of the receiving party in breach of this Agreement, (ii) can be demonstrated by documentation or other competent proof to have been in the receiving party’s possession prior to disclosure by the disclosing party without any obligation of confidentiality with respect to such information,

(iii)   is subsequently received by the receiving party from a third party who is not bound by any obligation of confidentiality with respect to such information, (iv) has been published by a third party or otherwise enters the public domain through no fault of the receiving party, or (v) can be demonstrated by documentation or other competent evidence to have been independently developed by or for the receiving party without reference to the disclosing party’s Confidential Information.

 


(c)


Each party shall have the right to disclose Confidential Information to


the extent that such disclosure is (i) made in response to a valid order of a court of competent jurisdiction or, if in the reasonable opinion of the receiving party’s legal counsel, such disclosure is otherwise required by applicable law; provided, however, that the receiving party shall first have given notice to the disclosing party and given the disclosing party a reasonable opportunity to quash such order or to obtain a protective order or confidential treatment order requiring that the Confidential Information that is the subject of such order or other applicable law be held in confidence by such court or other third party recipient, unless the receiving party is not permitted to provide such notice under such order or applicable law, or (ii) made by the receiving party or any of its Affiliates to its or their attorneys, auditors, advisors, consultants, contractors or other third parties for use by such person or entity as may be necessary or useful in connection with the performance of the activities under this Agreement, provided that such third party is bound by


confidentiality obligations at least as stringent as those set forth herein, either by written agreement or through professional responsibility standards.

 

[Note: The following section is applicable to intergovernmental organizations or governmental entities only.]

 

7.16          Special Provision Relating to Intergovernmental Organizations or Governmental Entities.

 

(a)                ICANN acknowledges that Registry Operator is an entity subject to public international law, including international treaties applicable to Registry Operator (such public international law and treaties, collectively hereinafter the “Applicable Laws”).                          Nothing in this Agreement and its related specifications shall be construed or interpreted

to require Registry Operator to violate Applicable Laws or prevent compliance therewith.  The Parties agree that Registry Operator’s compliance with Applicable Laws shall not constitute a breach of this Agreement.

 

(b)               In the event Registry Operator reasonably determines that any provision of this Agreement and its related specifications, or any decisions or policies of ICANN referred to in this Agreement, including but not limited to Temporary Policies and Consensus Policies (such provisions, specifications and policies, collectively hereinafter, “ICANN Requirements”), may conflict with or violate Applicable Law (hereinafter, a “Potential Conflict”), Registry Operator shall provide detailed notice (a “Notice”) of such Potential Conflict to ICANN as early as possible and, in the case of a Potential Conflict with a proposed Consensus Policy, no later than the end of any public comment period on such proposed Consensus Policy. In the event Registry Operator determines that there is Potential Conflict between a proposed Applicable Law and any ICANN Requirement, Registry Operator shall provide detailed Notice of such Potential Conflict to ICANN as early as possible and, in the case of a Potential Conflict with a proposed Consensus Policy, no later than the end of any public comment period on such proposed Consensus Policy.                                           

 

(c)                As soon as practicable following such review, the parties shall attempt to resolve the Potential Conflict by mediation pursuant to the procedures set forth in Section 5.1. In addition, Registry Operator shall use its best efforts to eliminate or

minimize any impact arising from such Potential Conflict between Applicable Laws and any ICANN Requirement. If, following such mediation, Registry Operator determines that the Potential Conflict constitutes an actual conflict between any ICANN Requirement, on the one hand, and Applicable Laws, on the other hand, then ICANN shall waive compliance with such ICANN Requirement (provided that the parties shall negotiate in good faith on a continuous basis thereafter to mitigate or eliminate the effects of such noncompliance on ICANN), unless ICANN reasonably and objectively determines that the failure of Registry Operator to comply with such ICANN Requirement would constitute a threat to the Security and Stability of Registry Services, the Internet or the DNS (hereinafter, an “ICANN Determination”). Following receipt of notice by Registry Operator of such ICANN Determination, Registry Operator shall be afforded a period of ninety (90) calendar days to resolve such conflict with an Applicable Law. If the conflict with an Applicable Law is not


resolved to ICANN’s complete satisfaction during such period, Registry Operator shall have the option to submit, within ten (10) calendar days thereafter, the matter to binding arbitration as defined in subsection (d) below. If during such period, Registry Operator does not submit the matter to arbitration pursuant to subsection (d) below, ICANN may, upon notice to Registry Operator, terminate this Agreement with immediate effect.

 

(d)               If Registry Operator disagrees with an ICANN Determination, Registry Operator may submit the matter to binding arbitration pursuant to the provisions of Section 5.2, except that the sole issue presented to the arbitrator for determination will be whether or not ICANN reasonably and objectively reached the ICANN Determination. For the purposes of such arbitration, ICANN shall present evidence to the arbitrator supporting the ICANN Determination. If the arbitrator determines that ICANN did not reasonably and objectively reach the ICANN Determination, then ICANN shall waive Registry Operator’s compliance with the subject ICANN Requirement. If the arbitrators or pre-arbitral referee, as applicable, determine that ICANN did reasonably and objectively reach the ICANN Determination, then, upon notice to Registry Operator, ICANN may terminate this Agreement with immediate effect.                      

 

(e)                Registry Operator hereby represents and warrants that, to the best of its knowledge as of the date of execution of this Agreement, no existing ICANN Requirement conflicts with or violates any Applicable Law.                         

 

(f)                Notwithstanding any other provision of this Section 7.16, following an ICANN Determination and prior to a finding by an arbitrator pursuant to Section 7.16(d) above, ICANN may, subject to prior consultations with Registry Operator, take such reasonable technical measures as it deems necessary to ensure the Security and Stability of Registry Services, the Internet and the DNS. These reasonable technical measures shall be taken by ICANN on an interim basis, until the earlier of the date of conclusion of the arbitration procedure referred to in Section 7.16(d) above or the date of complete resolution of the conflict with an Applicable Law. In case Registry Operator disagrees with such technical measures taken by ICANN, Registry Operator may submit the matter to binding arbitration pursuant to the provisions of Section 5.2 above, during which process ICANN may continue to take such technical measures. In the event that ICANN takes such measures, Registry Operator shall pay all costs incurred by ICANN as a result of taking such measures. In addition, in the event that ICANN takes such measures, ICANN shall retain and may enforce its rights under the Continued Operations Instrument and Alternative Instrument, as applicable.

 

* * * * *


IN WITNESS WHEREOF, the parties hereto have caused this Agreement to be executed by their duly authorized representatives.

 

INTERNET CORPORATION FOR ASSIGNED NAMES AND NUMBERS

 

By:                                                 

            [                    ]

            President and CEO

            Date:

 

 

[Registry Operator]

 

 

 

By:                                                 

[                  ]

            [                  ]

            Date: By:

Akram Atallah

President, Global Domains Division

 

 

Dish DBS Corporation

 


By:


Robert Stanton Dodge