%% You should probably cite rfc9536 instead of this I-D.
@techreport{ietf-regext-rdap-reverse-search-04,
    number =    {draft-ietf-regext-rdap-reverse-search-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/04/},
    author =    {Mario Loffredo and Maurizio Martinelli},
    title =     {{Registration Data Access Protocol (RDAP) Reverse search capabilities}},
    pagetotal = 10,
    year =      2020,
    month =     may,
    day =       18,
    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 functionality. In the RDAP context, an entity can be associated to any defined object class. Therefore, a reverse search can be applied to other use cases than the classic domain-entity scenario. This document describes an RDAP search query extension that allows clients to request a reverse search based on the relationship between an object and the associated entities.},
}