Common use of Reservations for Registry Operations Clause in Contracts

Reservations for Registry Operations. 2.1 ▇▇▇▇▇ may activate in the DNS at All Levels up to one hundred (1000) names (plus their IDN variants, where applicable) necessary for the operation or the promotion of the TLD. ▇▇▇▇▇ must act as the Registered Name Holder of such names as that term is defined in the then-current cxDA Registrar Accreditation Agreement (RAA). These activations will be considered Transactions for purposes of Section 6.1 of the Agreement. ▇▇▇▇▇ must either (i) register such names through an cxDA-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to cxDA for compliance with cxDA Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder). At ▇▇▇▇▇ ’s discretion and in compliance with all other terms of this Agreement, such names may be released for registration to another person or entity. 2.2 ▇▇▇▇▇ may withhold from registration or allocate to ▇▇▇▇▇ names (including their IDN variants, where applicable) at All Levels in accordance with Section 2.6 of the Agreement. Such names may not be activated in the DNS, but may be released for registration to another person or entity at ▇▇▇▇▇ ’s discretion. Upon conclusion of ▇▇▇▇▇ ’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to ▇▇▇▇▇ shall be transferred as specified by cxDA. Upon cxDA’s request, ▇▇▇▇▇ shall provide a listing of all names withheld or allocated to ▇▇▇▇▇ pursuant to Section 2.6 of the Agreement. ▇▇▇▇▇ may self-allocate and renew such names without use of an cxDA accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.