Common use of Post-Registration Complaint Investigation Clause in Contracts

Post-Registration Complaint Investigation. Registry Operator shall take reasonable steps to investigate and respond to any reports from governmental agencies and ccTLD operators of conduct that causes confusion with the corresponding country code in connection with the use of a letter/letter two-character ACSCII domain. In responding to such reports, Registry Operator will not be required to take any action in contravention of applicable law.” 1.1 The terms of Section 3.1.1 of Specification 5 are hereby amended and restated in their entirety as follows: “If Exhibit A to the Agreement specifically provides that Registry Operator may offer registration of IDNs, Registry Operator may also activate a language-specific translation or transliteration of the term "NIC" or an abbreviation for the translation of the term "Network Information Center" in the DNS in accordance with Registry Operator’s IDN Tables and IDN Registration Rules. Such translation, transliteration or abbreviation may be reserved by Registry Operator and used in addition to the label NIC to provide any required registry functions. For the avoidance of doubt, Registry Operator is required to activate the ASCII label NIC pursuant to Section 3.1 of this Specification 5.” Specification 5, § 3.2 The terms of Section 3.2 of Specification 5 shall be of no force or effect. Specification 5, § 3.4 The terms of Section 3.4 of Specification 5 are hereby amended and restated in their entirety as follows: “Registry Operator shall allocate the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar (as such registrar is described in Section 8.2 of Specification 10). If such domain name is not available for registration in the TLD or is otherwise inconsistent with the registration policies of the TLD, Registry Operator may allocate a different domain name to the ICANN testing registrar in consultation with ICANN. The allocation of any such alternative domain name will be communicated to ICANN following such consultation. The allocation of the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar will not be considered a Transaction for purposes of Section 6.1 of the Agreement.” Specification 5, § 5 The terms of Section 5 of Specification 5 shall be of no force or effect. Specification 5, § 6 The terms of Section 6 of Specification 5 shall be of no force or effect. Specification 6, § 6 The terms of Section 6 of Specification 6 shall be of no force or effect.

Post-Registration Complaint Investigation. Registry Operator shall take reasonable steps to investigate and respond to any reports from governmental agencies and ccTLD operators of conduct that causes confusion with the corresponding country code in connection with the use of a letter/letter two-character ACSCII domain. In responding to such reports, Registry Operator will not be required to take any action in contravention of applicable law.” 1.1 The terms of Section 3.1.1 of Specification 5 are hereby amended and restated in their entirety as follows: “If Exhibit A to the Agreement specifically provides that Registry Operator may offer registration of IDNs, Registry Operator may also activate a language-specific translation or transliteration of the term "NIC" or an abbreviation for the translation of the term "Network Information Center" in the Section Addendum Terms DNS in accordance with Registry Operator’s IDN Tables and IDN Registration Rules. Such translation, transliteration or abbreviation may be reserved by Registry Operator and used in addition to the label NIC to provide any required registry functions. For the avoidance of doubt, Registry Operator is required to activate the ASCII label NIC pursuant to Section 3.1 of this Specification 5.” Specification 5, § 3.2 The terms of Section 3.2 of Specification 5 shall be of no force or effect. Specification 5, § 3.4 The terms of Section 3.4 of Specification 5 are hereby amended and restated in their entirety as follows: “Registry Operator shall allocate the domain name “icann-sla-sla- monitoring.<tld>” to the ICANN testing registrar (as such registrar is described in Section 8.2 of Specification 10). If such domain name is not available for registration in the TLD or is otherwise inconsistent with the registration policies of the TLD, Registry Operator may allocate a different domain name to the ICANN testing registrar in consultation with ICANN. The allocation of any such alternative domain name will be communicated to ICANN following such consultation. The allocation of the domain name “icann-sla-sla- monitoring.<tld>” to the ICANN testing registrar will not be considered a Transaction for purposes of Section 6.1 of the Agreement.” Specification 5, § 5 The terms of Section 5 of Specification 5 shall be of no force or effect. Specification 5, § 6 The terms of Section 6 of Specification 5 shall be of no force or effect. Specification 6, § 6 The terms of Section 6 of Specification 6 shall be of no force or effect.

