Registration Data Access Protocol (RDAP) Partial Response
draft-ietf-regext-rdap-partial-response-07

Document Type Active Internet-Draft (regext WG)
Last updated 2020-04-03 (latest revision 2020-03-13)
Replaces draft-loffredo-regext-rdap-partial-response
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized bibtex
Stream WG state In WG Last Call
Document shepherd Jasdip Singh
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Jasdip Singh <jasdips@arin.net>
Registration Protocols Extensions                            M. Loffredo
Internet-Draft                                             M. Martinelli
Intended status: Standards Track                     IIT-CNR/Registro.it
Expires: September 14, 2020                               March 13, 2020

       Registration Data Access Protocol (RDAP) Partial Response
               draft-ietf-regext-rdap-partial-response-07

Abstract

   The Registration Data Access Protocol (RDAP) does not include
   capabilities to request partial responses.  In fact, according to the
   user authorization, the server can only return full responses.  A
   partial response capability, especially in the case of search
   queries, could bring benefits to both clients and servers.  This
   document describes an RDAP query extension that allows clients to
   specify their preference for obtaining a partial response.

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 September 14, 2020.

Copyright Notice

   Copyright (c) 2020 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
   (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

Loffredo & Martinelli  Expires September 14, 2020               [Page 1]
Internet-Draft            RDAP Partial Response               March 2020

   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
     2.1.  Subsetting Metadata . . . . . . . . . . . . . . . . . . .   3
       2.1.1.  RDAP Conformance  . . . . . . . . . . . . . . . . . .   4
       2.1.2.  Representing Subsetting Links . . . . . . . . . . . .   4
   3.  Dealing with Relationships  . . . . . . . . . . . . . . . . .   5
   4.  Basic Field Sets  . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Negative Answers  . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Implementation Status . . . . . . . . . . . . . . . . . . . .   8
     6.1.  IIT-CNR/Registro.it . . . . . . . . . . . . . . . . . . .   8
     6.2.  APNIC . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Appendix A.  Approaches to Partial Response Implementation  . . .  11
     A.1.  Specific Issues Raised by RDAP  . . . . . . . . . . . . .  12
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   The use of partial response in RESTful API ([REST]) design is very
   common.  The rationale is quite simple: instead of returning objects
   in API responses with all data fields, only a subset of fields in
   each result object is returned.  The benefit is obvious: less data
   transferred over the network means less bandwidth usage, faster
   server response, less CPU time spent both on the server and the
   client, as well as less memory usage on the client.

   Several leading APIs providers (e.g.  LinkedIn [LINKEDIN], Facebook
   [FACEBOOK], Google [GOOGLE]) implement the partial response feature
   by providing an optional query parameter by which users require the
   fields they wish to receive.  Partial response is also considered a
   leading principle by many best practices guidelines in REST APIs
   implementation ([REST-API1], [REST-API2]) in order to improve
Show full document text