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.
Emergency Standby for Goods and/or Services If any Federal or State official, having authority to do so, declares an emergency or the occurrence of a natural disaster within the State of Connecticut, DAS and the Client Agency may request the Goods and Services on an expedited and prioritized basis. Upon receipt of such a request the Contractor shall make all necessary and appropriate commercially reasonable efforts to reallocate its staffing and other resources in order to give primary preference to Performing this Contract ahead of or prior to fulfilling, in whole or in part, any other contractual obligations that the Contractor may have. The Contractor is not obligated to make those efforts to Perform on an expedited and prioritized basis in accordance with this paragraph if doing so will make the Contractor materially breach any other contractual obligations that the Contractor may have. Contractor shall acknowledge receipt of any request made pursuant to this paragraph within 2 hours from the time that the Contractor receives it via purchase order or through a request to make an expedited or prioritized purchase through the State of Connecticut Purchasing Card (MasterCard) Program (the “P-Card Program”). If the Contractor fails to acknowledge receipt within 2 hours, confirm its obligation to Perform or actually Perform, as set forth in the purchase order or through the P-Card Program, then DAS and the Client Agency may procure the Performance from another source without further notice to Contractor and without creating any right of recourse at law or in equity against DAS or Client Agency.
Contact in Event of Unauthorized Transfer If you believe your Card and/or access code has been lost or stolen or that someone has transferred or may transfer money from your account without your permission, either call us immediately at:
Default Authorized User a. Breach by Authorized User An Authorized User’s breach shall not be deemed a breach of the Centralized Contract; rather, it shall be deemed a breach of the Authorized User’s performance under the terms and conditions of the Centralized Contract.
Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).
Distribution of Written Materials Any written materials distributed by the Trustee to the Beneficiaries pursuant to this Agreement shall be sent by mail (or otherwise communicated in the same manner as Holdings utilizes in communications to holders of Holdings Shares subject to applicable regulatory requirements and provided such manner of communications is reasonably available to the Trustee) to each Beneficiary at its address as shown on the books of the Partnership. The Partnership shall provide or cause to be provided to the Trustee for purposes of communication, on a timely basis and without charge or other expense: (a) a current List; and (b) upon the request of the Trustee, mailing labels to enable the Trustee to carry out its duties under this Agreement.
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. 1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
Dissemination of Research Findings and Acknowledgement of Controlled-Access Datasets Subject to the NIH GDS Policy
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.
Authorized User You may request us to issue a Card to an individual who has no financial responsibility under this Agreement. An Authorized User has the same access to your Account as you do, subject to any limitations we may impose. An Authorized User has no authority to add or delete Cardholders, request a replacement Card or terminate or modify this Agreement. You may terminate an Authorized User’s authority to access your Account at any time. To do this, you must return the Card to PenFed. You agree that you are responsible for all charges and cash advances made by an Authorized User, including charges made before the Card is returned, recurring charges, or charges made without the use of the Card initiated by the Authorized User after termination of the Authorized User’s access.