Post-Registration Complaint Investigation. Registry Operator shall take reasonable steps to investigate and respond to any reports from governmental agencies and ccTLD operators of conduct that causes confusion with the corresponding country code in connection with the use of a letter/letter two-character ACSCII domain. In responding to such reports, Registry Operator will not be required to take any action in contravention of applicable law.” 1.1 The terms of Section 3.1.1 of Specification 5 are hereby amended and restated in their entirety as follows: “If Exhibit A to the Agreement specifically provides that Registry Operator may offer registration of IDNs, Registry Operator may also activate a language-specific translation or transliteration of the term "NIC" or an abbreviation for the translation of the term "Network Information Center" in the DNS in accordance with Registry Operator’s IDN Tables and IDN Registration Rules. Such translation, transliteration or abbreviation may be reserved by Registry Operator and used in addition to the label NIC to provide any required registry functions. For the avoidance of doubt, Registry Operator is required to activate the ASCII label NIC pursuant to Section 3.1 of this Specification 5.” Specification 5, § 3.2 The terms of Section 3.2 of Specification 5 shall be of no force or effect. Specification 5, § 3.4 The terms of Section 3.4 of Specification 5 are hereby amended and restated in their entirety as follows: “Registry Operator shall allocate the domain name “icann-sla-sla- monitoring.<tld>” to the ICANN testing registrar (as such registrar is described in Section 8.2 of Specification 10). If such domain name is not available for registration in the TLD or is otherwise inconsistent with the registration policies of the TLD, Section Addendum Terms Registry Operator may allocate a different domain name to the ICANN testing registrar in consultation with ICANN. The allocation of any such alternative domain name will be communicated to ICANN following such consultation. The allocation of the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar will not be considered a Transaction for purposes of Section 6.1 of the Agreement.” Specification 5, § 5 The terms of Section 5 of Specification 5 shall be of no force or effect. Specification 5, § 6 The terms of Section 6 of Specification 5 shall be of no force or effect. Specification 6, § 6 The terms of Section 6 of Specification 6 shall be of no force or effect.

Post-Registration Complaint Investigation. Registry Operator shall take reasonable steps to investigate and respond to any reports from governmental agencies and ccTLD operators of conduct that causes confusion with the corresponding country code in connection with the use of a letter/letter two-character ACSCII domain. In responding to such reports, Registry Operator will not be required to take any action in contravention of applicable law.” 1.1 The terms of Section 3.1.1 of Specification 5 are hereby amended and restated in their entirety as follows: “If Exhibit A to the Agreement specifically provides that Registry Operator may offer registration of IDNs, Registry Operator may also activate a language-specific translation or transliteration of the term "NIC" or an abbreviation for the translation of the term "Network Information Center" in the DNS in accordance with Registry Operator’s IDN Tables and IDN Registration Rules. Such translation, transliteration or abbreviation may be reserved by Registry Operator and used in addition to the label NIC to provide any required registry functions. For the avoidance of doubt, Registry Operator is required to activate the ASCII label NIC pursuant to Section 3.1 of this Specification 5.” Specification 5, § 3.2 The terms of Section 3.2 of Specification 5 shall be of no force or effect. Specification 5, § 3.4 The following terms of the first sentence of Section 3.4 of Specification 5 are hereby amended and restated in their entirety as followsshall be of no force or effect: “Registry Operator shall allocate Effective upon the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar (as such registrar is described in Section 8.2 of Specification 10). If such domain name is not available for registration in the TLD or is otherwise inconsistent with the registration policies conclusion of the TLD, Registry Operator may allocate a different domain name to the ICANN testing registrar No-Activation Period specified in consultation with ICANN. The allocation of any such alternative domain name will be communicated to ICANN following such consultation. The allocation of the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar will not be considered a Transaction for purposes of Section 6.1 of Specification 6,” The following terms of the Agreement.last sentence of Section 3.4 of Specification 5 shall be of no force or effect: • “(i)” • “, (ii) count towards the one hundred domain names available to Registry Operator under Section 3.2 of this Section Addendum Terms Specification 5, or (iii) adversely affect Registry Operator’s qualification as a .BRAND TLD pursuant to Specification 13 (.BRAND TLD Provisions) hereto (as applicable)” Specification 5, § 5 The terms of Section 5 of Specification 5 shall be of no force or effect. Specification 5, § 6 The terms of Section 6 of Specification 5 shall be of no force or effect. Specification 6, § 6 The terms of Section 6 of Specification 6 shall be of no force or effect.. Specification 7, § 1 The following term in the second sentence of Section 1 of Specification 7 shall be of no force or effect: “additional” The following terms of Section 1 of Specification 7 shall be of no force of effect: “Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxxx://xxx.xxxxx.xxx/en/resources/registries/tmch- requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry- Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements),

