RDAP Mirroring Protocol (RMP)
draft-harrison-regext-rdap-mirroring-00

Document Type Expired Internet-Draft (individual)
Last updated 2019-08-05 (latest revision 2019-02-01)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-mirroring-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. While most clients can retrieve the information they need on an ad hoc basis from the public services maintained by each registry, there are instances where local copies of those remote data sources need to be maintained, for various reasons (e.g. performance requirements). This document defines a protocol for transferring bulk RDAP response data and for keeping a local copy of that data up to date.

Authors

Tom Harrison (tomh@apnic.net)
George Michaelson (ggm@apnic.net)
Andrew Newton (andy@arin.net)

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