Internet DRAFT - draft-brown-rdap-ttl-extension
draft-brown-rdap-ttl-extension
Registration Extensions (REGEXT) G. Brown
Internet-Draft ICANN
Intended status: Standards Track 2 January 2024
Expires: 5 July 2024
RDAP Extension for DNS Time-To-Live (TTL Values)
draft-brown-rdap-ttl-extension-00
Abstract
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
https://github.com/gbxyz/rdap-ttl-extension.
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 5 July 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
Brown Expires 5 July 2024 [Page 1]
Internet-Draft RDAP TTL Extension January 2024
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 2
3. RDAP Response Specification . . . . . . . . . . . . . . . . . 2
3.1. RDAP Conformance . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. Normative References . . . . . . . . . . . . . . . . . . . . 3
6. Informative References . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
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.
Brown Expires 5 July 2024 [Page 2]
Internet-Draft RDAP TTL Extension January 2024
Example domain object:
{
"objectClassName": "domain",
"ldhName": "example.com",
"ttl_values": {
"NS": 3600,
"DS": 60
}
}
Example nameserver object:
{
"objectClassName": "nameserver",
"ldhName": "ns1.example.com",
"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 <iesg@ietf.org (mailto:iesg@ietf.org)>
*Intended usage:* this extension describes how DNS TTL values can be
included in RDAP responses.
5. Normative References
Brown Expires 5 July 2024 [Page 3]
Internet-Draft RDAP TTL Extension January 2024
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC9083] Hollenbeck, S. and A. Newton, "JSON Responses for the
Registration Data Access Protocol (RDAP)", STD 95,
RFC 9083, DOI 10.17487/RFC9083, June 2021,
<https://www.rfc-editor.org/info/rfc9083>.
6. Informative References
[I-D.ietf-regext-epp-ttl]
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, 14 December
2023, <https://datatracker.ietf.org/doc/html/draft-ietf-
regext-epp-ttl-04>.
Author's Address
Gavin Brown
ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
United States of America
Email: gavin.brown@icann.org
Brown Expires 5 July 2024 [Page 4]