Post-Registration Complaint Investigation. Registry Operator shall take reasonable steps to investigate and respond to any reports from governmental agencies and ccTLD operators of conduct that causes confusion with the corresponding country code in connection with the use of a letter/letter two-character ACSCII domain. In responding to such reports, Registry Operator will not be required to take any action in contravention of applicable law.” 1.1 The terms of Section 3.1.1 of Specification 5 are hereby amended and restated in their entirety as follows: “If Exhibit A to the Agreement specifically provides that Registry Operator may offer registration of IDNs, Registry Operator may also activate a language-specific translation or transliteration of the term "NIC" or an abbreviation for the Section Addendum Terms translation of the term "Network Information Center" in the DNS in accordance with Registry Operator’s IDN Tables and IDN Registration Rules. Such translation, transliteration or abbreviation may be reserved by Registry Operator and used in addition to the label NIC to provide any required registry functions. For the avoidance of doubt, Registry Operator is required to activate the ASCII label NIC pursuant to Section 3.1 of this Specification 5.” Specification 5, § 3.2 The terms of Section 3.2 of Specification 5 shall be of no force or effect. Specification 5, § 3.4 The terms of Section 3.4 of Specification 5 are hereby amended and restated in their entirety as follows: “Registry Operator shall allocate the domain name “icann-sla-sla- monitoring.<tld>” to the ICANN testing registrar (as such registrar is described in Section 8.2 of Specification 10). If such domain name is not available for registration in the TLD or is otherwise inconsistent with the registration policies of the TLD, Registry Operator may allocate a different domain name to the ICANN testing registrar in consultation with ICANN. The allocation of any such alternative domain name will be communicated to ICANN following such consultation. The allocation of the domain name “icann-sla-sla- monitoring.<tld>” to the ICANN testing registrar will not be considered a Transaction for purposes of Section 6.1 of the Agreement.” Specification 5, § 5 The terms of Section 5 of Specification 5 shall be of no force or effect. Specification 5, § 6 The terms of Section 6 of Specification 5 shall be of no force or effect. Specification 6, § 6 The terms of Section 6 of Specification 6 shall be of no force or effect.

