RDAP Mirroring Protocol (RMP)
draft-harrison-regext-rdap-mirroring-00
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-02-01
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
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: August 5, 2019 A. Newton
ARIN
February 1, 2019
RDAP Mirroring Protocol (RMP)
draft-harrison-regext-rdap-mirroring-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. 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.
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 August 5, 2019.
Copyright Notice
Copyright (c) 2019 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
Harrison, et al. Expires August 5, 2019 [Page 1]
Internet-Draft RDAP Mirroring Protocol February 2019
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. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. RDAP Mirroring Protocol Implementation . . . . . . . . . . . 3
2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. File Definitions . . . . . . . . . . . . . . . . . . . . 4
2.2.1. Update Notification File . . . . . . . . . . . . . . 4
2.2.2. Snapshot File . . . . . . . . . . . . . . . . . . . . 5
2.2.3. Delta File . . . . . . . . . . . . . . . . . . . . . 6
2.3. RDAP Objects . . . . . . . . . . . . . . . . . . . . . . 7
2.4. Serial Numbers . . . . . . . . . . . . . . . . . . . . . 9
2.5. Server Use . . . . . . . . . . . . . . . . . . . . . . . 9
2.5.1. Initialization . . . . . . . . . . . . . . . . . . . 9
2.5.2. Publishing Updates . . . . . . . . . . . . . . . . . 10
2.5.3. Consolidation . . . . . . . . . . . . . . . . . . . . 10
2.6. Client Use . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.1. Processing the Update Notification File . . . . . . . 11
2.6.1.1. Initial . . . . . . . . . . . . . . . . . . . . . 11
2.6.1.2. Subsequent . . . . . . . . . . . . . . . . . . . 12
3. Operational Considerations . . . . . . . . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 12
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.1. Normative References . . . . . . . . . . . . . . . . . . 13
7.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
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, constructing an
Show full document text