Common use of DNSSEC Clause in Contracts

DNSSEC. Registrar must allow its customers to use DNSSEC upon request by relaying orders to add, remove or change public key material (e.g., DNSKEY or DS resource records) on behalf of customers to the Registries that support DNSSEC. Such requests shall be accepted and processed in a secure manner and according to industry best practices. Registrars shall accept any public key algorithm and digest type that is supported by the TLD of interest and appears in the registries posted at: ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/assignments/dns- sec-alg-numbers/dns-sec-alg-numbers.xml and ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/assignments/ds-rr-types/ds-rr-types.xml. All such requests shall be transmitted to registries using the EPP extensions specified in RFC 5910 or its successors. Registrar must show the DNSSEC-signed status of the domain name in the RDAP Directory Service. Registrar must show the DNSSEC parameters stored in Registrar database in the RDAP Directory Service.

DNSSEC. Registrar must allow its customers to use DNSSEC upon request by relaying orders to add, remove or change public key material (e.g., DNSKEY or DS resource records) on behalf of customers to the Registries that support DNSSEC. Such requests shall be accepted and processed in a secure manner and according to industry best practices. Registrars shall accept any public key algorithm and digest type that is supported by the TLD of interest and appears in the registries posted at: ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/assignments/dns- dns-sec-alg-numbers/dns-sec-alg-numbers.xml and ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/assignments/ds-rr-types/ds-rr-types.xml. All such requests shall be transmitted to registries using the EPP extensions specified in RFC 5910 or its successors. Registrar must show the DNSSEC-signed status of the domain name in the RDAP Directory Service. Registrar must show the DNSSEC parameters stored in Registrar database in the RDAP Directory Service.