Post-Registration Complaint Investigation. Registry Operator shall take reasonable steps to investigate and respond to any reports from governmental agencies and ccTLD operators of conduct that causes confusion with the corresponding country code in connection with the use of a letter/letter two-character ACSCII domain. In responding to such reports, Registry Operator will not be required to take any action in contravention of applicable law.” 1.1 The terms of Section 3.1.1 of Specification 5 are hereby amended and restated in their entirety as follows: “If Exhibit A to the Agreement specifically provides that Registry Operator may offer registration of IDNs, Registry Operator may also activate a language-specific translation or transliteration of the term "NIC" or an abbreviation for the translation of the term "Network Information Center" in the DNS in accordance with Registry Operator’s IDN Tables and IDN Registration Rules. Such translation, transliteration or abbreviation may be reserved by Registry Operator and used in addition to the label NIC to provide any required registry functions. For the avoidance of doubt, Registry Operator is required to activate the ASCII label NIC pursuant to Section 3.1 of this Specification 5.” Specification 5, § 3.2 The terms of Section 3.2 of Specification 5 shall be of no force or effect. Specification 5, § 3.4 The following terms of the first sentence of Section 3.4 of Specification 5 are hereby amended and restated in their entirety as followsshall be of no force or effect: “Registry Operator shall allocate Effective upon the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar (as such registrar is described in Section 8.2 of Specification 10). If such domain name is not available for registration in the TLD or is otherwise inconsistent with the registration policies conclusion of the TLD, Registry Operator may allocate a different domain name to the ICANN testing registrar No-Activation Period specified in consultation with ICANN. The allocation of any such alternative domain name will be communicated to ICANN following such consultation. The allocation of the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar will not be considered a Transaction for purposes of Section 6.1 of Specification 6,” The following terms of the Agreement.last sentence of Section 3.4 of Specification 5 shall be of no force or effect: “(i)” “, (ii) count towards the one hundred domain names available to Registry Operator under Section 3.2 of this Specification 5, or (iii) adversely affect Registry Operator’s qualification as a .BRAND TLD pursuant to Specification 13 (.BRAND TLD Provisions) hereto (as applicable)” Specification 5, § 5 The terms of Section 5 of Specification 5 shall be of no force or effect. Specification 5, § 6 The terms of Section 6 of Specification 5 shall be of no force or effect. Specification 6, § 6 The terms of Section 6 of Specification 6 shall be of no force or effect. Specification 7, § 1 The following term in the second sentence of Section 1 of Specification 7 shall be of no force or effect: “additional” The following terms of Section 1 of Specification 7 shall be of no force of effect: “Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13).” Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.” Specification 8 The terms of Specification 8 shall be of no force or effect. Specification 9, § 1(b) The following terms of Section 1(b) of Specification 9 shall be of no force or effect: “(a)” “and (b) may withhold from registration or allocate to Registry Operator up to one hundred (100) names pursuant to Section 3.2 of Specification 5” Unless a different implementation period is provided in the Registry Agreement, Registry Operator will have a 270 calendar days grace period, beginning on the Effective Date, to work with ICANN and backend providers to ensure that all additional or changed technical operations between the Agreement and the Previous Registry Agreement are implemented. For the avoidance of doubt, Registry Operator shall continue to comply with all existing technical operation requirements of the Previous Registry Agreement until Registry Operator has implemented the applicable additional or changed technical operation requirements and any breach of such existing provision shall be deemed a breach of the Registry Agreement. This Addendum shall constitute an integral part of the Registry Agreement. Notwithstanding Section 7.10 of the Registry Agreement, the Registry Agreement (including those specifications and documents incorporated by reference to URL locations which form a part of it) and this Addendum constitute the entire agreement of the parties hereto pertaining to the operation of the TLD and supersedes all prior agreements, understandings, negotiations and discussions, whether oral or written, between the parties on that subject. The Registry Agreement and this Addendum shall at all times be read together. Except as specifically provided for in this Addendum, all of the terms of the Registry Agreement shall remain unchanged and in full force and effect, and, to the extent applicable, such terms shall apply to this Addendum as if it formed part of the Registry Agreement. This Addendum may be executed and delivered (including by electronic transmission) in any number of counterparts, and by the different parties hereto in separate counterparts, each of which when executed shall be deemed to be an original but all of which taken together shall constitute a single instrument.

Post-Registration Complaint Investigation. Registry Operator shall take reasonable steps to investigate and respond to any reports from governmental agencies and ccTLD operators of conduct that causes confusion with the corresponding country code in connection with the use of a letter/letter two-character ACSCII domain. In responding to such reports, Registry Operator will not be required to take any action in contravention of applicable law.” 1.1 The terms of Section 3.1.1 of Specification 5 are hereby amended and restated in their entirety as follows: “ 3.1.1 If Exhibit A to the Agreement specifically provides that Registry Operator may offer registration of IDNs, Registry Operator may also activate a language-specific translation or transliteration of the term "NIC" or an abbreviation for the translation of the term "Network Information Center" in the DNS in accordance with Registry Operator’s IDN Tables and IDN Registration Rules. Such translation, transliteration or abbreviation may be reserved by Registry Operator and used in addition to the label NIC to provide any required registry functions. For the avoidance of doubt, Registry Operator is required to activate the ASCII label NIC pursuant to Section 3.1 of this Specification 5.” Specification 5, § 3.2 The terms of Section 3.2 of Specification 5 shall be of no force or effect. Specification 5, § 3.4 The terms of Section 3.4 of Specification 5 are hereby amended and restated in their entirety as follows: “Registry Operator shall allocate the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar (as such registrar is described in Section 8.2 of Specification 10). If such domain name is not available for registration in the TLD or is otherwise inconsistent with the registration policies of the TLD, Registry Operator may allocate a different domain name to the ICANN testing registrar in consultation with ICANN. The allocation of any such alternative domain name will be communicated to ICANN following such consultation. The allocation of the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar will not be considered a Transaction for purposes of Section 6.1 of the Agreement.” Specification 5, § 5 The terms of Section 5 of Specification 5 shall be of no force or effect. Specification 5, § 6 The terms of Section 6 of Specification 5 shall be of no force or effect. Specification 6, § 6 The terms of Section 6 of Specification 6 shall be of no force or effect.

