Processing of Deposit files Sample Clauses

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 ...
Sample 1Sample 2Sample 3See All (4k)
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...
Sample 1Sample 2Sample 3See All (34)
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 - XXX 0000, 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:
Sample 1Sample 2
Processing of Deposit files. Each Full Deposit and Differential Deposit shall be processed and electronically delivered in encrypted form to Escrow Agent fully in accordance with the process described in the Escrow Specification and Escrow Deposit Guidelines as detailed in Appendix 4.
Sample 1
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) TheA compressed and encrypted OpenPGP Message is created using the tarball file should be compressedas sole input. The suggested algorithm for compression is ZIP as per RFC 4880. (4) 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.
Sample 1

Related to Processing of Deposit files

  • Custodial Accounts The Master Servicer shall cause to be established and maintained by each Servicer under the Master Servicer's supervision the Custodial Account for P&I, Buydown Fund Accounts (if any) and special Custodial Account for Reserves and shall deposit or cause to be deposited therein daily the amounts related to the Mortgage Loans required by the Selling and Servicing Contracts to be so deposited. Proceeds received with respect to individual Mortgage Loans from any title, hazard, or FHA insurance policy, VA guaranty, Primary Insurance Policy or other insurance policy covering such Mortgage Loans shall be deposited first in the Custodial Account for Reserves if required for the restoration or repair of the related Mortgaged Property. Proceeds from such insurance policies not so deposited in the Custodial Account for Reserves shall be deposited in the Custodial Account for P&I, and shall be applied to the balances of the related Mortgage Loans as payments of interest and principal. The Master Servicer is hereby authorized to make withdrawals from and to issue drafts against the Custodial Accounts for P&I and the Custodial Accounts for Reserves for the purposes required or permitted by this Agreement. Each Custodial Account for P&I and each Custodial Account for Reserves shall bear a designation clearly showing the respective interests of the applicable Servicer, as trustee, and of the Master Servicer, in substantially one of the following forms: (a) With respect to the Custodial Account for P&I: (i) [Servicer's Name], as agent, trustee and/or bailee of principal and interest custodial account for PNC Mortgage Securities Corp., its successors and assigns, for various owners of interests in PNC Mortgage Securities Corp. mortgage-backed pools or (ii) [Servicer's Name] in trust for PNC Mortgage Securities Corp.; (b) With respect to the Custodial Account for Reserves: (i) [Servicer's Name], as agent, trustee and/or bailee of taxes and insurance custodial account for PNC Mortgage Securities Corp., its successors and assigns for various mortgagors and/or various owners of interests in PNC Mortgage Securities Corp. mortgage-backed pools or (ii) [Servicer's Name] in trust for PNC Mortgage Securities Corp. and various Mortgagors. The Master Servicer hereby undertakes to assure remittance to the Certificate Account of all amounts relating to the Mortgage Loans that have been collected by any Servicer and are due to the Certificate Account pursuant to Section 4.01 of this Agreement.