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

Document Type Active Internet-Draft (individual)
Last updated 2017-10-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Registration Protocols Extensions                            M. Loffredo
Internet-Draft                                             M. Martinelli
Intended status: Standards Track                     IIT-CNR/Registro.it
Expires: April 6, 2018                                   October 3, 2017

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

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 functionalites.
   This document describes RDAP query extensions that allows clients to
   request a reverse search based on the domains-entities relationship.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 6, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Loffredo & Martinelli     Expires April 6, 2018                 [Page 1]
Internet-Draft             RDAP Reverse search              October 2017

   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   3
   2.  RDAP Path Segment Specification . . . . . . . . . . . . . . .   3
   3.  Implementation Considerations . . . . . . . . . . . . . . . .   4
   4.  Implementation Status . . . . . . . . . . . . . . . . . . . .   4
     4.1.  IIT-CNR/Registro.it . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Reverse Whois is a service provided by many web applications that
   allow users to find domain names owned by an individual person or
   company starting from the owner details (like name, email).  Even if
   the availability of this service might raise some objections due to
   potential privacy risks, ICANN itself, in its report about Next-Gen
   Registration Directory Service (RDS) [ICANN], states that it is
   allowed when driven by some permissible purposes (e.g. legal actions,
   criminal investigations) and if it provides adequate policies to
   enforce the requestor accreditation, authentication, authorization,
   and terms and conditions of data use.

   It is well known that these features are not implemented in Whois
   ([RFC3912]), while they are in RDAP.  In fact, RDAP relies on
   security features, available in the HTTP protocol to support access
   control based on local policy ([RFC7481]).

   Another objection to the implementation of Reverse Whois is connected
Show full document text