Common use of Notification of Deposits Clause in Contracts

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-▇▇▇▇▇▇-icann-registry-interfaces, see Part A, Section 9, reference 5 of this Specification (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliates. 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.

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-draft‐▇▇▇▇▇▇-icann-registry-interfaces‐icann‐registry‐interfaces, see Part A, Section 9, reference 5 of this Specification (the “Interface Specification”)) a written statement from Registry Operator (which may be by authenticated e-maile‐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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliates. 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.

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-▇▇▇▇▇▇-icann- icann-registry-interfaces, see Part A, Section 9, reference 5 of this Specification (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliates. 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.

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-▇▇▇▇▇▇-icann--icann- registry-interfaces, see Part A, Section 9, reference 5 of this Specification Appendix (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliatesaffiliates. 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 SpecificationAppendix. If not already an RFC, Registry Operator will use the most recent draft version of the Interface Specification at the Updated Data Escrow Effective Date. Registry Operator may at its election use newer versions of the Interface Specification after the Updated Data Escrow 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.

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-▇▇▇▇▇▇-icann-registry-interfaces, see Part A, Section 9, reference 5 of this Specification Appendix (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliatesaffiliates. 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 SpecificationAppendix. 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.

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-▇▇▇▇▇▇-icann-registry-interfaces, see Part A, Section 9, reference 5 of this Specification Appendix (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliatesaffiliates. 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 SpecificationAppendix. If not already an RFC, Registry Operator will use the most recent draft version of the Interface Specification at the Effective Dateas of July 1, 2023. Registry Operator may at its election use newer versions of the Interface Specification after the Effective DateJuly 1, 2023. 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.

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-▇▇▇▇▇▇-icann--icann- registry-interfaces, see Part A, Section 9, reference 5 of this Specification Appendix (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliatesaffiliates. 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 SpecificationAppendix. If not already an RFC, Registry Operator will use the most recent draft version of the Interface Specification at the Effective Dateas of December 1, 2024. Registry Operator may at its election use newer versions of the Interface Specification after the Effective DateDecember 1, 2024. 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.

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-▇▇▇▇▇▇-icann--icann- registry-interfaces, see Part A, Section 9, reference 5 of this Specification Appendix (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliatesaffiliates. 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 SpecificationAppendix. If not already an RFC, Registry Operator will use the most recent draft version of the Interface Specification at the Updated Data Escrow Effective Date▇▇▇▇.▇▇ of December 1, 2024. Registry Operator may at its election use newer versions of the Interface Specification after the Updated Data Escrow Effective DateDateDecember 1, 2024. 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.

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-▇▇▇▇▇▇-icann-registry-interfaces, see Part A, Section 9, reference 5 of this Specification Appendix (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliatesaffiliates. 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 SpecificationAppendix. If not already an RFC, Registry Operator will use the most recent draft version of the Interface Specification at the Effective DateDateas of July 1, 2023. Registry Operator may at its election use newer versions of the Interface Specification after the Effective DateDateJuly 1, 2023. 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.

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-▇▇▇▇▇▇-icann-registry-interfaces, see Part A, Section 9, reference 5 of this Specification Appendix (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliatesaffiliates. 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 SpecificationAppendix. If not already an RFC, Registry Operator will use the most recent draft version of the Interface Specification at the Updated Data Escrow Effective Date. Registry Operator may at its election use newer versions of the Interface Specification after the Updated Data Escrow 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.

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-▇▇▇▇▇▇-icann- icann-registry-interfaces, see Part A, Section 9, reference 5 of this Specification AppendixSpecification (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliates. 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 SpecificationAppendixSpecification. 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.

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-▇▇▇▇▇▇-icann-registry-interfaces, see Part A, Section 9, reference 5 of this Specification (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliates. 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. 18. Section 8 of Part A of Specification 2 is hereby amended and restated in its entirety as follows:

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-▇▇▇▇▇▇-icann-registry-interfaces, see Part A, Section 9, reference 5 of this Specification SpecificationAppendix (the “Interface Specification”)) a written statement from Registry Operator (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. The preparation and submission of this statement must be performed by the Registry Operator or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent’s Affiliatesaffiliates. 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 SpecificationSpecificationAppendix. 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.