draft-ietf-weirds-bootstrap-08.txt   draft-ietf-weirds-bootstrap-09.txt 
Network Working Group M. Blanchet Network Working Group M. Blanchet
Internet-Draft Viagenie Internet-Draft Viagenie
Intended status: Standards Track October 13, 2014 Intended status: Standards Track October 13, 2014
Expires: April 16, 2015 Expires: April 16, 2015
Finding the Authoritative Registration Data (RDAP) Service Finding the Authoritative Registration Data (RDAP) Service
draft-ietf-weirds-bootstrap-08.txt draft-ietf-weirds-bootstrap-09.txt
Abstract Abstract
This document specifies a method to find which Registration Data This document specifies a method to find which Registration Data
Access Protocol (RDAP) server is authoritative to answer queries for Access Protocol (RDAP) server is authoritative to answer queries for
a requested scope, such as domain names, IP addresses or Autonomous a requested scope, such as domain names, IP addresses or Autonomous
System numbers. System numbers.
Status of This Memo Status of This Memo
skipping to change at page 2, line 45 skipping to change at page 2, line 45
1. Introduction 1. Introduction
Querying and retrieving registration data from registries are defined Querying and retrieving registration data from registries are defined
in the Registration Data Access Protocol (RDAP) [I-D.ietf-weirds-rdap in the Registration Data Access Protocol (RDAP) [I-D.ietf-weirds-rdap
-query][I-D.ietf-weirds-using-http][I-D.ietf-weirds-json-response]. -query][I-D.ietf-weirds-using-http][I-D.ietf-weirds-json-response].
These documents do not specify where to send the queries. This These documents do not specify where to send the queries. This
document specifies a method to find which server is authoritative to document specifies a method to find which server is authoritative to
answer queries for the requested scope. answer queries for the requested scope.
TLDs, AS numbers, and network blocks are delegated by IANA to Top-level domains(TLD), Autonomous numbers (AS), and network blocks
registrars that then issue further delegations and maintain are delegated by IANA to Internet registries such as TLD registries
information about them. Thus, obviously the bootstrap information and Regional Internet Registries(RIR) that then issue further
needed by RDAP clients is best generated from data and processes delegations and maintain information about them. Thus, obviously the
already maintained by IANA, whose registries already exist at bootstrap information needed by RDAP clients is best generated from
[ipv4reg], [ipv6reg], [asreg], and [domainreg]. data and processes already maintained by IANA, whose registries
already exist at [ipv4reg], [ipv6reg], [asreg], and [domainreg].
The required new functionality in support of RDAP could be The required new functionality in support of RDAP could be
accomplished by augmenting these registries to contain new fields, or accomplished by augmenting these registries to contain new fields, or
creating second parallel registries containing the extra fields whose creating second parallel registries containing the extra fields whose
entries mirror the existing ones. Either approach will satisfy the entries mirror the existing ones. Either approach will satisfy the
needs of this document. This document requests IANA to make these needs of this document. This document requests IANA to make these
registries available for the specific purpose of RDAP use, herein registries available for the specific purpose of RDAP use, herein
named RDAP Bootstrap Service Registries. An RDAP client fetches the named RDAP Bootstrap Service Registries. An RDAP client fetches the
RDAP Bootstrap Service Registries, extracts the data and then does a RDAP Bootstrap Service Registries, extracts the data and then does a
match with the query data to find the authoritative registration data match with the query data to find the authoritative registration data
skipping to change at page 3, line 34 skipping to change at page 3, line 34
The RDAP Bootstrap Service Registries, as specified in Section 12, The RDAP Bootstrap Service Registries, as specified in Section 12,
will be made available as JSON [RFC7159] objects, to be retrieved via will be made available as JSON [RFC7159] objects, to be retrieved via
HTTP from a location as specified by IANA. The JSON object for each HTTP from a location as specified by IANA. The JSON object for each
registry will start with a series of members that contain metadata registry will start with a series of members that contain metadata
about the registry such as a version identifier, a timestamp of the about the registry such as a version identifier, a timestamp of the
publication date of the registry and a description. Following that publication date of the registry and a description. Following that
is a "services" member which contains the registry items themselves, is a "services" member which contains the registry items themselves,
as an array. Each item of the array contains a second-level array, as an array. Each item of the array contains a second-level array,
with two elements, each of them being a third-level array. with two elements, each of them being a third-level array.
There is no assumption of sorting except that the two arrays found in The first third-level array, named 'Entry array', contains all
each second-level array MUST appear in the correct order: The entries entries that have the same set of base RDAP URLs. The second third-
level array, named 'Service URL array', contains the list of base
RDAP URLs usable for the entries found in the 'Entry array'. There
is no assumption of sorting except that the two arrays found in each
second-level array MUST appear in the correct order: The entries
array are followed by the service URL array. An example structure of array are followed by the service URL array. An example structure of
the JSON output of a RDAP Bootstrap Service Registry is illustrated: the JSON output of a RDAP Bootstrap Service Registry is illustrated:
{ {
"version": "1.0", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ", "publication": "YYYY-MM-DDTHH:MM:SSZ",
"description": "Some text", "description": "Some text",
"services": [ "services": [
[ [
["entry1", "entry2", "entry3"], ["entry1", "entry2", "entry3"],
 End of changes. 3 change blocks. 
9 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/