Common use of Notification of Deposits Clause in Contracts

Notification of Deposits. 6.1 Along with the delivery of each Deposit, Registry Operator will deliver to Escrow Agent and to ICANN 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 such statements, as described in the DNDE Specification. Such written statements shall be delivered to Escrow Agent in a manner agreed to by Registry Operator and Escrow Agent, and shall be delivered to ICANN using the API described in ▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/draft-▇▇▇▇▇▇-icann-registry-interfaces, see Part A, Section 9, reference 5 of the Escrow Specification (“Interface Specification”). 6.2 For purposes of complying with the requirements of Section 6.1, Registry Operator will follow the draft version of the Interface Specifications available at the time of signing this Agreement or newer, if not already a RFC. Once the Interface Specification is published as an RFC, Registry Operator will follow such Interface Specification as soon as reasonably practicable, but in no event later than 180 calendar days after such publishing.

Notification of Deposits. 6.1 6.1. Along with the delivery of each Deposit, Registry Operator will deliver to Escrow Agent and to ICANN 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 such statements, as described in the DNDE Specification. Such written statements shall be delivered to Escrow Agent in a manner agreed to by Registry Operator and Escrow Agent, and shall be delivered to ICANN using the API described in ▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/draft-▇▇▇▇▇▇-icann-registry-interfaces, see Part A, Section 9, reference 5 of the Escrow Specification (“Interface Specification”). 6.2 6.2. For purposes of complying with the requirements of Section 6.1, Registry Operator will follow the draft version of the Interface Specifications available at the time of signing this Agreement or newer, if not already a RFC. Once the Interface Specification is published as an RFC, Registry Operator will follow such Interface Specification as soon as reasonably practicable, but in no event later than 180 calendar days after such publishing.

Notification of Deposits. 6.1 Along with the delivery of each Deposit, Registry Operator will deliver to Escrow Agent and to ICANN 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 such statements, as described in the DNDE Specification. Such written statements shall be delivered to Escrow Agent in a manner agreed to by Registry Operator and Escrow Agent, and shall be delivered to ICANN using the API described in ▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/draft-▇▇▇▇▇▇-icann--icann- registry-interfaces, see Part A, Section 9, reference 5 of the Escrow Specification (“Interface Specification”). 6.2 For purposes of complying with the requirements of Section 6.1, Registry Operator will follow the draft version of the Interface Specifications available at the time of signing this Agreement or newer, if not already a RFC. Once the Interface Specification is published as an RFC, Registry Operator will follow such Interface Specification as soon as reasonably practicable, but in no event later than 180 calendar days after such publishing.