A new Request for Comments is now available in online RFC libraries.
RFC 9536
Title: Registration Data Access Protocol (RDAP)
Reverse Search
Author: M. Loffredo,
M. Martinelli
Status: Standards Track
Stream: IETF
Date: April 2024
Mailbox: [email protected],
[email protected]
Pages: 17
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-regext-rdap-reverse-search-25.txt
URL: https://www.rfc-editor.org/info/rfc9536
DOI: 10.17487/RFC9536
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.
This document is a product of the Registration Protocols Extensions Working
Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext
