Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.
Proposal Format To facilitate efficiency and consistency in proposal evaluation the following is mandatory. Proposals which do not follow this direction may be rejected as non-responsive and thus ineligible for award.
File Search Reports File search reports have been obtained from each Uniform Commercial Code filing office identified with respect to such Grantor in Section 2 hereof, and such search reports reflect no liens against any of the Collateral other than those permitted under the Credit Agreement.
Contract Formation Subject to FAR Sections 1.601(a) and 43.102, the Government Order must be signed by a duly warranted contracting officer, in writing. The same requirement applies to contract modifications affecting the rights of the parties. All terms and conditions intended to bind the Government must be included within the contract signed by the Government.
File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
Computer The Contractor shall maintain at its office for its use a computer with, at a minimum, a 1 GHz processor and an internet connection. The Contractor shall maintain individual email accounts for each of its project managers.
Company Formation The Company has been formed as a limited liability company under and pursuant to the Act. The Managers shall file the Certificate and all other such instruments or documents and shall do or cause to be done all such filing, recording, or other acts, as may be necessary or appropriate from time to time to comply with the requirements of law for the formation and/or operation of a limited liability company in the State of Delaware. The Managers may also direct that the Company be registered or qualified to do business in other jurisdictions.
Due Formation The Purchaser is duly formed, validly existing and in good standing in the jurisdiction of its organization. The Purchaser has all requisite power and authority to carry on its business as it is currently being conducted.
Electronic Format If requested by the Purchaser, the Servicer shall supply any and all information regarding the Mortgage Loans and the REO Properties, including all reports required to be delivered pursuant to Section 5.03, Section 6.02 and this Section 8.01, to the Purchaser in electronic format reasonably acceptable to Purchaser, unless otherwise limited by the servicing system utilized by the Servicer.
ELECTRONIC SUBMISSIONS Concessionaire must have the capacity to send and receive electronic submissions and communications as a pre-condition and continuing requirement of this Agreement. For purposes of this Agreement, “Electronic Submissions” shall only include the transmission of documents by email. Concessionaire shall comply with the following terms and conditions:
A. Concessionaire shall electronically submit all reports, including, but not limited to, Monthly Reports and Annual Reports as described in Paragraphs 12 and 13, by email to: XxxxxxxxXxxxxx@xxx.xx.xxx. Failure on the part of Concessionaire to submit reports electronically shall be a material breach of this Agreement, subject to Suspension of Operations and/or Termination in accordance with the terms and conditions set forth in Paragraphs 9 and 10.
B. Concessionaire shall maintain and monitor on a daily basis an active email address, designated for this Agreement and report any change to the email address during any Term of this Agreement. Failure on the part of Concessionaire to maintain and monitor the active email address, designated for this Agreement, shall be a material breach of this Agreement, subject to Suspension of Operations and/or Termination in accordance with the terms and conditions set forth in Paragraphs 9 and 10.
