RDAP Redirect with Content
draft-harrison-regext-rdap-redirect-with-content-00

Document Type Active Internet-Draft (individual)
Authors Tom Harrison  , George Michaelson 
Last updated 2020-11-01
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
Internet Engineering Task Force                              T. Harrison
Internet-Draft                                             G. Michaelson
Intended status: Standards Track                                   APNIC
Expires: May 5, 2021                                    November 1, 2020

                       RDAP Redirect with Content
          draft-harrison-regext-rdap-redirect-with-content-00

Abstract

   The Registration Data Access Protocol (RDAP) is used by Regional
   Internet Registries (RIRs) and Domain Name Registries (DNRs) to
   provide access to their resource registration information.  When an
   RDAP service operator has delegated authority for a resource to a
   third party, the operator will configure its RDAP service to redirect
   requests for that resource to the third party.  However, the client
   may be interested in the resource registration data that the first
   service operator has in its own right, for various reasons.  This
   document defines a conformance code that a service operator can use
   to indicate that when redirecting requests, it will also include as
   the body of the response the RDAP object (if any) that it has in its
   own right for the requested resource.

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 May 5, 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

Harrison & Michaelson      Expires May 5, 2021                  [Page 1]
Internet-Draft         RDAP Redirect with Content          November 2020

   (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.  Implementation  . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The Registration Data Access Protocol (RDAP) [RFC7480] is used by
   Regional Internet Registries (RIRs) and Domain Name Registries (DNRs)
   to provide access to their resource registration information.  For a
   client, this typically involves following the bootstrap process
   [RFC7484] to determine the base URL for the query.  When the service
   operator for the base URL has delegated authority for a resource to a
   third party, the operator will configure its RDAP service to redirect
   requests accordingly.

   The client may also be interested in the registration data that the
   original service operator has, though.  For example:

      the original service operator's responses may be in conformance
      with an externally-defined RDAP profile, such that the client
      finds them easier or more useful to deal with than the responses
      provided by the delegated service operator;

      the original service operator's responses may provide useful
      information about larger delegations of resources to delegated
      service operators;

      where both service operators record information about the same
      delegation (e.g. the same specific IP network), the delegated
      operator may omit some information recorded by the original
      operator which is useful to the client; or

Harrison & Michaelson      Expires May 5, 2021                  [Page 2]
Internet-Draft         RDAP Redirect with Content          November 2020
Show full document text