Common use of Registrars Clause in Contracts

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 <xxxx://xxx.xxxxx.xxx/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.

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 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 <xxxx://xxx.xxxxx.xxx/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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry- Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/en/resources/registries/rra-amendment-procedure>, and such revisions may not be adopted and implemented until approved by ICANN. (b) . Notwithstanding the foregoing provisions of this Section 2.9(a), any change to the Registry-Registrar Agreement that relates exclusively to the fee charged by Registry Operator to register domain names in the TLD will not be subject to the notice and approval process specified in this Section 2.9(a), but will be subject to the requirements in Section 2.10 below. 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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/en/resources/registries/rra-amendment-procedure>, and such revisions may not be adopted and implemented until approved by ICANN. Notwithstanding the foregoing provisions of this Section 2.9(a), any change to the Registry-Registrar Agreement that relates exclusively to the fee charged by Registry Operator to register domain names in the TLD will not be subject to the notice and approval process specified in this Section 2.9(a), but will be subject to the requirements in Section 2.10 below. (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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry- Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/en/resources/registries/rra-amendment-procedure>, and such revisions may not be adopted and implemented until approved by ICANN. Notwithstanding the foregoing provisions of this Section 2.9(a), any change to the Registry- Registrar Agreement that relates exclusively to the fee charged by Registry Operator to register domain names in the TLD will not be subject to the notice and approval process specified in this Section 2.9(a), but will be subject to the requirements in Section 2.10 below. (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.

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 non‐discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry‐registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non‐discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry‐Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry‐Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/en/resources/registries/rra‐amendment‐procedure>, and such revisions may not be adopted and implemented until approved by ICANN. Notwithstanding the foregoing provisions of this Section 2.9(a), any change to the Registry‐Registrar Agreement that relates exclusively to the fee charged by Registry Operator to register domain names in the TLD will not be subject to the notice and approval process specified in this Section 2.9(a), but will be subject to the requirements in Section 2.10 below. (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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry- Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedure>xxxxx://xxx.xxxxx.xxx/rra- amendment-procedure, and such revisions may not be adopted and implemented until approved by ICANN. Notwithstanding the foregoing provisions of this Section 2.9(a), any change to the Registry-Registrar Agreement that relates exclusively to the fee charged by Registry Operator to register domain names in the TLD will not be subject to the notice and approval process specified in this Section 2.9(a), but will be subject to the requirements in Section 2.10 below. (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.

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 non‐discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry‐registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non‐discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry‐ Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry‐Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/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.

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 <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedure>, and such revisions may not be adopted and implemented until approved by ICANN. . Within sixty (b60) If calendar days of the RAA Adoption Date, as that term is defined herein below, Registry Operator will submit to ICANN for approval an amended version of the Registry-­‐Registrar Agreement (“Amended RAA”) in accordance with the provisions below, which will include a provision requiring all ICANN-­‐accredited registrars who are a party to Registry Operator’s Registry-­‐Registrar Agreement either to (i) becomes an Affiliate or reseller become a party to the form registrar accreditation agreement adopted by the ICANN Board of an ICANN accredited registrarDirectors on 27 June 2013 (the “2013 RAA”) within two hundred seventy (270) calendar days after the effective date of the Amended RRA, or (ii) subcontracts the provision of any be Suspended (as defined below) by Registry Services to an ICANN accredited registrar, registrar reseller or any of their respective Affiliates, then, in either Operator. Once such case of (i) or (ii) aboveAmended RRA is approved by ICANN, Registry Operator will give ICANN prompt notice shall promptly adopt and require each of the contract, transaction or other arrangement ICANN-­‐accredited registrars that resulted access Registry Services for the TLD to enter into the Amended RRA pursuant to the amendment procedures set forth in such affiliation, reseller relationship or subcontract, Registry Operator’s Registry-­‐Registrar Agreement in effect 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)the date hereof. ICANN reserves the right, but not the obligation, to refer any such contract, related documents, transaction or other arrangement to relevant competition authorities in In the event that any such registrar does not enter the 2013 RAA with ICANN determines that within such contracttwo hundred seventy (270) calendar day period, 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 is notified of that fact by ICANN in writing (a competition authority. (c) For the purposes of this Agreement: (i) “Affiliate” means a person or entity thatNon-­‐Compliant Registrar”), 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.then Registry Operator will Suspend the

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry- Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxxx://xxx.xxxxx.xxx/en/resources/registries/rra-amendment-procedure>, and such revisions may not be adopted and implemented until approved by ICANN. Notwithstanding the foregoing provisions of this Section 2.9(a), any change to the Registry- Registrar Agreement that relates exclusively to the fee charged by Registry Operator to register domain names in the TLD will not be subject to the notice and approval process specified in this Section 2.9(a), but will be subject to the requirements in Section 2.10 below. (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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/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.

