draft-ietf-regext-rfc7484bis-04.txt   draft-ietf-regext-rfc7484bis-05.txt 
Network Working Group M. Blanchet Network Working Group M. Blanchet
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 7484 (if approved) 2 September 2021 Obsoletes: 7484 (if approved) 25 January 2022
Intended status: Standards Track Intended status: Standards Track
Expires: 6 March 2022 Expires: 29 July 2022
Finding the Authoritative Registration Data (RDAP) Service Finding the Authoritative Registration Data (RDAP) Service
draft-ietf-regext-rfc7484bis-04 draft-ietf-regext-rfc7484bis-05
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. This document obsoletes RFC7484. System numbers. This document obsoletes RFC7484.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 6 March 2022. This Internet-Draft will expire on 29 July 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Revised BSD License text as
as described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Structure of the RDAP Bootstrap Service Registries . . . . . 3 3. Structure of the RDAP Bootstrap Service Registries . . . . . 3
4. Bootstrap Service Registry for Domain Name Space . . . . . . 5 4. Bootstrap Service Registry for Domain Name Space . . . . . . 5
5. Bootstrap Service Registries for Internet Numbers . . . . . . 6 5. Bootstrap Service Registries for Internet Numbers . . . . . . 6
5.1. Bootstrap Service Registry for IPv4 Address Space . . . . 6 5.1. Bootstrap Service Registry for IPv4 Address Space . . . . 6
5.2. Bootstrap Service Registry for IPv6 Address Space . . . . 7 5.2. Bootstrap Service Registry for IPv6 Address Space . . . . 7
skipping to change at page 2, line 32 skipping to change at page 2, line 32
11. Security Considerations . . . . . . . . . . . . . . . . . . . 12 11. Security Considerations . . . . . . . . . . . . . . . . . . . 12
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 13 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 13
12.1. RDAP Browser Mobile Application . . . . . . . . . . . . 13 12.1. RDAP Browser Mobile Application . . . . . . . . . . . . 13
12.2. ICANN Lookup Web Application . . . . . . . . . . . . . . 14 12.2. ICANN Lookup Web Application . . . . . . . . . . . . . . 14
12.3. ARIN Implementation . . . . . . . . . . . . . . . . . . 14 12.3. ARIN Implementation . . . . . . . . . . . . . . . . . . 14
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
13.1. Bootstrap Service Registry for IPv4 Address Space . . . 16 13.1. Bootstrap Service Registry for IPv4 Address Space . . . 16
13.2. Bootstrap Service Registry for IPv6 Address Space . . . 16 13.2. Bootstrap Service Registry for IPv6 Address Space . . . 16
13.3. Bootstrap Service Registry for AS Number Space . . . . . 16 13.3. Bootstrap Service Registry for AS Number Space . . . . . 16
13.4. Bootstrap Service Registry for Domain Name Space . . . . 16 13.4. Bootstrap Service Registry for Domain Name Space . . . . 16
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
14.1. Normative References . . . . . . . . . . . . . . . . . . 17 14.1. Normative References . . . . . . . . . . . . . . . . . . 16
14.2. Informative References . . . . . . . . . . . . . . . . . 17 14.2. Informative References . . . . . . . . . . . . . . . . . 17
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 19 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 19
Changes since RFC7484 . . . . . . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
Querying and retrieving registration data from registries are defined Querying and retrieving registration data from registries are defined
in Registration Data Access Protocol (RDAP) [RFC7480] [RFC7481] in Registration Data Access Protocol (RDAP) [RFC7480] [RFC7481]
[RFC9082] [RFC9083]. These documents do not specify where to send [RFC9082] [RFC9083]. These documents do not specify where to send
the queries. This document specifies a method to find which server the queries. This document specifies a method to find which server
is authoritative to answer queries for the requested scope. is authoritative to answer queries for the requested scope.
skipping to change at page 3, line 17 skipping to change at page 3, line 17
registries and Regional Internet Registries (RIRs) that then issue registries and Regional Internet Registries (RIRs) that then issue
further delegations and maintain information about them. Thus, the further delegations and maintain information about them. Thus, the
bootstrap information needed by RDAP clients is best generated from bootstrap information needed by RDAP clients is best generated from
data and processes already maintained by IANA; the relevant data and processes already maintained by IANA; the relevant
registries already exist at [ipv4reg], [ipv6reg], [asreg], and registries already exist at [ipv4reg], [ipv6reg], [asreg], and
[domainreg]. This document obsoletes [RFC7484]. [domainreg]. This document obsoletes [RFC7484].
Per this document, IANA has created new registries based on a JSON Per this document, IANA has created new registries based on a JSON
format specified in this document, herein named RDAP Bootstrap format specified in this document, herein named RDAP Bootstrap
Service Registries. These new registries are based on the existing Service Registries. These new registries are based on the existing
entries of the above mentioned registries. An RDAP client fetches entries of the above-mentioned registries. An RDAP client fetches
the RDAP Bootstrap Service Registries, extracts the data, and then the RDAP Bootstrap Service Registries, extracts the data, and then
performs a match with the query data to find the authoritative performs a match with the query data to find the authoritative
registration data server and appropriate query base URL. registration data server and appropriate query base URL.
2. Conventions Used in This Document 2. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
skipping to change at page 3, line 49 skipping to change at page 3, line 49
themselves, as an array. Each item of the array contains a second- themselves, as an array. Each item of the array contains a second-
level array, with two elements, each of them being a third-level level array, with two elements, each of them being a third-level
array. array.
Each element of the Services Array is a second-level array with two Each element of the Services Array is a second-level array with two
elements: in order, an Entry Array and a Service URL Array. elements: in order, an Entry Array and a Service URL Array.
The Entry Array contains all entries that have the same set of base 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 RDAP URLs. The Service URL Array contains the list of base RDAP URLs
usable for the entries found in the Entry Array. Elements within usable for the entries found in the Entry Array. Elements within
these two arrays are not sorted in any way. these two arrays are not ordered in any way.
An example structure of the JSON output of a RDAP Bootstrap Service An example structure of the JSON output of a RDAP Bootstrap Service
Registry is illustrated: 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": [
[ [
skipping to change at page 4, line 46 skipping to change at page 4, line 46
content of the bootstrap object. content of the bootstrap object.
Per [RFC7258], in each array of base RDAP URLs, the secure versions Per [RFC7258], in each array of base RDAP URLs, the secure versions
of the transport protocol SHOULD be preferred and tried first. For of the transport protocol SHOULD be preferred and tried first. For
example, if the base RDAP URLs array contains both HTTPS and HTTP example, if the base RDAP URLs array contains both HTTPS and HTTP
URLs, the bootstrap client SHOULD try the HTTPS version first. URLs, the bootstrap client SHOULD try the HTTPS version first.
Base RDAP URLs MUST have a trailing "/" character because they are Base RDAP URLs MUST have a trailing "/" character because they are
concatenated to the various segments defined in [RFC9082]. concatenated to the various segments defined in [RFC9082].
JSON names MUST follow the format recommendations of [RFC7480]. Any JSON names MUST follow the format recommendations of section 6 of
unrecognized JSON object properties or values MUST be ignored by [RFC7480]. Any unrecognized JSON object properties or values MUST be
implementations. ignored by implementations.
Internationalized Domain Name labels used as entries or base RDAP Internationalized Domain Name labels used as entries or base RDAP
URLs in the registries defined in this document MUST be only URLs in the registries defined in this document MUST be only
represented using their A-label form as defined in [RFC5890]. represented using their A-label form as defined in [RFC5890].
All Domain Name labels used as entries or base RDAP URLs in the All Domain Name labels used as entries or base RDAP URLs in the
registries defined in this document MUST be only represented in registries defined in this document MUST be only represented in
lowercase. lowercase.
4. Bootstrap Service Registry for Domain Name Space 4. Bootstrap Service Registry for Domain Name Space
The JSON output of this registry contains domain label entries The JSON output of this registry contains domain label entries
attached to the root, grouped by base RDAP URLs, as shown in this attached to the root, grouped by base RDAP URLs, as shown in this
example. example.
{ {
"version": "1.0", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ", "publication": "2024-01-07T10:11:12Z",
"description": "Some text", "description": "Some text",
"services": [ "services": [
[ [
["net", "com"], ["net", "com"],
[ [
"https://registry.example.com/myrdap/" "https://registry.example.com/myrdap/"
] ]
], ],
[ [
["org", "mytld"], ["org", "mytld"],
skipping to change at page 6, line 33 skipping to change at page 6, line 33
The entry for the root of the domain name space is specified as "". The entry for the root of the domain name space is specified as "".
5. Bootstrap Service Registries for Internet Numbers 5. Bootstrap Service Registries for Internet Numbers
This section discusses IPv4 and IPv6 address space and Autonomous This section discusses IPv4 and IPv6 address space and Autonomous
System numbers. System numbers.
For IP address space, the authoritative registration data service is For IP address space, the authoritative registration data service is
found by doing a longest match of the target address with the values found by doing a longest match of the target address with the values
of the arrays in the corresponding RDAP Bootstrap Service Registry of the arrays in the corresponding RDAP Bootstrap Service Registry
for Address Space. The longest match is done the same way as for for Address Space. The longest match is done the same way as in
routing: the addresses are converted in binary form and then the packet forwarding: the addresses are converted in binary form and
binary strings are compared to find the longest match up to the then the binary strings are compared to find the longest match up to
specified prefix length. The values contained in the second element the specified prefix length. The values contained in the second
of the array are the base RDAP URLs as described in [RFC9082]. The element of the array are the base RDAP URLs as described in
longest match method enables covering prefixes of a larger address [RFC9082]. The longest match method enables covering prefixes of a
space pointing to one base RDAP URL while more specific prefixes larger address space pointing to one base RDAP URL while more
within the covering prefix are being served by another base RDAP URL. specific prefixes within the covering prefix are being served by
another base RDAP URL.
5.1. Bootstrap Service Registry for IPv4 Address Space 5.1. Bootstrap Service Registry for IPv4 Address Space
The JSON output of this registry contains IPv4 prefix entries, The JSON output of this registry contains IPv4 prefix entries,
specified in Classless Inter-domain Routing (CIDR) format [RFC4632] specified in Classless Inter-domain Routing (CIDR) format [RFC4632]
and grouped by RDAP URLs, as shown in this example. and grouped by RDAP URLs, as shown in this example.
{ {
"version": "1.0", "version": "1.0",
"publication": "2024-01-07T10:11:12Z", "publication": "2024-01-07T10:11:12Z",
skipping to change at page 7, line 34 skipping to change at page 7, line 34
[ [
"https://example.net/rdaprir2/", "https://example.net/rdaprir2/",
"http://example.net/rdaprir2/" "http://example.net/rdaprir2/"
] ]
] ]
] ]
} }
For example, a query for "192.0.2.1/25" matches the "192.0.0.0/8" For example, a query for "192.0.2.1/25" matches the "192.0.0.0/8"
entry and the "192.0.2.0/24" entry in the example registry above. entry and the "192.0.2.0/24" entry in the example registry above.
The latter is chosen by the client given the longest match. The base The latter is chosen by the client because it is the longest match.
RDAP URL for this query is then taken from the second element of the The base RDAP URL for this query is then taken from the second
array, which is an array of base RDAP URLs valid for this entry. The element of the array, which is an array of base RDAP URLs valid for
client chooses one of the base URLs from this array; in this example, this entry. The client chooses one of the base URLs from this array;
it chooses the only one available, "https://example.org/". The in this example, it chooses the only one available,
{resource} specified in [RFC9082] is then appended to the base URL to "https://example.org/". The {resource} specified in [RFC9082] is
complete the query. The complete query is then "https://example.org/ then appended to the base URL to complete the query. The complete
ip/192.0.2.1/25". query is then "https://example.org/ip/192.0.2.1/25".
5.2. Bootstrap Service Registry for IPv6 Address Space 5.2. Bootstrap Service Registry for IPv6 Address Space
The JSON output of this registry contains IPv6 prefix entries, using The JSON output of this registry contains IPv6 prefix entries, using
[RFC4291] text representation of the address prefixes format, grouped [RFC5952] text representation of the address prefixes format, grouped
by base RDAP URLs, as shown in this example. by base RDAP URLs, as shown in this example.
{ {
"version": "1.0", "version": "1.0",
"publication": "2024-01-07T10:11:12Z", "publication": "2024-01-07T10:11:12Z",
"description": "RDAP Bootstrap file for example registries.", "description": "RDAP Bootstrap file for example registries.",
"services": [ "services": [
[ [
["2001:db8::/34"], ["2001:db8::/34"],
[ [
skipping to change at page 8, line 34 skipping to change at page 8, line 34
[ [
"https://example.net/rdaprir2/", "https://example.net/rdaprir2/",
"http://example.net/rdaprir2/" "http://example.net/rdaprir2/"
] ]
] ]
] ]
} }
For example, a query for "2001:db8:1000::/48" matches the For example, a query for "2001:db8:1000::/48" matches the
"2001:db8::/34" entry and the "2001:db8:1000::/36" entry in the "2001:db8::/34" entry and the "2001:db8:1000::/36" entry in the
example registry above. The latter is chosen by the client given the example registry above. The latter is chosen by the client because
longest match. The base RDAP URL for this query is then taken from it is the longest match. The base RDAP URL for this query is then
the second element of the array, which is an array of base RDAP URLs taken from the second element of the array, which is an array of base
valid for this entry. The client chooses one of the base URLs from RDAP URLs valid for this entry. The client chooses one of the base
this array; in this example, it chooses "https://example.net/ URLs from this array; in this example, it chooses
rdaprir2/" because it's the secure version of the protocol. The "https://example.net/rdaprir2/" because it's the secure version of
segment specified in [RFC9082] is then appended to the base URL to the protocol. The segment specified in [RFC9082] is then appended to
complete the query. The complete query is, therefore, the base URL to complete the query. The complete query is,
"https://example.net/rdaprir2/ip/2001:0db8:1000::/48". If the target therefore, "https://example.net/rdaprir2/ip/2001:db8:1000::/48". If
RDAP server does not answer, the client can then use another URL the target RDAP server does not answer, the client can then use
prefix from the array. another URL prefix from the array.
5.3. Bootstrap Service Registry for AS Number Space 5.3. Bootstrap Service Registry for AS Number Space
The JSON output of this registry contains Autonomous Systems number The JSON output of this registry contains Autonomous Systems number
ranges entries, grouped by base RDAP URLs, as shown in this example. ranges entries, grouped by base RDAP URLs, as shown in this example.
The Entry Array is an array containing the list of AS number ranges The Entry Array is an array containing the list of AS number ranges
served by the base RDAP URLs found in the second element. The array served by the base RDAP URLs found in the second element. The array
always contains two AS numbers represented in decimal format that always contains two AS numbers represented in decimal format that
represents the range of AS numbers between the two elements of the represents the range of AS numbers between the two elements of the
array. A single AS number is represented as a range of two identical array, where values are in increasing order (e.g. 100-200, not
AS numbers. AS numbers are represented as 'asplain' as defined in 200-100). A single AS number is represented as a range of two
[RFC5396]. identical AS numbers. AS numbers are represented as 'asplain' as
defined in [RFC5396]. Ranges MUST NOT overlap.
{ {
"version": "1.0", "version": "1.0",
"publication": "2024-01-07T10:11:12Z", "publication": "2024-01-07T10:11:12Z",
"description": "RDAP Bootstrap file for example registries.", "description": "RDAP Bootstrap file for example registries.",
"services": [ "services": [
[ [
["64496-64496"], ["64496-64496"],
[ [
"https://rir3.example.com/myrdap/" "https://rir3.example.com/myrdap/"
skipping to change at page 10, line 23 skipping to change at page 10, line 23
prefix from the array. prefix from the array.
6. Entity 6. Entity
Entities (such as contacts, registrants, or registrars) can be Entities (such as contacts, registrants, or registrars) can be
queried by handle as described in [RFC9082]. Since there is no queried by handle as described in [RFC9082]. Since there is no
global namespace for entities, this document does not describe how to global namespace for entities, this document does not describe how to
find the authoritative RDAP server for entities. However, it is find the authoritative RDAP server for entities. However, it is
possible that, if the entity identifier was received from a previous possible that, if the entity identifier was received from a previous
query, the same RDAP server could be queried for that entity, or the query, the same RDAP server could be queried for that entity, or the
entity identifier itself is a fully referenced URL that can be entity identifier itself is a fully qualified URL that can be
queried. The mechanism described in [RFC8521] MAY also be used. queried. The mechanism described in [RFC8521] MAY also be used.
7. Non-existent Entries or RDAP URL Values 7. Non-existent Entries or RDAP URL Values
The registries may not contain the requested value. In these cases, The registries may not contain the requested value. In these cases,
there is no known RDAP server for that requested value, and the there is no known RDAP server for that requested value, and the
client SHOULD provide an appropriate error message to the user. client SHOULD provide an appropriate error message to the user.
8. Deployment and Implementation Considerations 8. Deployment and Implementation Considerations
skipping to change at page 12, line 32 skipping to change at page 12, line 32
VALUE a STRING VALUE a STRING
* description: a MEMBER with MEMBER-NAME "description" and MEMBER- * description: a MEMBER with MEMBER-NAME "description" and MEMBER-
VALUE a STRING VALUE a STRING
* services-list: a MEMBER with MEMBER-NAME "services" and MEMBER- * services-list: a MEMBER with MEMBER-NAME "services" and MEMBER-
VALUE a services-array VALUE a services-array
* services-array: an ARRAY, where each ARRAY-VALUE is a service * services-array: an ARRAY, where each ARRAY-VALUE is a service
* service: an ARRAY of 2 elements, where the first ARRAY-VALUE is a * service: an ARRAY of 2 elements, where the first ARRAY-VALUE is an
an entry-list and the second ARRAY-VALUE is a service-uri-list entry-list and the second ARRAY-VALUE is a service-uri-list
* entry-list: an ARRAY, where each ARRAY-VALUE is an entry * entry-list: an ARRAY, where each ARRAY-VALUE is an entry
* entry: a STRING * entry: a STRING
* service-uri-list: an ARRAY, where each ARRAY-VALUE is a service- * service-uri-list: an ARRAY, where each ARRAY-VALUE is a service-
uri uri
* service-uri: a STRING * service-uri: a STRING
skipping to change at page 15, line 16 skipping to change at page 15, line 16
differs from the normal IANA registry processes: these registries are differs from the normal IANA registry processes: these registries are
generated from the data, processes, and policies maintained by IANA generated from the data, processes, and policies maintained by IANA
in their allocation registries ([ipv4reg], [ipv6reg], [asreg], and in their allocation registries ([ipv4reg], [ipv6reg], [asreg], and
[domainreg]), with the addition of new RDAP server information. [domainreg]), with the addition of new RDAP server information.
IANA updates RDAP Bootstrap Services Registries entries from the IANA updates RDAP Bootstrap Services Registries entries from the
allocation registries as those registries are updated. allocation registries as those registries are updated.
This document does not change any policies related to the allocation This document does not change any policies related to the allocation
registries; IANA has provided a mechanism for collecting the RDAP registries; IANA has provided a mechanism for collecting the RDAP
server information. The RDAP Bootstrap Services Registries will server information.
start empty and will be gradually populated as registrants of domains
and address spaces provide RDAP server information to IANA.
IANA has created a new top-level category on the Protocol Registries IANA has created a new top-level category on the Protocol Registries
page, <https://www.iana.org/protocols>. The group is called page, <https://www.iana.org/protocols>. The group is called
"Registration Data Access Protocol (RDAP)". Each of the RDAP "Registration Data Access Protocol (RDAP)". Each of the RDAP
Bootstrap Services Registries has been made available for general Bootstrap Services Registries has been made available for general
public on-demand download in the JSON format, and that registry's URI public on-demand download in the JSON format, and that registry's URI
is listed directly on the Protocol Registries page. is listed directly on the Protocol Registries page.
Other normal registries will be added to this group by other Other normal registries will be added to this group by other
documents, but the reason the URIs for these registries are clearly documents, but the reason the URIs for these registries are clearly
listed on the main page is to make those URIs obvious to implementers listed on the main page is to make those URIs obvious to implementers
-- these are registries that will be accessed by software, as well as -- these are registries that will be accessed by software, as well as
by humans using them for reference information. by humans using them for reference information.
Because these registries will be accessed by software, the download Because these registries will be accessed by software, the download
demand for the RDAP Bootstrap Services Registries may be unusually demand for the RDAP Bootstrap Services Registries may be unusually
high compared to normal IANA registries. The technical high compared to normal IANA registries. The technical
infrastructure by which registries are published has been put in infrastructure by which registries are published has been put in
place by IANA to support the load. Since the first publication of place by IANA to support the load. Since the publication of
this RFC, no issue have been reported regarding the load or the [RFC7484], no issue have been reported regarding the load or the
service. service.
As discussed in Section 8, software that accesses these registries As discussed in Section 8, software that accesses these registries
will depend on the HTTP Expires header field to limit their query will depend on the HTTP Expires header field to limit their query
rate. It is, therefore, important for that header field to be rate. It is, therefore, important for that header field to be
properly set to provide timely information as the registries change, properly set to provide timely information as the registries change,
while maintaining a reasonable load on the IANA servers. while maintaining a reasonable load on the IANA servers.
The HTTP Content-Type returned to clients accessing these JSON- The HTTP Content-Type returned to clients accessing these JSON-
formatted registries MUST be "application/json", as defined in formatted registries MUST be "application/json", as defined in
[RFC8259]. [RFC8259].
Because of how information in the RDAP Bootstrap Services Registries Because of how information in the RDAP Bootstrap Services Registries
is grouped and formatted, the registry entries may not be sortable. is grouped and formatted, the registry entries may not be sortable.
It is, therefore, not required or expected that the entries be sorted It is, therefore, not required or expected that the entries be
in any way. ordered in any way.
NOTE TO IANA: Please update the registries to reference this new RFC NOTE TO IANA: Please update the registries to reference this new RFC
instead of RFC 7484 once this document is approved by the IESG and instead of RFC 7484 once this document is approved by the IESG and
published by the RFC Editor". RFC-Editor, please remove this published by the RFC Editor". RFC-Editor, please remove this
paragraph before publication paragraph before publication
13.1. Bootstrap Service Registry for IPv4 Address Space 13.1. Bootstrap Service Registry for IPv4 Address Space
Entries in this registry contain at least the following: Entries in this registry contain at least the following:
* a CIDR [RFC4632] specification of the network block being * a CIDR [RFC4632] specification of the network block being
registered. registered.
* one or more URLs that provide the RDAP service regarding this * one or more URLs that provide the RDAP service regarding this
registration. registration.
13.2. Bootstrap Service Registry for IPv6 Address Space 13.2. Bootstrap Service Registry for IPv6 Address Space
Entries in this registry contain at least the following: Entries in this registry contain at least the following:
* an IPv6 prefix [RFC4291] specification of the network block being * an IPv6 prefix [RFC5952] specification of the network block being
registered. registered.
* one or more URLs that provide the RDAP service regarding this * one or more URLs that provide the RDAP service regarding this
registration. registration.
13.3. Bootstrap Service Registry for AS Number Space 13.3. Bootstrap Service Registry for AS Number Space
Entries in this registry contain at least the following: Entries in this registry contain at least the following:
* a range of Autonomous System numbers being registered. * a range of Autonomous System numbers being registered.
skipping to change at page 17, line 18 skipping to change at page 17, line 14
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<https://www.rfc-editor.org/info/rfc3339>. <https://www.rfc-editor.org/info/rfc3339>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <https://www.rfc-editor.org/info/rfc4291>.
[RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing [RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing
(CIDR): The Internet Address Assignment and Aggregation (CIDR): The Internet Address Assignment and Aggregation
Plan", BCP 122, RFC 4632, DOI 10.17487/RFC4632, August Plan", BCP 122, RFC 4632, DOI 10.17487/RFC4632, August
2006, <https://www.rfc-editor.org/info/rfc4632>. 2006, <https://www.rfc-editor.org/info/rfc4632>.
[RFC5396] Huston, G. and G. Michaelson, "Textual Representation of [RFC5396] Huston, G. and G. Michaelson, "Textual Representation of
Autonomous System (AS) Numbers", RFC 5396, Autonomous System (AS) Numbers", RFC 5396,
DOI 10.17487/RFC5396, December 2008, DOI 10.17487/RFC5396, December 2008,
<https://www.rfc-editor.org/info/rfc5396>. <https://www.rfc-editor.org/info/rfc5396>.
[RFC5890] Klensin, J., "Internationalized Domain Names for [RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework", Applications (IDNA): Definitions and Document Framework",
RFC 5890, DOI 10.17487/RFC5890, August 2010, RFC 5890, DOI 10.17487/RFC5890, August 2010,
<https://www.rfc-editor.org/info/rfc5890>. <https://www.rfc-editor.org/info/rfc5890>.
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
Address Text Representation", RFC 5952,
DOI 10.17487/RFC5952, August 2010,
<https://www.rfc-editor.org/info/rfc5952>.
[RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an [RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an
Attack", BCP 188, RFC 7258, DOI 10.17487/RFC7258, May Attack", BCP 188, RFC 7258, DOI 10.17487/RFC7258, May
2014, <https://www.rfc-editor.org/info/rfc7258>. 2014, <https://www.rfc-editor.org/info/rfc7258>.
[RFC7480] Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the
Registration Data Access Protocol (RDAP)", STD 95,
RFC 7480, DOI 10.17487/RFC7480, March 2015,
<https://www.rfc-editor.org/info/rfc7480>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", STD 90, RFC 8259, Interchange Format", STD 90, RFC 8259,
DOI 10.17487/RFC8259, December 2017, DOI 10.17487/RFC8259, December 2017,
<https://www.rfc-editor.org/info/rfc8259>. <https://www.rfc-editor.org/info/rfc8259>.
14.2. Informative References 14.2. Informative References
skipping to change at page 18, line 33 skipping to change at page 18, line 33
[RFC7071] Borenstein, N. and M. Kucherawy, "A Media Type for [RFC7071] Borenstein, N. and M. Kucherawy, "A Media Type for
Reputation Interchange", RFC 7071, DOI 10.17487/RFC7071, Reputation Interchange", RFC 7071, DOI 10.17487/RFC7071,
November 2013, <https://www.rfc-editor.org/info/rfc7071>. November 2013, <https://www.rfc-editor.org/info/rfc7071>.
[RFC7234] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, [RFC7234] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching", Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
RFC 7234, DOI 10.17487/RFC7234, June 2014, RFC 7234, DOI 10.17487/RFC7234, June 2014,
<https://www.rfc-editor.org/info/rfc7234>. <https://www.rfc-editor.org/info/rfc7234>.
[RFC7480] Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the
Registration Data Access Protocol (RDAP)", STD 95,
RFC 7480, DOI 10.17487/RFC7480, March 2015,
<https://www.rfc-editor.org/info/rfc7480>.
[RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the [RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the
Registration Data Access Protocol (RDAP)", STD 95, Registration Data Access Protocol (RDAP)", STD 95,
RFC 7481, DOI 10.17487/RFC7481, March 2015, RFC 7481, DOI 10.17487/RFC7481, March 2015,
<https://www.rfc-editor.org/info/rfc7481>. <https://www.rfc-editor.org/info/rfc7481>.
[RFC7484] Blanchet, M., "Finding the Authoritative Registration Data [RFC7484] Blanchet, M., "Finding the Authoritative Registration Data
(RDAP) Service", RFC 7484, DOI 10.17487/RFC7484, March (RDAP) Service", RFC 7484, DOI 10.17487/RFC7484, March
2015, <https://www.rfc-editor.org/info/rfc7484>. 2015, <https://www.rfc-editor.org/info/rfc7484>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
skipping to change at page 19, line 43 skipping to change at page 19, line 39
Hollenbeck, Arturo Servin, Andy Newton, Murray Kucherawy, Tom Hollenbeck, Arturo Servin, Andy Newton, Murray Kucherawy, Tom
Harrison, Naoki Kambe, Alexander Mayrhofer, Edward Lewis, Pete Harrison, Naoki Kambe, Alexander Mayrhofer, Edward Lewis, Pete
Resnick, Alessandro Vesely, Bert Greevenbosch, Barry Leiba, Jari Resnick, Alessandro Vesely, Bert Greevenbosch, Barry Leiba, Jari
Arkko, Kathleen Moriaty, Stephen Farrell, Richard Barnes, and Jean- Arkko, Kathleen Moriaty, Stephen Farrell, Richard Barnes, and Jean-
Francois Tremblay have provided input and suggestions to this Francois Tremblay have provided input and suggestions to this
document. Guillaume Leclanche was a coauthor of this document for document. Guillaume Leclanche was a coauthor of this document for
some revisions; his support is therein acknowledged and greatly some revisions; his support is therein acknowledged and greatly
appreciated. The section on formal definition was inspired by appreciated. The section on formal definition was inspired by
Section 6.2 of [RFC7071]. This new version got comments and Section 6.2 of [RFC7071]. This new version got comments and
suggestions from: Gavin Brown, Patrick Mevzek, John Levine, Jasdip suggestions from: Gavin Brown, Patrick Mevzek, John Levine, Jasdip
Singh, George Michaelson and Scott Hollenbeck. Singh, George Michaelson, Scott Hollenbeck, Russ Housley, Joel
Halpern, Lars Eggert, Benjamin Kaduk, Scott Kelly. Errata of RFC7484
were submitted by Pieter Vandepitte and were applied to this version.
Author's Address Changes since RFC7484
There are no substantive changes except for updates to the
implementation status and minor clarifications. This update is
primarily to meet the requirements for moving to Internet Standard.
Author's Address
Marc Blanchet Marc Blanchet
Viagenie Viagenie
246 Aberdeen 246 Aberdeen
Quebec QC G1R 2E1 Quebec QC G1R 2E1
Canada Canada
Email: Marc.Blanchet@viagenie.ca Email: Marc.Blanchet@viagenie.ca
URI: https://viagenie.ca URI: https://viagenie.ca
 End of changes. 31 change blocks. 
69 lines changed or deleted 79 lines changed or added

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