Registry Operations Sample Clauses

Registry Operations. 3.1 (d)(i)
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
Registry Operations. 3.1 (d)(i) Registration Restrictions.
Sample 1Sample 2Sample 3See All (4)
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.
Sample 1
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.
Sample 1
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.
Sample 1
Registry Operations. Obligations of all registry operators under the Registry Agreement, plus ICM specific actions, identified in the Documentation:
Sample 1
Registry Operations 
Sample 1Sample 2Sample 3See All (31)
AutoNDA by SimpleDocs

Related to Registry Operations

  • Registry Operator has (i) ceased to conduct its business in the ordinary course; or (ii) filed for bankruptcy, become insolvent or anything analogous to any of the foregoing under the laws of any jurisdiction anywhere in the world; or

  • Reservations for Registry Operations 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are 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 DNS servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy as defined in Specification 1; (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 the scope of (a), (b) or (c) above.

  • Registry Lock Registry Operator may offer the Registry Lock service, which is a registry service that allows an authorized representative from the sponsoring Registrar, request the activation or deactivation of any of the following EPP statuses: serverUpdateProhibited, serverDeleteProhibited and⁄or serverTransferProhibited. SPECIFICATION 1 CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION

  • REGISTRY OPERATOR CODE OF CONDUCT 1. In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to:

  • INTERNET PLANNING, ENGINEERING AND OPERATIONS ‌ Job Title: Internet/Web Engineer Job#: 2620 General Characteristics Integrally involved in the development and support of all Internet/Intranet/Extranet sites and supporting systems. Works closely with other IT groups and customers to define the system design and user interface based on customer needs and objectives. Participates in all phases of the development and implementation process, and may act as a project manager on special projects. Ensures the integration of the Web servers and all other supporting systems. Responsible for system tuning, optimization of information/data processing, maintenance and support of the production environment.

  • Abuse and Neglect of Children and Vulnerable Adults: Abuse Registry Party agrees not to employ any individual, to use any volunteer or other service provider, or to otherwise provide reimbursement to any individual who in the performance of services connected with this agreement provides care, custody, treatment, transportation, or supervision to children or to vulnerable adults if there has been a substantiation of abuse or neglect or exploitation involving that individual. Party is responsible for confirming as to each individual having such contact with children or vulnerable adults the non-existence of a substantiated allegation of abuse, neglect or exploitation by verifying that fact though (a) as to vulnerable adults, the Adult Abuse Registry maintained by the Department of Disabilities, Aging and Independent Living and (b) as to children, the Central Child Protection Registry (unless the Party holds a valid child care license or registration from the Division of Child Development, Department for Children and Families). See 33 V.S.A. §4919(a)(3) and 33 V.S.A. §6911(c)(3).

  • System Operations Each party, at its own expense, shall provide and maintain the equipment, software, services and testing necessary to transmit Data Communications to, and receive Data Communications from the parties’ respective Receipt Computers.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • COVENANTS OF REGISTRY OPERATOR Registry Operator covenants and agrees with ICANN as follows:

Time is Money Join Law Insider Premium to draft better contracts faster.