Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-‐xxxxx-‐xxxxxxx-‐registry-‐data-‐escrow, see Part A, Section 9, reference 1 of this Specification and draft-‐xxxxx-‐noguchi-‐dnrd-‐objects-‐mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-‐8 character encoding will be used.
Appears in 1613 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-‐xxxxx-‐xxxxxxx-‐registry-‐data-‐escrow, see Part A, Section 9, reference 1 of this Specification and draft-‐xxxxx-‐noguchi-‐dnrd-‐objects-‐mappingdraft-‐xxxxx-‐xxxxxxx-‐dnrd-‐objects-‐mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-‐8 character encoding will be used.
Appears in 613 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-‐xxxxx-‐xxxxxxx-‐registry-‐data-‐escrowdraft-‐xxxxx-‐noguchi-‐registry-‐data-‐escrow, see Part A, Section 9, reference 1 of this Specification and draft-‐xxxxx-‐noguchi-‐dnrd-‐objects-‐mappingdraft-‐xxxxx-‐xxxxxxx-‐dnrd-‐objects-‐mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-‐8 character encoding will be used.
Appears in 183 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-‐xxxxx-‐xxxxxxx-‐registry-‐data-‐escrow, see Part A, Section 9, reference 1 of this Specification Appendix and draft-‐xxxxx-‐noguchi-‐dnrd-‐objects-‐mapping, see Part A, Section 9, reference 2 of this Specification Appendix (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-‐8 character encoding will be used.
Appears in 1 contract
Samples: Coop Registry Agreement
Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-‐xxxxx-‐xxxxxxx-‐registry-‐data-‐escrow, see Part A, Section 9, reference 1 of this Specification and draft-‐xxxxx-‐noguchi-‐dnrd-‐objects-‐mappingdraft-‐xxxxx-‐xxxxxxx-‐ dnrd-‐objects-‐mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-‐8 character encoding will be used.
Appears in 1 contract
Samples: Registry Agreement
Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-‐xxxxx-‐xxxxxxx-‐registry-‐data-‐escrow, see Part A, Section 9, reference 1 of this Specification and draft-‐xxxxx-‐noguchi-‐dnrd-‐objects-‐mappingdraft-‐xxxxx-‐noguchi-‐ dnrd-‐objects-‐mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-‐8 character encoding will be used.
Appears in 1 contract
Samples: Registry Agreement
