Registration Data Access Protocol (RDAP) Extension for Status Set

Introduction This document describes an Registration Data Access Protocol (RDAP) extension for including status sets assigned to RDAP object classes, such as the Domain Object Class and the Nameserver Object Class in . There can be many overlapping reasons for each of the "status" member values, such as implementing a lock service, complying with a court order, or addressing domain abuse. A status set defines an object representing the reason for setting a "status" value, can effectively manage the overlapping reasons of individual "status" values using the status sets. This RDAP extension supports returning the assigned client and server status sets with additional data members, such as the "type", the mapped "status" values, whether the status set is inherited either from the parent object (domain) or to child objects (nameservers), and whether the status set is directly assigned. This document is complementary to the Extensible Provisioning Protocol (EPP) Status Set Extension [I-D.gould-regext-epp-status-set], but registry operators do not need to implement that extension in their EPP server in order to implement this RDAP extension.

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 when, and only when, they appear in all capitals, as shown here. The example RDAP responses don't include all of the RDAP response members, but are only representative of the members that are relavant to this extension.

RDAP Conformance Servers implementing this extension MUST include the string "statusSet" in the "rdapConformance" () array of all relevant RDAP responses. The registration of the "statusSet" extension identifier is described in .

"statusSet_data" Member The status set information is conveyed via a new top-level object member named "statusSet_data" within the object class that the status sets are assigned to. A status set is an object that defines the reason for the "status" member values for an RDAP object class, such as the Domain Object Class and the Nameserver Object Class in . The status set can also be used as a marker status set when there are no mapped "status" member values that can drive additional business logic and publishing use cases. An object can have many assigned status sets, and the status sets can include an overlapping set of "status" member values. The "status" member value will be assigned to the object if there is at least one set set assigned to the object with the mapped "status" member value. The "status" member value will be unassigned from the object when all status sets are unassigned with the mapped "status" member value. For example, both the "Registrar Lock" status set and the "Auth Token Lock" status set are mapped to the "client update prohibited" "status" member value, where if either of the status sets are assigned to the object, the "client update prohibited" "status" member value will be assigned. The "client update prohibited" "status" member value will be unassigned if both "Registrar Lock" status set and "Auth Token Lock" status sets are unassigned. The "statusSet_data" member includes a list of status set objects containing the following members:

name -- the unique name for the status set that is up to server policy. Example names include "Registrar Lock", "Auth Token Lock", and "Registry Lock". There is a reserved value of "REDACTED" that is used for a server status set, where the name must be redacted based on server policy.
type -- indicates whether the status set is a client status set with a value of "client" or the status set is a server status set with a value of "server". Only servers can set and unset a server status set.
inherited -- OPTIONAL boolean with a default value of false that indicates inheritable downward to child objects (Nameservers) when applied to Domain Objects, and inherited upward from parent object (Domain) when applied to NameServer object.
assigned -- OPTIONAL boolean with a default value of true that indicates whether the status set is directly assigned to the object. The value can be false for an inherited status set.
created -- OPTIONAL date and time that the status set was assigned to the object.
status -- An array of "status" values in that are mapped to the status set.

Domain object including the "statusSet_data" member { "objectClassName": "domain", "handle": "XXX", "ldhName": "example.com", "status": [ "client update prohibited", "client delete prohibited", "client transfer prohibited" ], "rdapConformance": ["rdap_level_0", "statusSet"], "statusSet_data": [ { "name": "Auth Token Lock", "type": "client", "inherited": true, "assigned": true, "created": "2026-05-03T09:00:00.0Z", "status": [ "client update prohibited", "client delete prohibited", "client transfer prohibited" ] } ] }

Domain object including the "statusSet_data" member that includes the assigned Client Status Sets ("Auth Token Lock" and "Registrar Lock") and the assigned Server Status Set ("Registry Lock") { "objectClassName": "domain", "handle": "XXX", "ldhName" : "example.com", "status" : [ "client update prohibited", "client delete prohibited", "client transfer prohibited", "server update prohibited", "server delete prohibited", "server transfer prohibited" ], "rdapConformance": ["rdap_level_0", "statusSet"], "statusSet_data": [ { "name": "Auth Token Lock", "type": "client", "inherited": true, "assigned": true, "created": "2026-05-03T09:00:00.0Z", "status": [ "client update prohibited", "client delete prohibited", "client transfer prohibited" ] }, { "name": "Registrar Lock", "type": "client", "inherited": false, "assigned": true, "created": "2026-05-03T09:00:00.0Z", "status": [ "client update prohibited", "client delete prohibited", "client transfer prohibited" ] }, { "name": "Registry Lock", "type": "server", "inherited": false, "assigned": true, "created": "2026-05-03T09:10:00.0Z", "status": [ "server update prohibited", "server delete prohibited", "server transfer prohibited" ] } ] }

Nameserver object includes an the inherited Client Status Set ("Auth Token Lock") from the parent domain name { "objectClassName": "nameserver", "handle": "XXXX", "ldhName" : "ns1.xn--fo-5ja.example", "status" : [ "active" ], "rdapConformance": ["rdap_level_0", "statusSet"], "statusSet_data": [ { "name": "Auth Token Lock", "type": "client", "inherited": true, "assigned": false, "created": "2026-05-03T09:00:00.0Z", "status": [ "client update prohibited", "client delete prohibited", "client transfer prohibited" ] } ] }

This extension supports the Point Versioning defined in with a Point Extension Version Identifier of "statusSet-0.1". When there are interface changes to the extension, the Point Extension Version Identifier will be incremented, which may not match the draft version number. When the draft becomes a working group document and passes Working Group Last Call (WGLC), the Point Extension Version Identifier will be changed to "statusSet-1.0".

IANA Considerations

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

Extension identifier:: statusSet
Registry operator:: Any
Published specification:: This document.
Contact:: IETF <iesg@ietf.org>
Intended usage:: This extension identifies RDAP extension for status set information.

Security Considerations Status set data may include legal and policy implications. Servers MUST ensure that disclosure of this information complies with applicable data protection laws and policies.