ICANN

12025 Waterfront Drive, Suite 300 Los Angeles 90094-2536 US CA gavin.brown@icann.org

Internet Registration Extensions (REGEXT) This document describes an extension to the Registration Data Access Protocol () which allows the Time-To-Live (TTL) values for relevant DNS record types to be included in RDAP responses. The source for this draft, and an issue tracker, may can be found at .

Introduction While allows RDAP server operators to provide information about the content of the NS, DS, A and AAAA record(s) which are published in the DNS for a given registry object (domain or host object), it does not provide a mechanism to allow the Time-To-Live (TTL) values of those records to be included in responses. This document describes how TTL information can be included in domain and nameserver objects in RDAP responses. This document is complementary to the EPP TTL extension (), but registry operators do not need to implement that extension in their EPP server in order to implement this RDAP extension.

Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

RDAP Response Specification Servers which support this extension MUST include a ttl_values object in any domain and nameserver objects included in RDAP responses. The ttl_values object has property names which are DNS record types, and values which are integers representing the TTL values used for those record types. Example domain object: Example nameserver object:

RDAP Conformance Servers returning responses containing TTL values MUST include the string "ttl" in the rdapConformance array.

IANA Considerations IANA is requested to register the following value in the RDAP Extensions Registry: Extension identifier: ttl Registry operator: Any Published specification: this document Contact: IETF <iesg@ietf.org> Intended usage: this extension describes how DNS TTL values can be included in RDAP responses.

Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document describes JSON data structures representing registration information maintained by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs). These data structures are used to form Registration Data Access Protocol (RDAP) query responses. This document obsoletes RFC 7483. Informative References ICANN This document describes an extension to the Extensible Provisioning Protocol (EPP) that allows EPP clients to manage the Time-To-Live (TTL) value for domain name delegation records. About this draft This note is to be removed before publishing as an RFC. The source for this draft, and an issue tracker, may can be found at https://github.com/gbxyz/epp-ttl-extension.