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.
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.
Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:
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.
Location of Receivable Files The Custodian will maintain the Receivable Files in the United States in such a manner as to permit retrieval thereof and access thereto in the manner contemplated by this Agreement. The Custodian’s records will at all times indicate that it is holding the Receivable Files on behalf of the Trust, separate from any other instruments and files that it holds.
System Agency Data A. As between the Parties, all data and information acquired, accessed, or made available to Grantee by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Grantee in the course of providing data processing services in connection with Xxxxxxx’s performance hereunder (the “System Agency Data”), is owned solely by System Agency.
B. Grantee has no right or license to use, analyze, aggregate, transmit, create derivatives of, copy, disclose, or process the System Agency Data except as required for Grantee to fulfill its obligations under the Grant Agreement or as authorized in advance in writing by System Agency.
C. For the avoidance of doubt, Grantee is expressly prohibited from using, and from permitting any third party to use, System Agency Data for marketing, research, or other non-governmental or commercial purposes, without the prior written consent of System Agency.
D. Grantee shall make System Agency Data available to System Agency, including to System Agency’s designated vendors, as directed in writing by System Agency. The foregoing shall be at no cost to System Agency.
E. Furthermore, the proprietary nature of Xxxxxxx’s systems that process, store, collect, and/or transmit the System Agency Data shall not excuse Xxxxxxx’s performance of its obligations hereunder.
COMPUTER GRAPHICS FILES The Engineer agrees to comply with Attachment G, Computer Graphics Files for Document and Information Exchange, if determined by the State to be applicable to this contract.
Client Records 25.2.1 CONTRACTOR shall prepare and maintain accurate and 26 complete records of clients served and dates and type of services provided 27 under the terms of this Agreement in a form acceptable to ADMINISTRATOR.
Access to Files A copy of any completed evaluation which is to be placed in a nurse’s file shall be first reviewed with the nurse. The nurse shall initial such evaluation as having been read and shall have the opportunity to add her views to such evaluation prior to it being placed in her file. It is understood that such evaluations do not constitute disciplinary action by the Hospital against the nurse. Each nurse shall have reasonable access to all her files for the purpose of reviewing their contents in the presence of her supervisor. A copy of the evaluation will be provided to the nurse at her request. No document shall be used against a nurse where it has not been brought to her attention in a timely manner. Any letter of reprimand, suspension or other sanction will be removed from the record of a nurse eighteen months following the receipt of such letter, suspension or other sanction provided that the nurse’s record has been discipline free for one year. Newly hired part-time nurses shall beconsidered to be on probation for a period of sixty tours worked hours of work for nurses whose regular hours of work are other than the standard work day). If retained the sixty tours hours) worked. With the written consent of the or her designate, such probationary period may be extended. Where the Hospital requests an extension of the probationary period, it will provide notice to the Association at least fourteen calendar days prior to the expected date of expiration of the initial probationary period. It is to the probationary period will not exceed an additional sixty tours hours) worked and, where requested, the Hospital will advise the nurse and the Association of the basis of such extension. A nurse who transfers from casual part-time or full-time to regular not has previously completed one since her date of last hire. Where no such probationary period has been served, the number of tours worked (hours worked for nurses whose regular hours of work are other than the standard work day) during the nine months immediately preceding the transfer shall be credited towards the probationary period.
Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.
