Common use of Registration Restrictions Clause in Contracts

Registration Restrictions. (A) Registry Operator shall establish registration policies with respect to the TLD for (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, with respect to disputes arising pursuant to this Section 3.1(c)(i)(A). Registry Operator shall implement and comply with the community registration policies and other terms set forth on Specification 12 attached hereto. (B) Sponsor shall reserve, and not register any TLD strings appearing on the list of reserved TLD strings attached as Specification 5 hereto (“Specification 5”). Except to the extent ICANN otherwise authorizes in writing, Sponsor shall comply with the requirements of Specification 5. Sponsor may at any time establish or modify policies concerning Sponsor’s ability to reserve (i.e., withhold from registration or allocate to Sponsor, but not register to third parties, delegate, use, activate in the DNS or otherwise make available) or block additional character strings within the TLD at its discretion. Except as specified in Specification 5, if Sponsor is the registrant for any domain names in the registry TLD, such registrations must be through an ICANN accredited registrar, and will be considered transactions for purposes of calculating the Registry-Level Transaction Fee to be paid to ICANN by Sponsor pursuant to Section 7.2.

Registration Restrictions. (A) Registry Operator shall establish registration policies with respect to the TLD for (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, with respect to disputes arising pursuant to this Section 3.1(c)(i)(A). Registry Operator shall implement and comply with the community registration policies and other terms set forth on Specification 12 attached hereto. (B) Sponsor Registry Operator shall reserve, and not register any TLD strings appearing on the list of reserved TLD strings attached as Specification 5 hereto (“Specification 5”). Except to the extent ICANN otherwise authorizes in writing, Sponsor Registry Operator shall comply with the requirements of Specification 5. Sponsor Registry Operator may at any time establish or modify policies concerning SponsorRegistry Operator’s ability to reserve (i.e., withhold from registration or allocate to SponsorRegistry Operator, but not register to third parties, delegate, use, activate in the DNS or otherwise make available) or block additional character strings within the TLD at its discretion. Except as specified in Specification 5, if Sponsor Registry Operator is the registrant for any domain names in the registry TLD, such registrations must be through an ICANN accredited registrar, and will be considered transactions for purposes of calculating the Registry-Level Transaction Fee to be paid to ICANN by Sponsor Registry Operator pursuant to Section 7.2.

Registration Restrictions. (A) Sponsor shall be responsible for establishing policies, in conformity with the Charter, for the naming conventions within the sponsored TLD and for requirements of registration, consistent with Section 3.1(g). (A) Registry Operator shall establish registration policies with respect to the TLD for (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, with respect to disputes arising pursuant to this Section 3.1(c)(i)(A). Registry Operator shall implement and comply with the community registration policies and other terms set forth on Specification 12 attached hereto. (B) Sponsor shall be responsible for establishing procedures for the enforcement of applicable Charter restrictions on registration within the TLD, as described in more detail in the sponsored TLD Charter attached as Part I to Appendix S. (B) Sponsor shall reserve, and not register any TLD strings appearing on the list of reserved TLD strings attached as Specification 5 hereto (“Specification 5”). Except to the extent ICANN otherwise authorizes in writing, Sponsor shall comply with the requirements of Specification 5. Sponsor may at any time establish or modify policies concerning Sponsor’s ability to reserve (i.e., withhold from registration or allocate to Sponsor, but not register to third parties, delegate, use, activate in the DNS or otherwise make available) or block additional character strings within the TLD at its discretion. Except as specified in Specification 5, if Sponsor is the registrant for any domain names in the registry TLD, such registrations must be through an ICANN accredited registrar, and will be considered transactions for purposes of calculating the Registry-Level Transaction Fee to be paid to ICANN by Sponsor pursuant to Section 7.2. (C) Sponsor shall reserve, and not register any TLD strings (i) appearing on the list of reserved TLD strings attached as Appendix 6 hereto or (ii) located at xxxx://xxxx.xxxx.xxx/TLD/tlds-alpha- bydomain.txt for initial (i.e., other than renewal) registration at the second level within the TLD. (ii) Use of ICANN-Accredited Registrars. Sponsor shall ensure that all Approved Services are provided through one or more ICANN-Accredited Registrars, except to the extent that (a) Specification 12 – Part II delegates to Sponsor the authority to provide or to arrange for the provision of ENS Services by means other than ICANN-Accredited Registrars or (b) the Sponsor provides for a different means of providing Approved Services in accordance with its delegation of authority and with the consent of its community and ICANN, such consent not being unreasonably withheld. Sponsor shall ensure that Registry-Registrar Agreements are in conformance with Section 7.1 of this Agreement.