Notice File. CUSTOMER AGREES TO COMPLY WITH THE TERMS AND CONDITIONS CONTAINED IN ANY NOTICE FILES. 3.2 通知文件。客户同意遵守任何通知文件中包含的条款和条件。
Notice File Sample Clauses
Related to Notice File
Database File The Servicer will provide the Successor Servicer with a magnetic tape (in a format reasonably acceptable to the Indenture Trustee and the Servicer) containing the database file for each Contract (i) as of the Initial Cutoff Date, (ii) the Subsequent Cutoff Date, (iii) thereafter, as of the last day of the preceding Due Period on each Determination Date prior to a Service Transfer and (iv) on and as of the Business Day before the actual commencement of servicing functions by the Successor Servicer following the occurrence of a Service Transfer.
Receivable Files Complete There exists a Receivable File pertaining to each Receivable. Related documentation concerning the Receivable, including any documentation regarding modifications of the Contract, will be maintained electronically by the Servicer in accordance with customary policies and procedures. With respect to any Receivables that are tangible chattel paper, the complete Receivable File for each Receivable currently is in the possession of the Custodian.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
Review of Custodial Files The Custodian agrees, for the benefit of Certificateholders, to review, in accordance with the provisions of Section 2.01 of the Pooling and Servicing Agreement, each Custodial File. If in performing the review required by this Section 2.3 the Custodian finds any document or documents constituting a part of a Custodial File to be missing or defective in any material respect, the Custodian shall promptly so notify the Seller, the Master Servicer and the Trustee.
Grievance Files Written grievances and responses will be maintained separately from the employee’s personnel file.
Separate Grievance File All documents, communications and records dealing with the processing of a grievance shall be filed in a separate grievance file and shall not be kept in the personnel file of any of the participants.
Inspection Checklist (check one)
Processing of Deposit files The use of compression is recommended in order to reduce electronic data transfer times, and storage capacity requirements. Data encryption will be used to ensure the privacy of registry escrow data. Files processed for compression and encryption will be in the binary OpenPGP format as per OpenPGP Message Format -‐ RFC 4880, see Part A, Section 9, reference 3 of this Specification. Acceptable algorithms for Public-‐key cryptography, Symmetric-‐key cryptography, Hash and Compression are those enumerated in XXX 0000, not marked as deprecated in OpenPGP IANA Registry, see Part A, Section 9, reference 4 of this Specification, that are also royalty-‐free. The process to follow for the data file in original text format is: (1) The XML file of the deposit as described in Part A, Section 9, reference 1 of this Specification must be named as the containing file as specified in Section 5 but with the extension xml. (2) The data file(s) are aggregated in a tarball file named the same as (1) but with extension tar. (3) A compressed and encrypted OpenPGP Message is created using the tarball file as sole input. The suggested algorithm for compression is ZIP as per XXX 0000. The compressed data will be encrypted using the escrow agent’s public key. The suggested algorithms for Public-‐key encryption are Elgamal and RSA as per XXX 0000. The suggested algorithms for Symmetric-‐key encryption are TripleDES, AES128 and CAST5 as per XXX 0000. (4) The file may be split as necessary if, once compressed and encrypted, it is larger than the file size limit agreed with the escrow agent. Every part of a split file, or the whole file if not split, will be called a processed file in this section. (5) A digital signature file will be generated for every processed file using the Registry Operator’s private key. The digital signature file will be in binary OpenPGP format as per RFC 4880 Section 9, reference 3, and will not be compressed or encrypted. The suggested algorithms for Digital signatures are DSA and RSA as per XXX 0000. The suggested algorithm for Hashes in Digital signatures is SHA256. (6) The processed files and digital signature files will then be transferred to the Escrow Agent through secure electronic mechanisms, such as, SFTP, SCP, HTTPS file upload, etc. as agreed between the Escrow Agent and the Registry Operator. Non-‐electronic delivery through a physical medium such as CD-‐ROMs, DVD-‐ROMs, or USB storage devices may be used if authorized by ICANN. (7) The Escrow Agent will then validate every (processed) transferred data file using the procedure described in Part A, Section 8 of this Specification.
Personal File Any employee or owner operator shall be allowed to inspect his or her own personal file in the presence of the Company, during normal business hours. Any Officer of the Union, acting on behalf of the Employee, may inspect an employee or owner operator’s disciplinary file, with the written authorization from the employee or owner operator.
EMPLOYEE FILES 10.01 A copy of any completed formal evaluation which is to be placed in an employee’s file shall be first reviewed with the employee. The employee shall initial such evaluation as having been read and shall have the opportunity to add her or his views to such evaluation prior to it being placed in her or his file. It is understood that such evaluations do not constitute disciplinary action by the Employer against the employee. Having provided a written request to the Director of Care, or her designate, an employee shall be entitled to her personnel file for the purpose of reviewing any evaluations or formal disciplinary notations contained therein, in the presence of the Director of Care, at a mutually agreeable time. 10.02 The Employer will accommodate reasonable requests for copies of performance appraisals and records of discipline in an employee's file. 10.03 Letters of discipline shall be removed from an employee's file eighteen (18) months following the receipt of such letters provided that the employee's disciplinary record has remained discipline free over the eighteen (18) months period. Leaves of absence in excess of thirty (30) continuous calendar days will not count towards the eighteen (18) months period noted above.