Post-Registration Complaint Investigation. Registry Operator shall take reasonable steps to investigate and respond to any reports from governmental agencies and ccTLD operators of conduct that causes confusion with the corresponding country code in connection with the use of a letter/letter two-character ACSCII domain. In responding to such reports, Registry Operator will not be required to take any action in contravention of applicable law.” 1.1 The terms of Section 3.1.1 of Specification 5 are hereby amended and restated in their entirety as follows: “If Exhibit A to the Agreement specifically provides that Registry Operator may offer registration of IDNs, Registry Operator may also activate a language-specific translation or transliteration of the term "NIC" or an abbreviation for the translation of the term "Network Information Center" in the DNS in accordance with Registry Operator’s IDN Tables and IDN Registration Rules. Such translation, transliteration or abbreviation may be reserved by Registry Operator and used in addition to the label NIC to provide any required registry functions. For the avoidance of doubt, Registry Operator is required to activate the ASCII label NIC pursuant to Section 3.1 of this Specification 5.” Specification 5, § 3.2 The terms of Section 3.2 of Specification 5 shall be of no force or effect. Specification 5, § 3.4 The following terms of the first sentence of Section 3.4 of Specification 5 are hereby amended and restated in their entirety as followsshall be of no force or effect: “Registry Operator shall allocate Effective upon the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar (as such registrar is described in Section 8.2 of Specification 10). If such domain name is not available for registration in the TLD or is otherwise inconsistent with the registration policies conclusion of the TLD, Registry Operator may allocate a different domain name to the ICANN testing registrar No-Activation Period specified in consultation with ICANN. The allocation of any such alternative domain name will be communicated to ICANN following such consultation. The allocation of the domain name “icann-sla-monitoring.<tld>” to the ICANN testing registrar will not be considered a Transaction for purposes of Section 6.1 of Specification 6,” The following terms of the Agreement.last sentence of Section 3.4 of Specification 5 shall be of no force or effect: • “(i)” • “, (ii) count towards the one hundred domain names available to Registry Operator under Section 3.2 of this Specification 5, § 5 or (iii) adversely affect Registry Operator’s qualification as a .BRAND TLD pursuant to Specification 13 (.BRAND TLD Provisions) hereto (as applicable)” Specification The terms of Section 5 of Specification 5 shall be of no force or 5, § 5 effect. Specification 5, § 6 The terms of Section 6 of Specification 5 shall be of no force or effect. Specification 6, § 6 The terms of Section 6 of Specification 6 shall be of no force or effect. Specification 7, § 1 The following term in the second sentence of Section 1 of Specification 7 shall be of no force or effect: “additional” The following terms of Section 1 of Specification 7 shall be of no force of effect: “Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxxx://xxx.xxxxx.xxx/en/resources/registries/tmch- requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry- Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any Section Addendum Terms domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13).” Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.” Specification 8 The terms of Specification 8 shall be of no force or effect. Specification 9, § 1(b) The following terms of Section 1(b) of Specification 9 shall be of no force or effect: • “(a)” • “and (b) may withhold from registration or allocate to Registry Operator up to one hundred (100) names pursuant to Section 3.2 of Specification 5”