Registration Data Access Protocol (RDAP) Reverse Search
draft-ietf-regext-rdap-reverse-search-26

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-regext-rdap-reverse-search@ietf.org, regext-chairs@ietf.org, regext@ietf.org, rfc-editor@rfc-editor.org, superuser@gmail.com, tomh@apnic.net
Subject: Protocol Action: 'Registration Data Access Protocol (RDAP) Reverse Search' to Proposed Standard (draft-ietf-regext-rdap-reverse-search-25.txt)

The IESG has approved the following document:
- 'Registration Data Access Protocol (RDAP) Reverse Search'
  (draft-ietf-regext-rdap-reverse-search-25.txt) as Proposed Standard

This document is the product of the Registration Protocols Extensions Working
Group.

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/

Ballot Text

Technical Summary

   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.

Working Group Summary

   The working group is medium-sized overall but has a limited number
   of vocal participants.  That small community achieved consensus.  Processing
   appears to have been typical.

Document Quality

   Section 11 identifies existing implementations.

   All appropriate reviews have been completed, especially
   early IANA activity.

Personnel

   The Document Shepherd for this document is Tom Harrison. The Responsible
   Area Director is Murray Kucherawy.

RFC Editor Note