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

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 https://datatracker.ietf.org/drafts/current/.¶

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 26 December 2024.¶

Copyright Notice

Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

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

3. RDAP Response Specification

Servers which support this extension MUST include a ttl property in any domain and nameserver objects included in RDAP responses.¶

The ttl property is an array of objects. These objects have the following properties:¶

• A types property, which is an array of DNS record type mnemonics;¶
• A value property, which is an unsigned integer indicated the TTL value for those DNS record types;¶
• An OPTIONAL remarks property, which is an array of remarks (see Section 4.3 of [RFC9083]); and¶
• An OPTIONAL events property, which is an array of events (see Section 4.5 of [RFC9083]).¶

DNS record type mnemonics MUST be in all capitals. Each DNS record type MUST only appear once in a response.¶

TTL values MUST be unsigned integers in the range 0-2,147,483,647.¶

Example domain object:¶

{
  "objectClassName": "domain",
  "ldhName": "example.com",
  "ttl": [
    {
      "types": [
        "NS"
      ],
      "value": 3600,
      "remarks": [
        {
          "description": [
            "The .example registry does not permit NS record TTL ",
            "values to be changed."
          ]
        }
      ]
    },
    {
      "types": [
        "DS"
      ],
      "value": 300,
      "events": [
        {
          "eventAction": "last updated",
          "eventActor": "example-registry",
          "eventDate": "2024-01-08T13:52:18Z"
        }
      ],
      "remarks": [
        {
          "description": [
            "For more information about the .example registry policy "
            "relating to DS record TTL changes, see https://example.com"
          ],
          "links": [
            {
              "rel": "related",
              "title": ".Example Registry DNS TTL Policy",
              "value": "https://example.com",
              "href": "https://example.com"
            }
          ]
        }
      ]
    }
  ]
}

Example nameserver object:¶

{
  "objectClassName": "nameserver",
  "ldhName": "ns1.example.com",
  "ttl": [
    {
      "types": [
        "A",
        "AAAA"
      ],
      "value": 86400,
      "remarks": [
        {
          "description": [
            "The .example registry does not permit TTL ",
            "values for nameservers to be changed."
          ]
        }
      ]
    }
  ]
}

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 <iesg@ietf.org>¶

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

5. Change Log

Author's Address