Registrars. (a) All domain name registrations in the TLD Registry Operator must be registered through an use only ICANN accredited registrar; provided, that Registry Operator need not use a registrar if it registers names registrars in its own name in order to withhold such names from delegation or use in accordance with Section 2.6registering domain names. Subject to the requirements of Specification 11, Registry Operator must provide non-­‐discriminatory non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided provided, that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Agreement”)TLD. Such agreement may be revised by Registry Operator may amend the Registry-­‐Registrar Agreement from time to time; provided, however, that any material such 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 <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedure>, and such revisions may not be adopted and implemented until approved advance 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 not disclose such contract and related documents contracts to any third party other than 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 authorityissues. (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.

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 non‐discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry‐registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non‐discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry‐Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry‐Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/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.

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 nonMdiscriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registryMregistrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory nonMdiscriminatory 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 nonMdiscriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar RegistryM Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar RegistryMRegistrar 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 RegistryMRegistrar 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 calendarMday 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 RegistryMRegistrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/en/resources/registries/rraMamendmentMprocedure>, 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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedure>xxxxx://xxx.xxxxx.xxx/rra-amendment-procedure, and such revisions may not be adopted and implemented until approved by ICANN. (b) . Notwithstanding the foregoing provisions of this Section 2.9(a), any change to the Registry-Registrar Agreement that relates exclusively to the fee charged by Registry Operator to register domain names in the TLD will not be subject to the notice and approval process specified in this Section 2.9(a), but will be subject to the requirements in Section 2.10 below. 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.

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 nonLdiscriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registryLregistrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory nonLdiscriminatory 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 nonLdiscriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar RegistryLRegistrar Agreement”). Registry Operator may amend the Registry-­‐Registrar RegistryLRegistrar 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 RegistryLRegistrar 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 calendarLday 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 RegistryLRegistrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/en/resources/registries/rraLamendmentLprocedure>, 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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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. Within sixty (60) calendar days of the RAA Adoption Date, as that term is defined herein below, Registry Operator will provide submit to ICANN and for approval an amended version of the Registry-Registrar Agreement (“Amended RAA”) in accordance with the provisions below, which will include a provision requiring all ICANN-accredited registrars authorized who are a party to register names in Registry Operator’s Registry-Registrar Agreement either to (i) become a party to the TLD at least fifteen form registrar accreditation agreement adopted by the ICANN Board of Directors on 27 June 2013 (15the “2013 RAA”) within two hundred seventy (270) calendar days written notice after the effective date 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 <xxxx://xxx.xxxxx.xxx/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 registrarAmended RRA, or (ii) subcontracts the provision of any be Suspended (as defined below) by Registry Services to an ICANN accredited registrar, registrar reseller or any of their respective Affiliates, then, in either Operator. Once such case of (i) or (ii) aboveAmended RRA is approved by ICANN, Registry Operator will give ICANN prompt notice shall promptly adopt and require each of the contract, transaction or other arrangement ICANN-accredited registrars that resulted access Registry Services for the TLD to enter into the Amended RRA pursuant to the amendment procedures set forth in such affiliation, reseller relationship or subcontract, Registry Operator’s Registry-Registrar Agreement in effect 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)the date hereof. ICANN reserves the right, but not the obligation, to refer any such contract, related documents, transaction or other arrangement to relevant competition authorities in In the event that any such registrar does not enter the 2013 RAA with ICANN determines that within such contracttwo hundred seventy (270) calendar day period, 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 is notified of that fact by ICANN in writing (a “Non-Compliant Registrar”), then Registry Operator will Suspend the Non-Compliant Registrar until such time as such Non-Compliant Registrar becomes a party to making any such referral to a competition authority. (c) For the purposes of this Agreement: (i) 2013 RAA. “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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry- Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 days’ written notice of any revisions to the Registry-­‐Registrar 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/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.

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 non-discriminatory access to Registry Services to all ICANN allICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 days’ written notice of any revisions to the Registry-­‐Registrar 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/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 orrelated 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 relevantcompetition 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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry- registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/en/resources/registries/rra- amendment-procedure>, and such revisions may not be adopted and implemented until approved by ICANN. Notwithstanding the foregoing provisions of this Section 2.9(a), any change to the Registry-Registrar Agreement that relates exclusively to the fee charged by Registry Operator to register domain names in the TLD will not be subject to the notice and approval process specified in this Section 2.9(a), but will be subject to the requirements in Section 2.10 below. (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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxxx://xxx.xxxxx.xxx/en/resources/registries/rra-amendment-procedure>, and such revisions may not be adopted and implemented until approved by ICANN. Notwithstanding the foregoing provisions of this Section 2.9(a), any change to the Registry-Registrar Agreement that relates exclusively to the fee charged by Registry Operator to register domain names in the TLD will not be subject to the notice and approval process specified in this Section 2.9(a), but will be subject to the requirements in Section 2.10 below. (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.

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 non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar registry-registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory 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 non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Registry-Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar 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 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 Revision enables Registry Operator to change the pricing terms of the Registry-Registrar Agreement without seeking ICANN’s approval since the Registry Agreement does not specify a specific price for domain names registration (see rationale for Section 2.10 below). Section Change to Text Comments and Rationale Registry Operator with notice of its determination within such fifteen (15) calendar-­‐day 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 Registry-Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedurexxxx://xxx.xxxxx.xxx/en/resources/registries/rra- amendment-procedure>, and such revisions may not be adopted and implemented until approved by ICANN. (b) If . Notwithstanding the foregoing provisions of this Section 2.9(a), any change to the Registry-Registrar Agreement that relates exclusively to the fee charged by Registry Operator (i) becomes an Affiliate or reseller of an ICANN accredited registrar, or (ii) subcontracts to register domain names in the provision of any Registry Services TLD will not be subject to an ICANN accredited registrar, registrar reseller or any of their respective Affiliates, then, the notice and approval process specified 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 this 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 authorities2.9(a). ICANN reserves the right, but not will be subject to the obligation, to refer any such contract, related documents, transaction or other arrangement to relevant competition authorities requirements 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 authoritySection 2.10 below. (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.