INITIAL VERIFICATION; VALIDATION AND REGISTRATION; BASELINE Sample Clauses

INITIAL VERIFICATION; VALIDATION AND REGISTRATION; BASELINE. Section 6.1 Initial Verification
AutoNDA by SimpleDocs

Related to INITIAL VERIFICATION; VALIDATION AND REGISTRATION; BASELINE

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • LICENSING, ACCREDITATION AND REGISTRATION The Contractor shall comply with all applicable local, state, and federal licensing, accreditation and registration requirements or standards necessary for the performance of this Contract.

  • Supported Initial and Renewal Registration Periods a. Initial registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms of up to ten years.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Inspection Testing Authorization and Right of Access 2.1 Equipment Testing and Inspection 2.2 Authorization Required Prior to Parallel Operation

  • Initial Registration Periods Initial registrations of registered names may be made in the registry in one (1) year increments for up to a maximum of ten (10) years. For the avoidance of doubt, initial registrations of registered names may not exceed ten (10) years.

  • Drug Testing Procedures a. The testing procedures and safeguards provided in this policy shall be adhered to by any laboratory personnel administering departmental drug tests.

  • Registration of Contractors Contractor and all subcontractors must comply with the requirements of labor code section 1771.1(a), pertaining to registration of contractors pursuant to section 1725.5. Registration and all related requirements of those sections must be maintained throughout the performance of the Contract.

  • Unbundled Subloop Distribution (USLD) 2.8.2.1 The USLD facility is a dedicated transmission facility that BellSouth provides from an End User’s point of demarcation to a BellSouth cross-connect device. The BellSouth cross-connect device may be located within a remote terminal (RT) or a stand-alone cross-box in the field or in the equipment room of a building. The USLD media is a copper twisted pair that can be provisioned as a 2-wire or 4-wire facility. BellSouth will make available the following subloop distribution offerings where facilities exist: USLD – Voice Grade (USLD-VG) Unbundled Copper Subloop (UCSL) USLD – Intrabuilding Network Cable (USLD-INC (aka riser cable))

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