The RDAP Bootstrap Service Registries, as specified in Section 12
below, have been made available as JSON [RFC 8259
] objects, which can be retrieved via HTTP from locations specified by IANA. The JSON object for each registry contains a series of members containing metadata about the registry such as a version identifier, a timestamp of the publication date of the registry, and a description. Additionally, a "services" member contains the registry items themselves, as an array. Each item of the array contains a second-level array, with two elements, each of them being a third-level array.
Each element of the Services Array is a second-level array with two elements: in order, an Entry Array and a Service URL Array.
The Entry Array contains all entries that have the same set of base RDAP URLs. The Service URL Array contains the list of base RDAP URLs usable for the entries found in the Entry Array. Elements within these two arrays are not ordered in any way.
An example structure of the JSON output of an RDAP Bootstrap Service Registry is illustrated:
"description": "Some text",
["entry1", "entry2", "entry3"],
The formal syntax is described in Section 10
The "version" corresponds to the format version of the registry. This specification defines version "1.0".
The syntax of the "publication" value conforms to the Internet date/time format [RFC 3339
]. The value is the latest update date of the registry by IANA.
The optional "description" string can contain a comment regarding the content of the bootstrap object.
Per [RFC 7258
], in each array of base RDAP URLs, the secure versions of the transport protocol SHOULD
be preferred and tried first. For example, if the base RDAP URLs array contains both HTTPS and HTTP URLs, the bootstrap client SHOULD
try the HTTPS version first.
Base RDAP URLs MUST
have a trailing "/" character because they are concatenated to the various segments defined in [RFC 9082
JSON names MUST
follow the format recommendations of Section 6
of RFC 7480
. Any unrecognized JSON object properties or values MUST
be ignored by implementations.
Internationalized Domain Name labels used as entries or base RDAP URLs in the registries defined in this document MUST
be only represented using their A-label form as defined in [RFC 5890
All Domain Name labels used as entries or base RDAP URLs in the registries defined in this document MUST
be only represented in lowercase.