%% You should probably cite draft-ietf-regext-rdap-reverse-search instead of this I-D. @techreport{loffredo-regext-rdap-reverse-search-03, number = {draft-loffredo-regext-rdap-reverse-search-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-loffredo-regext-rdap-reverse-search/03/}, author = {Mario Loffredo and Maurizio Martinelli}, title = {{Registration Data Access Protocol (RDAP) Reverse search capabilities}}, pagetotal = 10, year = 2018, month = oct, day = 16, 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 to as reverse search, respond to some needs not yet readily fulfilled by the current Whois protocol, they have raised concern from two perspectives: server processing impact and data privacy. Anyway, the impact of the reverse queries on RDAP servers processing is the same of the standard searches and it can be reduced by implementing policies to deal with big result sets, while data privacy risks can be mitigated by RDAP access control functionalities. This document describes RDAP query extensions that allows clients to request a reverse search based on the domains- entities relationship.}, }