Registration Mindjet User Credentials Clause Samples
Registration Mindjet User Credentials
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with ▇▇▇ ▇▇▇▇, 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.
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.
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.
Registration of Contractor All contractors and subcontractors must comply with the requirements of Labor Code Section 1771.1(a), pertaining to registration of contractors pursuant to Section 1725.5. Bids cannot be accepted from unregistered contractors except as provided in Section 1771.1. This project is subject to compliance monitoring and enforcement by the Department of Industrial Relations. After award of the contract, Contractor and each Subcontractor shall furnish electronic payroll records directly to the Labor Commissioner in the manner specified in Labor Code Section 1771.4.
Registration, etc Each Pledgor agrees that, upon the occurrence and during the continuance of an Event of Default hereunder, if for any reason the Collateral Agent desires to sell any of the Pledged Securities of the Borrower at a public sale, it will, at any time and from time to time, upon the written request of the Collateral Agent, use its best efforts to take or to cause the issuer of such Pledged Securities to take such action and prepare, distribute and/or file such documents, as are required or advisable in the reasonable opinion of counsel for the Collateral Agent to permit the public sale of such Pledged Securities. Each Pledgor further agrees to indemnify, defend and hold harmless the Collateral Agent, each other Secured Party, any underwriter and their respective officers, directors, affiliates and controlling persons from and against all loss, liability, expenses, costs of counsel (including, without limitation, reasonable fees and expenses to the Collateral Agent of legal counsel), and claims (including the costs of investigation) that they may incur insofar as such loss, liability, expense or claim arises out of or is based upon any alleged untrue statement of a material fact contained in any prospectus (or any amendment or supplement thereto) or in any notification or offering circular, or arises out of or is based upon any alleged omission to state a material fact required to be stated therein or necessary to make the statements in any thereof not misleading, except insofar as the same may have been caused by any untrue statement or omission based upon information furnished in writing to such Pledgor or the issuer of such Pledged Securities by the Collateral Agent or any other Secured Party expressly for use therein. Each Pledgor further agrees, upon such written request referred to above, to use its best efforts to qualify, file or register, or cause the issuer of such Pledged Securities to qualify, file or register, any of the Pledged Securities under the Blue Sky or other securities laws of such states as may be requested by the Collateral Agent and keep effective, or cause to be kept effective, all such qualifications, filings or registrations. Each Pledgor will bear all costs and expenses of carrying out its obligations under this Section 12. Each Pledgor acknowledges that there is no adequate remedy at law for failure by it to comply with the provisions of this Section 12 and that such failure would not be adequately compensable in damages, and therefore agrees that its agreements contained in this Section 12 may be specifically enforced.