Registry Operations. 3.1 (d)(i)
Registry Operations. 3.1 (d)(i) Registration Restrictions.
3.1 (d)(i)(A) Registry Operator 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 hxxx://xxxx.xxxx.xxx/XXX/tlds-alpha-by-domain.txt for initial (i.e., other than renewal) registration at the second level within the TLD.
3.1 (d)(i)(B) Registry Operator shall apply, monitor, and enforce the restrictions on registration in the Registry TLD. Appendix 11 sets forth the restrictions to be applied and sets forth the manner by which these restrictions shall be applied, monitored, and enforced. Changes to the restrictions may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall unreasonably withhold). 3.1 (d)(ii) Functional and Performance Specifications. Functional and Performance Specifications for operation of the TLD shall be as set forth in Appendix 7 hereto, and shall address without limitation DNS services; operation of the shared registration system; and nameserver operations. Registry Operator shall keep technical and operational records sufficient to evidence compliance with such specifications for at least one year, which records ICANN may audit from time to time upon reasonable advance written notice, provided that such audits shall not exceed one per quarter. Any such audit shall be at ICANN’s cost. 3.1 (d)(iii) Registry Services. Registry Services are, for purposes of this Agreement, defined as the following: (a) those services that are both (i) operations of the registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the registry zone servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; and (ii) provided by the Registry Operator for the .biz registry as of the Effective Date as set forth on Appendix 9; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy (as defined in Section 3.1(b) above); (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within ...
Registry Operations. (d)(i) Registration Restrictions.
Registry Operations. 3.1 (d)(i) Registration Restrictions. 3.1 (d)(i) Registration Restrictions. Registry Operator shall reserve, and not register any TLD strings (ia) appearing on the list of reserved TLD strings attached as Xxxxxxxx 0 xxxxxx xx (xxx) located at xxxx://xxxx.xxxx.xxx/TLD/tlds-‐alpha-‐by-‐domain.txt for initial (i.e., other than renewal) registration at the second level within the TLD.
Registry Operations. Obligations of all registry operators under the Registry Agreement, plus ICM specific actions, identified in the Documentation:
1. Registry Operator will
a. Contract with back-end provider
b. Work with the designated back-end registry provider to provide the back-end Registry system and services related to providing and maintaining the system (e.g., registrar help desk and billing). The system will integrate with databases that record and manage the authentication data.
c. Work with the designated back end provider will conduct comprehensive testing of the registry system and registration procedures (including the interfaces with Registrars and the Authentication Services provider(s)).
i. This testing will occur in cooperation with a select group of ICANN accredited registrars (the “Testbed Registrars”) with in put from sTLD Community members as appropriate.
ii. The goal of OT&E testing is the confirmation that all entities involved in the registration process are prepared for the commencement of full operations and that escalation, support and reporting processes are in place and ready
d. Ensure that the processes and procedures for registrars and registrants are clearly established and published in time to meet the published schedules in the Start Up Plan.
e. Select and integrate Registrars, in accordance with Appendix S, Part 5
f. Operate mechanisms for pre-reservation, STOP, CEDRP, reserved names, and mechanisms related to abusive registrations, geographic designators, culturally sensitive names.
g. Conduct the Limited Launch, accepting registrations through ICANN accredited registrars only from members of the Community who have already been pre- authenticated.
h. During the General Registration phase, registrations will be accepted through ICANN accredited registrars from prospective registrants who may or may not have already been authenticated as members of the Community. For those who have not been pre-authenticated, the requested domains will be placed on registry hold and will not resolve until the registrant has been successfully authenticated. In the event that a prospective registrant cannot be verified as a member of the community, the registration will not be completed and the name will be reallocated.
i. Operate the registry going forward in accordance with the provisions of the Registry Agreement
Registry Operations. Participant acknowledges that the Registry is a newly developed service of the ABFM and, as such, may be subject to modification or adjustment by the ABFM. Participant agrees that the ABFM may, from time-to-time, modify or amend the substantive provisions of this Master Agreement related to the manner in which the Registry operates, so long as such modifications or amendments are of general applicability to all similarly situated participants participating in the Registry. Participant will be bound by any modifications or amendments to this Master Agreement unless, within thirty (30) days of receipt of such modification or amendment, Participant notifies the ABFM pursuant to Section 13 of this Master Agreement that a specific modification or amendment is not acceptable to it, in which case, this Master Agreement and Participant’s participation in the Registry will terminate effective at the end of the thirty (30) day period in which the ABFM receives such notice. In addition, during the foregoing pre-termination period, Participant shall not have the right to submit further data to the Registry but the other provisions of this Master Agreement shall apply.
Registry Operations. Practice acknowledges that the Registry is a newly developed service of CDR and, as such, may be subject to modification or adjustment by CDR. Practice agrees that CDR may, from time-to-time, modify or amend the substantive provisions of this Agreement related to the manner in which the Registry operates, so long as such modifications or amendments are of general applicability to all similarly situated Practices participating in the Registry. Practice will be bound by any modifications or amendments to this Agreement unless, within thirty (30) days of receipt of such modification or amendment, Practice notifies CDR pursuant to Section 12 of this Agreement that a specific modification or amendment is not acceptable to it, in which case, this Agreement and Practice’s participation in the Registry will terminate effective at the end of the thirty (30) day period in which CDR receives such notice. In addition, during the foregoing pre-termination period, Practice shall not have the right to submit further data to the Registry but the other provisions of this Agreement shall apply.
Registry Operations
