Registration Data Access Protocol (RDAP) Reverse Search
RFC 9536
Revision differences
Document history
Date | By | Action |
---|---|---|
2024-04-16
|
(System) | IANA registries were updated to include RFC9536 |
2024-04-11
|
(System) | Received changes through RFC Editor sync (created document RFC 9536, created became rfc relationship between draft-ietf-regext-rdap-reverse-search and RFC 9536, set abstract to 'The … Received changes through RFC Editor sync (created document RFC 9536, created became rfc relationship between draft-ietf-regext-rdap-reverse-search and RFC 9536, set abstract to '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.', set pages to 17, set standardization level to Proposed Standard, added RFC published event at 2024-04-11) |
2024-04-11
|
(System) | RFC published |