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

Document Type Active Internet-Draft (regext WG)
Authors Mario Loffredo  , Maurizio Martinelli 
Last updated 2020-09-23
Replaces draft-loffredo-regext-rdap-partial-response
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Jasdip Singh
Shepherd write-up Show (last changed 2020-05-08)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has enough positions to pass.
Responsible AD Barry Leiba
Send notices to Jasdip Singh <jasdips@arin.net>
IANA IANA review state Version Changed - Review Needed
Registration Protocols Extensions                            M. Loffredo
Internet-Draft                                             M. Martinelli
Intended status: Standards Track                     IIT-CNR/Registro.it
Expires: March 27, 2021                               September 23, 2020

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

Abstract

   The Registration Data Access Protocol (RDAP) does not include
   capabilities to request partial responses.  Servers will only return
   full responses that include all of the information that a client is
   authorized to receive.  A partial response capability that limits the
   amount of information returned, 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 March 27, 2021.

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

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

   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
     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  . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Negative Answers  . . . . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Implementation Status . . . . . . . . . . . . . . . . . . . .   8
     7.1.  IIT-CNR/Registro.it . . . . . . . . . . . . . . . . . . .   9
     7.2.  APNIC . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Approaches to Partial Response Implementation  . . .  11
     A.1.  Specific Issues Raised by RDAP  . . . . . . . . . . . . .  12
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  13
   Change Log  . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   The use of partial responses 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 the fields in
   each result object is returned.  The benefit is obvious: less data
   transferred over the network means less bandwidth usage, faster
   server responses, less CPU time spent both on the server and the
   client, and less memory usage on the client.

   Currently, RDAP does not provide a client with any way to request a
   partial response.  Servers can only provide the client with a full
   response [RFC7483].  Servers cannot limit the amount of information
   returned in a response based on a client's preferences, and this
   creates inefficiencies.

   The protocol described in this specification extends RDAP search
Show full document text