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

Document Type Expired Internet-Draft (individual)
Authors Tom Harrison  , George Michaelson 
Last updated 2021-05-05 (latest revision 2020-11-01)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-harrison-regext-rdap-redirect-with-content-00.txt

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.

Authors

Tom Harrison (tomh@apnic.net)
George Michaelson (ggm@apnic.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)