APNIC's Tom Harrison presents on RDAP mirroring at IETF 104 in Prague, Czech Republic from 23 to 29 March 2019.

1. 1
draft-harrison-regext-rdap-mirroring
●●●
Tom Harrison (tomh@apnic.net)
George Michaelson (ggm@apnic.net)
Andy Newton (andy@arin.net)
IETF 104 REGEXT Working Group

2. 2
What is RDAP mirroring?
●
A protocol for retrieving all of the data from an RDAP server’s data
store, and for keeping a local copy of that data up to date over time
●
Use cases:
– When the overhead of querying the remote RDAP server is too
high
– When there’s a need to analyse the RDAP data set as a whole
– When a client wants to provide access in its own right to the
remote RDAP server’s data

3. 3
How does it work?
●
The server hosts an update notification file (UNF),
which contains links to a snapshot and a series of
deltas
●
A snapshot contains all of the server’s RDAP data as at
the time of generation
●
A delta is used to record changes that have happened
since the snapshot was generated

4. 4
RDAP
Server
1. Request UNF
2. Return UNF
Mirroring
Client
RDAP
Updater
{ “version”: 1,
“refresh”: 3600,
“snapshot”: {
“uri”: “https://example.com/snapshot-1.json”,
“serial”: 1,
},
“deltas”: [] }

5. 5
RDAP
Server
3. Request Snapshot
4. Return Snapshot
Mirroring
Client
RDAP
Updater
{ “version” : 1,
“serial”: 1,
“objects”: [
{ “id”: “https://example.org/I1”,
“object”: {
“rdapConformance”: [ “rdap_level_0” ],
“objectClassName”: “ip network”,
“startAddress”: “192.0.2.0”,
... } },
...
] }

6. 6
RDAP
Server
Mirroring
Client
RDAP
Updater
{ “rdapConformance”: [ “rdap_level_0” ],
“objectClassName”: “ip network”,
“startAddress”: “192.0.2.0”,
“name”: “updated-name”,
... }
5. Send updates
6. Updates OK

7. 7
RDAP
Server
7. Request UNF
8. Return UNF
Mirroring
Client
RDAP
Updater
{ “version”: 1,
“refresh”: 3600,
“snapshot”: {
“uri”: “https://example.com/snapshot-1.json”,
“serial”: 1
},
“deltas”: [
{ “uri”: “https://example.com/delta-2.json”,
“serial”: 2 }
] }

8. 8
RDAP
Server
9. Request Delta
10. Return Delta
Mirroring
Client
RDAP
Updater
{ “version” : 1,
“serial”: 2,
“removed_objects”: [],
“added_or_updated_objects”: [
{ “id”: “https://example.org/I1”,
“object”: {
“rdapConformance”: [ “rdap_level_0” ],
“objectClassName”: “ip network”,
“startAddress”: “192.0.2.0”,
“name”: “updated-name”,
... } },
] }

9. 9
Miscellaneous features
●
Define default set of response attributes
– Terms and conditions, port43, etc.
●
Refer to other RDAP objects by reference
●
Server may specify requested refresh rate

10. 10
Open topics
●
Is this useful in the domain name context?
●
Not looking for adoption just yet