Registration Data Access Protocol Reverse Search
RFC 9536, “Registration Data Access Protocol Reverse Search”, is a Proposed Standard document published in April 2024 by M. Loffredo, M. Martinelli. The canonical text is published by the RFC Editor.
Abstract
The Registration Data Access Protocol (RDAP) does not include query capabilities for finding the list of domains related to a set of entities matching a given search pattern. Considering that an RDAP entity can be associated with any defined object class and other relationships between RDAP object classes exist, a reverse search can be applied to other use cases besides the classic domain-entity scenario. This document describes an RDAP extension that allows servers to provide a reverse search feature based on the relationship defined in RDAP between an object class for search and any related object class. The reverse search based on the domain-entity relationship is treated as a particular case.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9536 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9535 JSONPath: Query Expressions for JSON
- RFC 9537 Redacted Fields in the Registration Data Access Protocol Response
- RFC 9534 Simple Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation Group
- RFC 9538 Content Delivery Network Interconnection Delegation Using the Automated Certificate Management Environment
- RFC 9533 One-Way and Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation Group
- RFC 9539 Unilateral Opportunistic Deployment of Encrypted Recursive-to- Authoritative DNS
- RFC 9532 HTTP Proxy-Status Parameter for Next-Hop Aliases
- RFC 9540 Discovery of Oblivious Services via Service Binding Records