Common use of Deposit’s Format Clause in Contracts

Deposit’s Format. 4.1.1. The data in each Deposit, such as domains, contacts, name servers, registrars, etc., will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping (see Domain Name Data Escrow Specification (work in progress) at <▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/draft-ariasnoguchi-registry-data-escrow> and Domain Name Registration (DNRD) Objects Mapping, at <▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping> (collectively, the “DNDE Specification”)). The DNDE Specification describes certain data elements as optional; if Registry Operator uses such elements, Registry Operator will include those data elements in the Deposits. 4.1.2. For purposes of complying with the requirements of Section 4.1.1 and Section 7.4, Registry Operator will follow the draft version of the DNDE Specification available at the time of signing this Agreement or newer, if not already a Request for Comments (“RFC”). Once DNDE Specification is published as an RFC, Registry Operator shall thereafter follow such DNDE Specification as soon as reasonably practicable, but in no event later than 180 calendar days after such publishing. 4.1.3. Registry Operator shall identify to Escrow Agent the Deposit format (CSV or XML) under the DNDE Specification that it will use for Deposits. Verification of Registry Operator’s Deposits shall be based on the Deposit format identified by Registry Operator. Registry Operator may change the Deposit format that it uses for Deposits to other formats acceptable under the DNDE Specification provided that Registry Operator shall identify such new format in writing to Escrow Agent and ICANN in advance of its first Deposit using the new format.

Deposit’s Format. 4.1.1. 4.1.1 The data in each Deposit, such as domains, contacts, name servers, registrars, etc., will be compiled into a file constructed as described in draft-draft- ▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-objects- mapping (see Domain Name Data Escrow Specification (work in progress) at <▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/draft-ariasnoguchi-registry-data-escrow> and Domain Name Registration (DNRD) Objects Mapping, at <▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping> (collectively, the “DNDE Specification”)). The DNDE Specification describes certain data elements as optional; if Registry Operator uses such elements, Registry Operator will include those data elements in the Deposits. 4.1.2. 4.1.2 For purposes of complying with the requirements of Section 4.1.1 and Section 7.44.1.1, Registry Operator will follow the draft version of the DNDE Specification available at the time of signing this Agreement or newer, if not already a Request for Comments (“RFC”). Once DNDE Specification is published as an RFC, Registry Operator shall thereafter follow such DNDE Specification as soon as reasonably practicable, but in no event later than 180 calendar days after such publishing. 4.1.3. 4.1.3 Registry Operator shall identify to Escrow Agent the Deposit format (CSV or XML) under the DNDE Specification that it will use for Deposits. Verification of Registry Operator’s Deposits shall be based on the Deposit format identified by Registry Operator. Registry Operator may change the Deposit format that it uses for Deposits to other formats acceptable under the DNDE Specification provided that Registry Operator shall identify such new format in writing to Escrow Agent and ICANN in advance of its first Deposit using the new format.

Deposit’s Format. 4.1.1. 4.1.1 The data in each Deposit, such as domains, contacts, name servers, registrars, etc., will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd--dnrd- objects-mapping (see Domain Name Data Escrow Specification (work in progress) at <▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/draft-ariasnoguchi-registry-data-data- escrow> and Domain Name Registration (DNRD) Objects Mapping, at <▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping> (collectively, the “DNDE Specification”)). The DNDE Specification describes certain data elements as optional; if Registry Operator uses such elements, Registry Operator will include those data elements in the Deposits. 4.1.2. 4.1.2 For purposes of complying with the requirements of Section 4.1.1 and Section 7.44.1.1, Registry Operator will follow the draft version of the DNDE Specification available at the time of signing this Agreement or newer, if not already a Request for Comments (“RFC”). Once DNDE Specification is published as an RFC, Registry Operator shall thereafter follow such DNDE Specification as soon as reasonably practicable, but in no event later than 180 calendar days after such publishing. 4.1.3. 4.1.3 Registry Operator shall identify to Escrow Agent the Deposit format (CSV or XML) under the DNDE Specification that it will use for Deposits. Verification of Registry Operator’s Deposits shall be based on the Deposit format identified by Registry Operator. Registry Operator may change the Deposit format that it uses for Deposits to other formats acceptable under the DNDE Specification provided that Registry Operator shall identify such new format in writing to Escrow Agent and ICANN in advance of its first Deposit using the new format.