Internet-Draft RDAP TTL Extension January 2024
Brown Expires 5 July 2024 [Page]
Registration Extensions (REGEXT)
Intended Status:
Standards Track
G. Brown

RDAP Extension for DNS Time-To-Live (TTL Values)


This document describes an extension to the Registration Data Access Protocol ([RFC9083]) which allows the Time-To-Live (TTL) values for relevant DNS record types to be included in RDAP responses.

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

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 5 July 2024.

Table of Contents

1. Introduction

While [RFC9083] 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 ([I-D.ietf-regext-epp-ttl]), but registry operators do not need to implement that extension in their EPP server in order to implement this RDAP extension.

2. 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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

3. 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:

    "objectClassName": "domain",
    "ldhName": "",
    "ttl_values": {
        "NS": 3600,
        "DS": 60

Example nameserver object:

    "objectClassName": "nameserver",
    "ldhName": "",
    "ttl_values": {
        "A": 86400,
        "AAAA": 172800

3.1. RDAP Conformance

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

4. 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 <>

Intended usage: this extension describes how DNS TTL values can be included in RDAP responses.

5. Normative References

Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <>.
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <>.
Hollenbeck, S. and A. Newton, "JSON Responses for the Registration Data Access Protocol (RDAP)", STD 95, RFC 9083, DOI 10.17487/RFC9083, , <>.

6. Informative References

Brown, G., "Extensible Provisioning Protocol (EPP) mapping for DNS Time-To-Live (TTL) values", Work in Progress, Internet-Draft, draft-ietf-regext-epp-ttl-04, , <>.

Author's Address

Gavin Brown
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
United States of America