Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in RFC 8909, see Part A, Section 9, reference 1 of this Specification and RFC 9022, 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. UTF-8 character encoding will be used.
Appears in 8 contracts
Samples: TLD Sponsorship Registry Agreement, Sponsored TLD 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 RFC 8909, see Part A, Section 9, reference 1 of this Specification Appendix and RFC 9022, 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. UTF-8 character encoding will be used.
Appears in 6 contracts
Samples: Registry Agreement (Verisign Inc/Ca), 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 RFC 8909XXX 0000, see Part A, Section 9, reference 1 of this Specification and RFC 9022XXX 0000, 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. UTF-8 character encoding will be used.
Appears in 4 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
