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 ▇▇▇ ▇▇▇▇, 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.
Acceptable Accounting System The Contractor shall maintain the acceptable/approved status of their Accounting System and submit updates to the current status
Required Good Faith Efforts In accordance with 5 NYCRR § 142.8, Contractors must document their good faith efforts toward utilizing MWBEs on the Contract. Evidence of required good faith efforts shall include, but not be limited to, the following:
1. A list of the general circulation, trade and MWBE-oriented publications and dates of publications in which the Contractor solicited the participation of certified MWBEs as subcontractors/suppliers, copies of such solicitations and any responses thereto.
2. A list of the certified MWBEs appearing in the Empire State Development (“ESD”) MWBE directory that were solicited for this Contract. Provide proof of dates or copies of the solicitations and copies of the responses made by the certified MWBEs. Describe specific reasons that responding certified MWBEs were not selected.
3. Descriptions of the Contract documents/plans/specifications made available to certified MWBEs by the Contractor when soliciting their participation and steps taken to structure the scope of work for the purpose of subcontracting with, or obtaining supplies from, certified MWBEs.
4. A description of the negotiations between the Contractor and certified MWBEs for the purposes of complying with the MWBE goals of this Contract.
5. Dates of any pre-bid, pre-award or other meetings attended by Contractor, if any, scheduled by OGS with certified MWBEs whom OGS determined were capable of fulfilling the MWBE goals set in the Contract.
6. Other information deemed relevant to the request.
Obligor Notification Forms The Borrower shall furnish the Collateral Agent and the Administrative Agent with an appropriate power of attorney to send (at the Administrative Agent’s discretion on the Collateral Agent’s behalf, after the occurrence and during the continuance of an Event of Default or the Facility Maturity Date) Obligor notification forms to give notice to the Obligors of the Collateral Agent’s interest in the Collateral Portfolio and the obligation to make payments as directed by the Administrative Agent on the Collateral Agent’s behalf.
Acceptable Estimating System The Contractor shall maintain the acceptable status of their Estimating System and submit updates to the current status, if applicable