Notification of Deposits Along with the delivery of each Deposit, Registry Operator will deliver to Escrow Agent and to ICANN (using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Part A, Section 9, reference 5 of this Specification (the “Interface Specification”)) a written statement (which may be by authenticated e-‐mail) that includes a copy of the report generated upon creation of the Deposit and states that the Deposit has been inspected by Registry Operator and is complete and accurate. Registry Operator will include the Deposit’s “id” and “resend” attributes in its statement. The attributes are explained in Part A, Section 9, reference 1 of this Specification. If not already an RFC, Registry Operator will use the most recent draft version of the Interface Specification at the Effective Date. Registry Operator may at its election use newer versions of the Interface Specification after the Effective Date. Once the Interface Specification is published as an RFC, Registry Operator will implement that version of the Interface Specification, no later than one hundred eighty (180) calendar days after such publishing.
Verification of Deposits 7.1. Within twenty-‐four (24) hours after receiving each Deposit or corrected Deposit, Escrow Agent must verify the format and completeness of each Deposit and deliver to ICANN a notification generated for each Deposit. Reports will be delivered electronically using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Part A, Section 9, reference 5 of this Specification.
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:
Payment of Deposits In the event any depositor does not accept the obligation of the Assuming Institution to pay any Deposit liability of the Failed Bank assumed by the Assuming Institution pursuant to this Agreement and asserts a claim against the Receiver for all or any portion of any such Deposit liability, the Assuming Institution agrees on demand to provide to the Receiver funds sufficient to pay such claim in an amount not in excess of the Deposit liability reflected on the books of the Assuming Institution at the time such claim is made. Upon payment by the Assuming Institution to the Receiver of such amount, the Assuming Institution shall be discharged from any further obligation under this Agreement to pay to any such depositor the amount of such Deposit liability paid to the Receiver.
