| Internet-Draft | RDAP DELEG Extension | September 2026 |
| AlBanna & Hollenbeck | Expires 8 March 2027 | [Page] |
This document describes an extension of the Registration Data Access Protocol (RDAP) that includes DNS DELEG values in responses to RDAP domain object queries.¶
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 8 March 2027.¶
Copyright (c) 2026 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.¶
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.¶
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.¶
RDAP responses that contain values described in this document MUST indicate conformance with this specification by including an rdapConformance ([RFC9083]) value of "dnsDeleg". The information needed to register this value in the RDAP Extensions Registry is described in Section 6.¶
Example rdapConformance structure with extension specified:¶
"rdapConformance" :
[
"rdap_level_0",
"dnsDeleg"
]
This specification describes a new data structure that is used to return DNS DELEG information in an RDAP domain response. A new element, "DelegInfos", is defined to return a representation of DNS DELEG and DELEGPARAMS records. As described in Internet-Draft "Extensible Delegation for DNS" [DELEG], a DELEG record is based on "SvcParams" for the SVCB record type RFC 9460 [RFC9460] but differs from it by not having the "SvcPriority" and "TargetName" fields. The "DelegInfos" data structure is a JSON array whose members contain lists of key:value pairs (DelegInfoKey:DelegInfoValue) that describe DNS DELEG record information associated with a registered domain name.¶
TBD: a full specification of the key-value pairs that can appear in a DelegInfos object. It may be possible to cite specific text from [DELEG] and/or [brown-epp-deleg]; we need to see how those specifications evolve.¶
Example 1: A DELEG record type based on a section A.1 of DELEG [DELEG]:¶
"dnsDeleg_DelegInfos": [
{
"server-ipv6": "3fff::33"
"include-delegparam": ["config2.example.net","cname.example.org","Acfg.example.org"]
}
]
¶
Example 2: A DELEG record for domain names Acfg.example.org and subcfg.example.org, based on section A.2 of DELEG [DELEG]:¶
"dnsDeleg_DelegInfos": [
{
"server-ipv6": "2001:db8::6666"
"server-name": "ns3.example.org."
"include-delegparam": ["subcfg.example.org."]
},
{
"server-name": "subcfg.example.org."
"server-ipv4": "203.0.113.1"
"server-ipv6": "3fff::2"
}
]
¶
Example 3: A DELEG record for domain name config2.example.org, based on section A.3 of DELEG [DELEG]:¶
"dnsDeleg_DelegInfos": [
{
"server-name": "b.example.org."
}
]
¶
Example 4: An RDAP response that includes a DelegInfos object based on section A.4.3.1 of DELEG [DELEG]:¶
{
"objectClassName": "domain",
"handle": "2336799_SomeHandle",
"ldhName": "foo.example.",
"links": [
...
],
"status": [
"client delete prohibited",
"client transfer prohibited",
"client update prohibited"
],
"entities": [
...
],
"events": [
...
],
"secureDNS": {
...
},
"dnsDeleg_DelegInfos": [
{
"server-ipv4": ["192.0.2.1",]
"server-ipv6": ["2001:db8::1",]
"server-name": ["ns2.example.net","ns3.example.net"]
}
],
"nameservers": [
{
"objectClassName": "nameserver",
"ldhName": "ns2.example.net"
},
{
"objectClassName": "nameserver",
"ldhName": "ns3.example.net"
}
],
"rdapConformance": [
"rdap_level_0",
"dnsDeleg"
],
"notices": [
...
]
}¶
Example 5: An RDAP response that includes a DelegInfos object based on section A.4.3.2 of DELEG [DELEG]:¶
{
"objectClassName": "domain",
"handle": "2336799_SomeHandle",
"ldhName": "foo.test",
"links": [
{
...
}
],
"status": [
"client delete prohibited",
"client transfer prohibited",
"client update prohibited"
],
"entities": [
...
],
"events": [
...
],
"secureDNS": {
...
},
"dnsDeleg_DelegInfos": [
{
"server-ipv6": ["3fff::33",]
"server-name": ["Acfg.example.org","config2.example.net"]
}
],
"nameservers": [
{
"objectClassName": "nameserver",
"ldhName": "Acfg.example.org"
},
{
"objectClassName": "nameserver",
"ldhName": "config2.example.net"
}
],
"rdapConformance": [
"rdap_level_0",
"dnsDeleg"
],
"notices": [
...
]
}¶
IANA is requested to register the following value in the RDAP Extensions Registry:¶
Extension identifier: dnsDeleg¶
Registry operator: Any¶
Published specification: this document¶
Contact: IETF <iesg@ietf.org>¶
Intended usage: this extension describes how DNS DELEG record values can be included in RDAP responses.¶
The Security Considerations described in RFC 9083 [RFC9083] are applicable to this extension.¶
The following individuals have provided feedback and contributions to the content and direction of this document: James Gould¶