Registration Data Access Protocol (RDAP) Reverse search capabilities
draft-loffredo-regext-rdap-reverse-search-04

Document Type Replaced Internet-Draft (individual)
Last updated 2019-01-31
Replaced by draft-ietf-regext-rdap-reverse-search
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-regext-rdap-reverse-search
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-loffredo-regext-rdap-reverse-search-04.txt

Abstract

The Registration Data Access Protocol (RDAP) does not include query capabilities to find the list of domains related to a set of entities matching a given search pattern. Even if such capabilities, commonly referred as reverse search, respond to some needs not yet readily fulfilled by the current Whois protocol, they have raised concerns from two perspectives: server processing impact and data privacy. Anyway, the impact of the reverse queries on RDAP servers processing is the same as the standard searches and it can be reduced by implementing policies to deal with large result sets, while data privacy risks can be prevented by RDAP access control functionalities. This document describes RDAP query extensions that allow clients to request a reverse search based on the domains- entities relationship.

Authors

Mario Loffredo (mario.loffredo@iit.cnr.it)
Maurizio Martinelli (maurizio.martinelli@iit.cnr.it)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)