RFC 9536
Registration Data Access Protocol (RDAP) Reverse Search, April 2024
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Authors:
- M. Loffredo
M. Martinelli - Stream:
- IETF
- Source:
- regext (art)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9536
Discuss this RFC: Send questions or comments to the mailing list regext@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9536
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.