RDAP Extension for DNS DELEG

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 13 October 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

This document describes an extension of the Registration Data Access Protocol (RDAP) that includes DNS DELEG values in responses to RDAP domain object queries as described in section 5.3 of RFC 9083 [RFC9083]. The definition of DNS DELEG information is based on concepts described in Internet-Draft "Extensible Delegation for DNS" [DELEG] and Internet-Draft "Extensible Provisioning Protocol (EPP) mapping for DELEG records" [brown-epp-deleg]. This draft is subject to changes that may take place in [DELEG] and [brown-epp-deleg] as they are developed. This document describes how DNS DELEG record information can be included in RDAP responses that contain RDAP domain objects.¶

3. RDAP Conformance

RDAP responses that contain values described in this document MUST indicate conformance with this specification by including an rdapConformance ([RFC9083]) value of "deleg". The information needed to register this value in the RDAP Extensions Registry is described in Section 5.¶

Example rdapConformance structure with extension specified:¶

   "rdapConformance" :
     [
       "rdap_level_0",
       "deleg"
     ]

4. RDAP Response Specification

This specification describes a new data structure that is used to return DNS DELEG information in a RDAP domain response. s described in Internet-Draft "Extensible Delegation for DNS" [DELEG], a DELEG record is a specialized form of a DNS SVCB [RFC9460] resource record. "deleg_delegInfo" is a data structure that contains information that describes DNS DELEG record information associated with a registered domain name. The "deleg_delegInfo" data structure is a list of objects. The list of objects contains the following members whose values and presentations are described in Section 2.1, and Appendix A of RFC 9460 [RFC9460]:¶

1. "priority": a number that represents the SvcPriority value of the record.¶

2. "target": a domain name that represents the TargetName of the record.¶

3. "params": an OPTIONAL object that contains SvcParam key-value pairs.¶

        "deleg_delegInfo": [
          {
            "priority": 0,
            "target": "config1.example.net"
          }
        ]

        "deleg_delegInfo": [
          {
            "priority": 0,
            "target": "config1.example.net"
          {
            "priority": 0,
            "target": "config1.example.org"
        ]

       "deleg_delegInfo": [
          {
            "priority": 1,
            "target": "config3.example.net",
            "params": {
              "ipv6hint": "2001:db8:2423::3"
            }
          }
       ]

       "deleg_delegInfo": [
          {
            "priority": 1,
            "target": "ns1.example.com",
            "params": {
              "ipv4hint": "192.0.2.1",
              "ipv6hint": "2001:DB8::1"
            }
          },
          {
            "priority": 1,
            "target": "ns2.example.net",
            "params": {
              "ipv4hint": "192.0.2.2",
              "ipv6hint": "2001:DB8::2"
            }
          }
       ]

{
  "objectClassName": "domain",
  "handle": "2336799_SomeHandle",
  "ldhName": "EXAMPLE.COM",
  "links": [
    ...
  ],
  "status": [
    "client delete prohibited",
    "client transfer prohibited",
    "client update prohibited"
  ],
  "entities": [
    ...
  ],
  "events": [
    ...
  ],
  "secureDNS": {
    ...
  },
  "deleg_delegInfo": [
     {
        "priority": 0,
        "target" : "config1.example.net",
     }
  ],
  "nameservers": [
    {
      "objectClassName": "nameserver",
      "ldhName": "ns1.example.net"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "ns2.example.net"
    }
  ],
  "rdapConformance": [
    "rdap_level_0",
    "deleg"
  ],
  "notices": [
    ...
  ]
}

{
  "objectClassName": "domain",
  "handle": "2336799_SomeHandle",
  "ldhName": "EXAMPLE.COM",
  "links": [
    {
      ...
    }
  ],
  "status": [
    "client delete prohibited",
    "client transfer prohibited",
    "client update prohibited"
  ],
  "entities": [
    ...
  ],
  "events": [
    ...
  ],
  "secureDNS": {
    ...
  },
  "deleg_delegInfo": [
     {
        "priority": 1,
        "target" : "ns1.example.com",
        "params": {
           "ipv4hint": "192.0.2.1",
           "ipv6hint": "2001:BE8::1"
         }
     },
     {
        "priority": 1,
        "target" : "ns2.example.net",
        "params": {
           "ipv4hint": "192.0.2.2",
           "ipv6hint": "2001:DB8::2"
         }
     }
  ],
  "nameservers": [
    {
      "objectClassName": "nameserver",
      "ldhName": "ns1.example.com"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "ns2.example.com"
    }
  ],
  "rdapConformance": [
    "rdap_level_0",
    "deleg"
  ],
  "notices": [
    ...
  ]
}

5. IANA Considerations

IANA is requested to register the following value in the RDAP Extensions Registry:¶

Extension identifier: deleg¶

Registry operator: Any¶

Published specification: this document¶

Contact: IETF <iesg@ietf.org>¶

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

6. Security Considerations

The Security Considerations described in RFC 9083 [RFC9083] are applicable to this extension.¶

7. Acknowledgments

The following individuals have provided feedback and contributions to the content and direction of this document: James Gould¶

Authors' Addresses