Internet Engineering Task Force (IETF) M. Blanchet
Request for Comments: 7484 Viagenie
Category: Standards Track March 2015
ISSN: 2070-1721
Internet Engineering Task Force (IETF) M. Blanchet
Request for Comments: 7484 Viagenie
Category: Standards Track March 2015
ISSN: 2070-1721
Finding the Authoritative Registration Data (RDAP) Service
查找权威注册数据（RDAP）服务
Abstract
摘要
This document specifies a method to find which Registration Data Access Protocol (RDAP) server is authoritative to answer queries for a requested scope, such as domain names, IP addresses, or Autonomous System numbers.
本文档指定了一种方法，用于查找哪个注册数据访问协议（RDAP）服务器有权回答请求范围的查询，如域名、IP地址或自治系统号。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7484.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7484.
Copyright Notice
版权公告
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2015 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of 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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Structure of the RDAP Bootstrap Service Registries . . . . . 3
4. Bootstrap Service Registry for Domain Name Space . . . . . . 5
5. Bootstrap Service Registries for Internet Numbers . . . . . . 6
5.1. Bootstrap Service Registry for IPv4 Address Space . . . . 7
5.2. Bootstrap Service Registry for IPv6 Address Space . . . . 8
5.3. Bootstrap Service Registry for AS Number Space . . . . . 9
6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 10
8. Deployment and Implementation Considerations . . . . . . . . 10
9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 11
10. Formal Definition . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Imported JSON Terms . . . . . . . . . . . . . . . . . . 11
10.2. Registry Syntax . . . . . . . . . . . . . . . . . . . . 12
11. Security Considerations . . . . . . . . . . . . . . . . . . . 13
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
12.1. Bootstrap Service Registry for IPv4 Address Space . . . 14
12.2. Bootstrap Service Registry for IPv6 Address Space . . . 14
12.3. Bootstrap Service Registry for AS Number Space . . . . . 14
12.4. Bootstrap Service Registry for Domain Name Space . . . . 15
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
13.1. Normative References . . . . . . . . . . . . . . . . . . 15
13.2. Informative References . . . . . . . . . . . . . . . . . 15
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Structure of the RDAP Bootstrap Service Registries . . . . . 3
4. Bootstrap Service Registry for Domain Name Space . . . . . . 5
5. Bootstrap Service Registries for Internet Numbers . . . . . . 6
5.1. Bootstrap Service Registry for IPv4 Address Space . . . . 7
5.2. Bootstrap Service Registry for IPv6 Address Space . . . . 8
5.3. Bootstrap Service Registry for AS Number Space . . . . . 9
6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 10
8. Deployment and Implementation Considerations . . . . . . . . 10
9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 11
10. Formal Definition . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Imported JSON Terms . . . . . . . . . . . . . . . . . . 11
10.2. Registry Syntax . . . . . . . . . . . . . . . . . . . . 12
11. Security Considerations . . . . . . . . . . . . . . . . . . . 13
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
12.1. Bootstrap Service Registry for IPv4 Address Space . . . 14
12.2. Bootstrap Service Registry for IPv6 Address Space . . . 14
12.3. Bootstrap Service Registry for AS Number Space . . . . . 14
12.4. Bootstrap Service Registry for Domain Name Space . . . . 15
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
13.1. Normative References . . . . . . . . . . . . . . . . . . 15
13.2. Informative References . . . . . . . . . . . . . . . . . 15
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17
Querying and retrieving registration data from registries are defined in Registration Data Access Protocol (RDAP) [RFC7480] [RFC7482] [RFC7483]. These documents do not specify where to send the queries. This document specifies a method to find which server is authoritative to answer queries for the requested scope.
在注册数据访问协议（RDAP）[RFC7480][RFC7482][RFC7483]中定义了从注册中心查询和检索注册数据。这些文档没有指定将查询发送到何处。本文档指定了一种方法，用于查找哪个服务器有权回答请求范围的查询。
Top-Level Domains (TLDs), Autonomous System (AS) numbers, and network blocks are delegated by IANA to Internet registries such as TLD registries and Regional Internet Registries (RIRs) that then issue further delegations and maintain information about them. Thus, the bootstrap information needed by RDAP clients is best generated from data and processes already maintained by IANA; the relevant registries already exist at [ipv4reg], [ipv6reg], [asreg], and [domainreg].
IANA将顶级域（TLD）、自治系统（AS）编号和网络块委托给互联网注册中心，如TLD注册中心和区域互联网注册中心（RIR），然后这些注册中心将进一步委托并维护有关这些注册中心的信息。因此，RDAP客户端所需的引导信息最好由IANA已经维护的数据和流程生成；相关注册表已存在于[ipv4reg]、[ipv6reg]、[asreg]和[domainreg]。
Per this document, IANA has created new registries based on a JSON format specified in this document, herein named RDAP Bootstrap Service Registries. These new registries are based on the existing entries of the above mentioned registries. An RDAP client fetches the RDAP Bootstrap Service Registries, extracts the data, and then performs a match with the query data to find the authoritative registration data server and appropriate query base URL.
根据本文档，IANA已经基于本文档中指定的JSON格式创建了新的注册表，本文称为RDAP引导服务注册表。这些新的登记册以上述登记册的现有条目为基础。RDAP客户端获取RDAP引导服务注册表，提取数据，然后与查询数据进行匹配，以查找权威注册数据服务器和适当的查询基URL。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
The RDAP Bootstrap Service Registries, as specified in Section 12 below, have been made available as JSON [RFC7159] 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.
如下文第12节所述，RDAP引导服务注册表已作为JSON[RFC7159]对象提供，可通过HTTP从IANA指定的位置检索。每个注册表的JSON对象包含一系列成员，其中包含有关注册表的元数据，例如版本标识符、注册表发布日期的时间戳和描述。此外，“服务”成员将注册表项本身作为数组包含。数组的每个项都包含一个第二级数组，其中包含两个元素，每个元素都是第三级数组。
Each element of the Services Array is a second-level array with two elements: in order, an Entry Array and a Service URL Array.
服务数组的每个元素都是一个二级数组，包含两个元素：按顺序排列，一个条目数组和一个服务URL数组。
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 sorted in any way.
条目数组包含具有相同基本RDAP URL集的所有条目。服务URL数组包含可用于条目数组中找到的条目的基本RDAP URL列表。这两个数组中的元素不会以任何方式排序。
An example structure of the JSON output of a RDAP Bootstrap Service Registry is illustrated:
RDAP引导服务注册表JSON输出的示例结构如下所示：
{
"version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ",
"description": "Some text",
"services": [
[
["entry1", "entry2", "entry3"],
[
"https://registry.example.com/myrdap/",
"http://registry.example.com/myrdap/"
]
],
[
["entry4"],
[
"http://example.org/"
]
]
]
}
{
"version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ",
"description": "Some text",
"services": [
[
["entry1", "entry2", "entry3"],
[
"https://registry.example.com/myrdap/",
"http://registry.example.com/myrdap/"
]
],
[
["entry4"],
[
"http://example.org/"
]
]
]
}
The formal syntax is described in Section 10.
第10节描述了形式语法。
The "version" corresponds to the format version of the registry. This specification defines version "1.0".
“版本”对应于注册表的格式版本。本规范定义了版本“1.0”。
The syntax of the "publication" value conforms to the Internet date/ time format [RFC3339]. The value is the latest update date of the registry by IANA.
“发布”值的语法符合互联网日期/时间格式[RFC3339]。该值是IANA对注册表的最新更新日期。
The optional "description" string can contain a comment regarding the content of the bootstrap object.
可选的“description”字符串可以包含有关引导对象内容的注释。
Per [RFC7258], 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.
根据[RFC7258]，在每个基本RDAP URL数组中，传输协议的安全版本应该是首选的，并首先尝试。例如，如果基本RDAP URL数组同时包含HTTPS和HTTP URL，则引导客户机应首先尝试HTTPS版本。
Base RDAP URLs MUST have a trailing "/" character because they are concatenated to the various segments defined in [RFC7482].
基本RDAP URL必须具有尾随“/”字符，因为它们连接到[RFC7482]中定义的各个段。
JSON names MUST follow the format recommendations of [RFC7480]. Any unrecognized JSON object properties or values MUST be ignored by implementations.
JSON名称必须遵循[RFC7480]的格式建议。实现必须忽略任何无法识别的JSON对象属性或值。
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 [RFC5890].
在本文档中定义的注册表中用作条目或基本RDAP URL的国际化域名标签只能使用[RFC5890]中定义的A标签形式表示。
All Domain Name labels used as entries or base RDAP URLs in the registries defined in this document MUST be only represented in lowercase.
本文档中定义的注册表中用作条目或基本RDAP URL的所有域名标签必须仅以小写字母表示。
The JSON output of this registry contains domain label entries attached to the root, grouped by base RDAP URLs, as shown in this example.
此注册表的JSON输出包含附加到根目录的域标签项，按基本RDAP URL分组，如本例所示。
{
"version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ",
"description": "Some text",
"services": [
[
["net", "com"],
[
"https://registry.example.com/myrdap/"
]
],
[
["org", "mytld"],
[
"http://example.org/"
]
],
[
["xn--zckzah"],
[
"https://example.net/rdapxn--zckzah/",
"http://example.net/rdapxn--zckzah/"
]
]
]
}
{
"version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ",
"description": "Some text",
"services": [
[
["net", "com"],
[
"https://registry.example.com/myrdap/"
]
],
[
["org", "mytld"],
[
"http://example.org/"
]
],
[
["xn--zckzah"],
[
"https://example.net/rdapxn--zckzah/",
"http://example.net/rdapxn--zckzah/"
]
]
]
}
The domain name's authoritative registration data service is found by doing the label-wise longest match of the target domain name with the domain values in the Entry Arrays in the IANA Bootstrap Service Registry for Domain Name Space. The match is done per label, from right to left. If the longest match results in multiple entries, then those entries are considered equivalent. The values contained
域名的权威注册数据服务是通过将目标域名与域名空间的IANA引导服务注册表项数组中的域值进行标签式最长匹配来找到的。按照标签从右到左进行匹配。如果最长匹配导致多个条目，则这些条目被视为等效条目。包含的值
in the Service URL Array of the matching second-level array are the valid base RDAP URLs as described in [RFC7482].
在匹配的二级数组的服务URL数组中，有[RFC7482]中描述的有效基本RDAP URL。
For example, a domain RDAP query for a.b.example.com matches the com entry in one of the arrays of the registry. The base RDAP URL for this query is then taken from the second element of the array, which is an array of base RDAP URLs valid for this entry. The client chooses one of the base URLs from this array; in this example, it chooses the only one available, "https://registry.example.com/ myrdap/". The segment specified in [RFC7482] is then appended to the base URL to complete the query. The complete query is then "https://registry.example.com/myrdap/domain/a.b.example.com".
例如，a.b.example.com的域RDAP查询与注册表的一个数组中的com项匹配。然后，此查询的基本RDAP URL取自数组的第二个元素，该元素是对该条目有效的基本RDAP URL数组。客户端从该数组中选择一个基本URL；在本例中，它选择了唯一可用的一个。”https://registry.example.com/ myrdap/”。然后将[RFC7482]中指定的段附加到基本URL以完成查询。完整的查询是“https://registry.example.com/myrdap/domain/a.b.example.com".
If a domain RDAP query for a.b.example.com matches both com and example.com entries in the registry, then the longest match applies and the example.com entry is used by the client.
如果a.b.example.com的域RDAP查询同时匹配注册表中的com和example.com条目，则应用最长的匹配，并且客户端使用example.com条目。
If the registry contains entries such as com and goodexample.com, then a domain RDAP query for example.com only matches the com entry because matching is done on a per-label basis.
如果注册表包含com和goodexample.com等条目，则example.com的域RDAP查询仅匹配com条目，因为匹配是基于每个标签进行的。
The entry for the root of the domain name space is specified as "".
域名空间的根目录项指定为“”。
This section discusses IPv4 and IPv6 address space and Autonomous System numbers.
本节讨论IPv4和IPv6地址空间以及自治系统编号。
For IP address space, the authoritative registration data service is found by doing a longest match of the target address with the values of the arrays in the corresponding RDAP Bootstrap Service Registry for Address Space. The longest match is done the same way as for routing: the addresses are converted in binary form and then the binary strings are compared to find the longest match up to the specified prefix length. The values contained in the second element of the array are the base RDAP URLs as described in [RFC7482]. The longest match method enables covering prefixes of a larger address space pointing to one base RDAP URL while more specific prefixes within the covering prefix are being served by another base RDAP URL.
对于IP地址空间，通过将目标地址与地址空间的相应RDAP引导服务注册表中的数组值进行最长匹配，可以找到权威注册数据服务。最长匹配的方式与路由相同：将地址转换为二进制形式，然后比较二进制字符串以找到最长的匹配，直到指定的前缀长度。数组的第二个元素中包含的值是[RFC7482]中描述的基本RDAP URL。最长匹配方法允许覆盖指向一个基本RDAP URL的较大地址空间的前缀，而覆盖前缀中的更多特定前缀由另一个基本RDAP URL提供服务。
The JSON output of this registry contains IPv4 prefix entries, specified in Classless Inter-domain Routing (CIDR) format [RFC4632] and grouped by RDAP URLs, as shown in this example.
此注册表的JSON输出包含IPv4前缀项，以无类域间路由（CIDR）格式[RFC4632]指定，并按RDAP URL分组，如本例所示。
{
"version": "1.0",
"publication": "2024-01-07T10:11:12Z",
"description": "RDAP Bootstrap file for example registries.",
"services": [
[
["1.0.0.0/8", "192.0.0.0/8"],
[
"https://rir1.example.com/myrdap/"
]
],
[
["28.2.0.0/16", "192.0.2.0/24"],
[
"http://example.org/"
]
],
[
["28.3.0.0/16"],
[
"https://example.net/rdaprir2/",
"http://example.net/rdaprir2/"
]
]
]
}
{
"version": "1.0",
"publication": "2024-01-07T10:11:12Z",
"description": "RDAP Bootstrap file for example registries.",
"services": [
[
["1.0.0.0/8", "192.0.0.0/8"],
[
"https://rir1.example.com/myrdap/"
]
],
[
["28.2.0.0/16", "192.0.2.0/24"],
[
"http://example.org/"
]
],
[
["28.3.0.0/16"],
[
"https://example.net/rdaprir2/",
"http://example.net/rdaprir2/"
]
]
]
}
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. The latter is chosen by the client given the longest match. The base RDAP URL for this query is then taken from the second element of the array, which is an array of base RDAP URLs valid for this entry. The client chooses one of the base URLs from this array; in this example, it chooses the only one available, "http://example.org/". The {resource} specified in [RFC7482] is then appended to the base URL to complete the query. The complete query is then "https://example.org/ ip/192.0.2.1/25".
例如，对“192.0.2.1/25”的查询匹配上述示例注册表中的“192.0.0.0/8”条目和“192.0.2.0/24”条目。后者由给定最长匹配的客户机选择。然后，此查询的基本RDAP URL取自数组的第二个元素，该元素是对该条目有效的基本RDAP URL数组。客户端从该数组中选择一个基本URL；在本例中，它选择了唯一可用的一个。”http://example.org/". 然后将[RFC7482]中指定的{resource}追加到基本URL以完成查询。完整的查询是“https://example.org/ ip/192.0.2.1/25”。
The JSON output of this registry contains IPv6 prefix entries, using [RFC4291] text representation of the address prefixes format, grouped by base RDAP URLs, as shown in this example.
此注册表的JSON输出包含IPv6前缀项，使用地址前缀格式的[RFC4291]文本表示，按基本RDAP URL分组，如本例所示。
{
"version": "1.0",
"publication": "2024-01-07T10:11:12Z",
"description": "RDAP Bootstrap file for example registries.",
"services": [
[
["2001:0200::/23", "2001:db8::/32"],
[
"https://rir2.example.com/myrdap/"
]
],
[
["2600::/16", "2100:ffff::/32"],
[
"http://example.org/"
]
],
[
["2001:0200:1000::/36"],
[
"https://example.net/rdaprir2/",
"http://example.net/rdaprir2/"
]
]
]
}
{
"version": "1.0",
"publication": "2024-01-07T10:11:12Z",
"description": "RDAP Bootstrap file for example registries.",
"services": [
[
["2001:0200::/23", "2001:db8::/32"],
[
"https://rir2.example.com/myrdap/"
]
],
[
["2600::/16", "2100:ffff::/32"],
[
"http://example.org/"
]
],
[
["2001:0200:1000::/36"],
[
"https://example.net/rdaprir2/",
"http://example.net/rdaprir2/"
]
]
]
}
For example, a query for "2001:0200:1000::/48" matches the "2001:0200::/23" entry and the "2001:0200:1000::/36" entry in the example registry above. The latter is chosen by the client given the longest match. The base RDAP URL for this query is then taken from the second element of the array, which is an array of base RDAP URLs valid for this entry. The client chooses one of the base URLs from this array; in this example, it chooses "https://example.net/ rdaprir2/" because it's the secure version of the protocol. The segment specified in [RFC7482] is then appended to the base URL to complete the query. The complete query is, therefore, "https://example.net/rdaprir2/ip/2001:0200:1000::/48". If the target RDAP server does not answer, the client can then use another URL prefix from the array.
例如，对“2001:0200:1000:：/48”的查询与上面示例注册表中的“2001:0200:：/23”条目和“2001:0200:1000:：/36”条目相匹配。后者由给定最长匹配的客户机选择。然后，此查询的基本RDAP URL取自数组的第二个元素，该元素是对该条目有效的基本RDAP URL数组。客户端从该数组中选择一个基本URL；在本例中，它选择“https://example.net/ rdaprir2/“因为它是协议的安全版本。然后将[RFC7482]中指定的段附加到基本URL以完成查询。因此，完整的查询是，”https://example.net/rdaprir2/ip/2001:0200:1000::/48". 如果目标RDAP服务器没有应答，则客户端可以使用阵列中的另一个URL前缀。
The JSON output of this contains Autonomous Systems number 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 served by the base RDAP URLs found in the second element. The array always contains two AS numbers represented in decimal format that 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 AS numbers.
它的JSON输出包含自治系统编号范围条目，按基本RDAP URL分组，如本例所示。Entry数组是一个数组，包含第二个元素中的基本RDAP URL提供的AS编号范围列表。数组始终包含两个以十进制格式表示的AS数，十进制格式表示数组两个元素之间AS数的范围。单个AS编号表示为两个相同AS编号的范围。
{
"version": "1.0",
"publication": "2024-01-07T10:11:12Z",
"description": "RDAP Bootstrap file for example registries.",
"services": [
[
["2045-2045"],
[
"https://rir3.example.com/myrdap/"
]
],
[
["10000-12000", "300000-400000"],
[
"http://example.org/"
]
],
[
["64512-65534"],
[
"http://example.net/rdaprir2/",
"https://example.net/rdaprir2/"
]
]
]
}
{
"version": "1.0",
"publication": "2024-01-07T10:11:12Z",
"description": "RDAP Bootstrap file for example registries.",
"services": [
[
["2045-2045"],
[
"https://rir3.example.com/myrdap/"
]
],
[
["10000-12000", "300000-400000"],
[
"http://example.org/"
]
],
[
["64512-65534"],
[
"http://example.net/rdaprir2/",
"https://example.net/rdaprir2/"
]
]
]
}
For example, a query for AS 65411 matches the 64512-65534 entry in the example registry above. The base RDAP URL for this query is then taken from the second element of the array, which is an array of base RDAP URLs valid for this entry. The client chooses one of the base URLs from this array; in this example, it chooses "https://example.net/rdaprir2/". The segment specified in [RFC7482] is then appended to the base URL to complete the query. The complete query is, therefore, "https://example.net/rdaprir2/autnum/65411". If the server does not answer, the client can then use another URL prefix from the array.
例如，AS 65411的查询与上面示例注册表中的64512-65534项匹配。然后，此查询的基本RDAP URL取自数组的第二个元素，该元素是对该条目有效的基本RDAP URL数组。客户端从该数组中选择一个基本URL；在本例中，它选择“https://example.net/rdaprir2/". 然后将[RFC7482]中指定的段附加到基本URL以完成查询。因此，完整的查询是，”https://example.net/rdaprir2/autnum/65411". 如果服务器没有应答，则客户端可以使用阵列中的另一个URL前缀。
Entities (such as contacts, registrants, or registrars) can be queried by handle as described in [RFC7482]. Since there is no global namespace for entities, this document does not describe how to find the authoritative RDAP server for entities. However, it is possible that, if the entity identifier was received from a previous query, the same RDAP server could be queried for that entity, or the entity identifier itself is a fully referenced URL that can be queried.
实体（如联系人、注册人或注册人）可以通过[RFC7482]中所述的句柄进行查询。由于实体没有全局名称空间，因此本文档不描述如何查找实体的权威RDAP服务器。但是，如果从以前的查询中接收到实体标识符，则可能会为该实体查询相同的RDAP服务器，或者实体标识符本身是可以查询的完全引用URL。
The registries may not contain the requested value. In these cases, there is no known RDAP server for that requested value, and the client SHOULD provide an appropriate error message to the user.
注册表可能不包含请求的值。在这些情况下，对于请求的值，没有已知的RDAP服务器，客户端应该向用户提供适当的错误消息。
This method relies on the fact that RDAP clients are fetching the IANA registries to then find the servers locally. Clients SHOULD NOT fetch the registry on every RDAP request. Clients SHOULD cache the registry, but use underlying protocol signaling, such as the HTTP Expires header field [RFC7234], to identify when it is time to refresh the cached registry.
这种方法依赖于这样一个事实，即RDAP客户端获取IANA注册表，然后在本地查找服务器。客户端不应在每次RDAP请求时获取注册表。客户端应该缓存注册表，但使用底层协议信令，如HTTP Expires头字段[RFC7234]，来确定何时刷新缓存的注册表。
If the query data does not match any entry in the client cached registry, then the client may implement various methods, such as the following:
如果查询数据与客户端缓存注册表中的任何条目不匹配，则客户端可以实现各种方法，例如：
o In the case of a domain object, the client may first query the DNS to see if the respective entry has been delegated or if it is mistyped information by the user. The DNS query could be to fetch the NS records for the TLD domain. If the DNS answer is negative, then there is no need to fetch the new version of the registry. However, if the DNS answer is positive, this may mean that the currently cached registry is no longer current. The client could then fetch the registry, parse, and then do the normal matching as specified above. This method may not work for all types of RDAP objects.
o 在域对象的情况下，客户机可以首先查询DNS，以查看相应的条目是否已被委派，或者用户是否键入了错误的信息。DNS查询可以用于获取TLD域的NS记录。如果DNS回答为否定，则无需获取注册表的新版本。但是，如果DNS回答为肯定，这可能意味着当前缓存的注册表不再是当前注册表。然后，客户端可以获取注册表、解析，然后按照上面指定的方式进行正常匹配。此方法可能不适用于所有类型的RDAP对象。
o If the client knows the existence of an RDAP aggregator or redirector and its associated base URL, and trusts that service, then it could send the query to the redirector, which would redirect the client if it knows the authoritative server that client has not found.
o 如果客户端知道存在RDAP聚合器或重定向器及其关联的基本URL，并信任该服务，则可以将查询发送到重定向器，如果客户端知道客户端未找到的权威服务器，重定向器将重定向客户端。
Some authorities of registration data may work together on sharing their information for a common service, including mutual redirection [REDIRECT-RDAP].
一些注册数据管理机构可能会合作共享其公共服务的信息，包括相互重定向[REDIRECT-RDAP]。
When a new object is allocated, such as a new AS range, a new TLD, or a new IP address range, there is no guarantee that this new object will have an entry in the corresponding bootstrap RDAP registry, since the setup of the RDAP server for this new entry may become live and registered later. Therefore, the clients should expect that even if an object, such as TLD, IP address range, or AS range is allocated, the existence of the entry in the corresponding bootstrap registry is not guaranteed.
分配新对象时，例如新的as范围、新的TLD或新的IP地址范围，无法保证此新对象在相应的引导RDAP注册表中有一个条目，因为此新条目的RDAP服务器设置可能会在以后激活并注册。因此，客户机应该期望，即使分配了对象（如TLD、IP地址范围或as范围），也不能保证相应引导注册表中存在该项。
This method does not provide a direct way to find authoritative RDAP servers for any other objects than the ones described in this document. In particular, the following objects are not bootstrapped with the method described in this document:
除了本文档中描述的对象之外，此方法不提供为任何其他对象查找权威RDAP服务器的直接方法。特别是，以下对象不是使用本文档中描述的方法引导的：
o entities
o 实体
o queries using search patterns that do not contain a terminating string that matches some entries in the registries
o 使用不包含与注册表中某些项匹配的终止字符串的搜索模式的查询
o nameservers
o 名称服务器
o help
o 帮助
This section is the formal definition of the registries. The structure of JSON objects and arrays using a set of primitive elements is defined in [RFC7159]. Those elements are used to describe the JSON structure of the registries.
本节是注册处的正式定义。使用一组基本元素的JSON对象和数组的结构在[RFC7159]中定义。这些元素用于描述注册表的JSON结构。
o OBJECT: a JSON object, defined in Section 4 of [RFC7159]
o OBJECT:JSON对象，在[RFC7159]第4节中定义
o MEMBER: a member of a JSON object, defined in Section 4 of [RFC7159]
o 成员：JSON对象的成员，在[RFC7159]的第4节中定义
o MEMBER-NAME: the name of a MEMBER, defined as a "string" in Section 4 of [RFC7159]
o 成员名称：成员的名称，在[RFC7159]第4节中定义为“字符串”
o MEMBER-VALUE: the value of a MEMBER, defined as a "value" in Section 4 of [RFC7159]
o 成员价值：成员的价值，在[RFC7159]第4节中定义为“价值”
o ARRAY: an array, defined in Section 5 of [RFC7159]
o 数组：在[RFC7159]第5节中定义的数组
o ARRAY-VALUE: an element of an ARRAY, defined in Section 5 of [RFC7159]
o ARRAY-VALUE：数组的一个元素，在[RFC7159]的第5节中定义
o STRING: a "string", as defined in Section 7 of [RFC7159]
o 字符串：如[RFC7159]第7节所定义的“字符串”
Using the above terms for the JSON structures, the syntax of a registry is defined as follows:
使用上述JSON结构术语，注册表的语法定义如下：
o rdap-bootstrap-registry: an OBJECT containing a MEMBER version and a MEMBER publication, an optional MEMBER description, and a MEMBER services-list
o rdap引导注册表：包含成员版本和成员发布、可选成员描述和成员服务列表的对象
o version: a MEMBER with MEMBER-NAME "version" and MEMBER-VALUE a STRING
o 版本：成员名为“版本”且成员值为字符串的成员
o publication: a MEMBER with MEMBER-NAME "publication" and MEMBER-VALUE a STRING
o 发布：成员名为“publication”且成员值为字符串的成员
o description: a MEMBER with MEMBER-NAME "description" and MEMBER-VALUE a STRING
o description：成员名为“description”且成员值为字符串的成员
o services-list: a MEMBER with MEMBER-NAME "services" and MEMBER-VALUE a services-array
o 服务列表：成员名为“服务”且成员值为服务数组的成员
o services-array: an ARRAY, where each ARRAY-VALUE is a service
o 服务数组：一个数组，其中每个数组值都是一个服务
o service: an ARRAY of 2 elements, where the first ARRAY-VALUE is a an entry-list and the second ARRAY-VALUE is a service-uri-list
o 服务：由2个元素组成的数组，其中第一个数组值是条目列表，第二个数组值是服务uri列表
o entry-list: an ARRAY, where each ARRAY-VALUE is an entry
o 条目列表：一个数组，其中每个数组值都是一个条目
o entry: a STRING
o 条目：字符串
o service-uri-list: an ARRAY, where each ARRAY-VALUE is a service-uri
o 服务uri列表：一个数组，其中每个数组值都是一个服务uri
o service-uri: a STRING
o 服务uri：一个字符串
By providing a bootstrap method to find RDAP servers, this document helps to ensure that the end users will get the RDAP data from an authoritative source, instead of from rogue sources. The method has the same security properties as the RDAP protocols themselves. The transport used to access the registries can be more secure by using TLS [RFC5246], which IANA supports.
通过提供查找RDAP服务器的引导方法，本文档有助于确保最终用户将从权威来源而不是流氓来源获取RDAP数据。该方法与RDAP协议本身具有相同的安全属性。通过使用IANA支持的TLS[RFC5246]，用于访问注册表的传输可以更加安全。
Additional considerations on using RDAP are described in [RFC7481].
[RFC7481]中描述了使用RDAP的其他注意事项。
IANA has created the RDAP Bootstrap Services Registries, listed below, and made them available as JSON objects. The contents of these registries are described in Section 3, Section 4, and Section 5, with the formal syntax specified in Section 10.
IANA创建了RDAP引导服务注册中心，如下所示，并将其作为JSON对象提供。第3节、第4节和第5节描述了这些注册中心的内容，第10节规定了正式语法。
The process for adding or updating entries in these registries differs from the normal IANA registry processes: these registries are generated from the data, processes, and policies maintained by IANA in their allocation registries ([ipv4reg], [ipv6reg], [asreg], and [domainreg]), with the addition of new RDAP server information.
在这些注册表中添加或更新条目的过程不同于正常的IANA注册表过程：这些注册表是由IANA在其分配注册表（[ipv4reg]、[ipv6reg]、[asreg]和[domainreg]）中维护的数据、过程和策略生成的，并添加了新的RDAP服务器信息。
IANA will create and update RDAP Bootstrap Services Registries entries from the allocation registries as those registries are updated.
IANA将从分配注册表中创建和更新RDAP引导服务注册表项，这些注册表项将随着这些注册表项的更新而更新。
This document does not change any policies related to the allocation registries; IANA has provided a mechanism for collecting the RDAP server information. The RDAP Bootstrap Services Registries will start empty and will be gradually populated as registrants of domains and address spaces provide RDAP server information to IANA.
本文件不改变与分配登记册相关的任何政策；IANA提供了一种收集RDAP服务器信息的机制。RDAP引导服务注册中心将开始为空，并随着域和地址空间的注册人向IANA提供RDAP服务器信息而逐渐填充。
IANA has created a new top-level category on the Protocol Registries page, <http://www.iana.org/protocols>. The group is called "Registration Data Access Protocol (RDAP)". Each of the RDAP Bootstrap Services Registries has been made available for general public on-demand download in the JSON format, and that registry's URI is listed directly on the Protocol Registries page.
IANA在协议注册页面上创建了一个新的顶级类别<http://www.iana.org/protocols>. 该组称为“注册数据访问协议（RDAP）”。每个RDAP引导服务注册中心都以JSON格式提供给公众按需下载，该注册中心的URI直接列在协议注册中心页面上。
Other normal registries will be added to this group by other documents, but the reason the URIs for these registries are clearly 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 by humans using them for reference information.
其他普通注册中心将通过其他文档添加到此组中，但主页上清楚列出这些注册中心的URI的原因是为了使这些URI对实现者显而易见——这些注册中心将由软件访问，也可以由使用它们作为参考信息的人访问。
Because these registries will be accessed by software, the download demand for the RDAP Bootstrap Services Registries may be unusually high compared to normal IANA registries. The technical infrastructure by which registries are published will need to be reviewed and might need to be augmented.
由于这些注册表将通过软件访问，因此与普通IANA注册表相比，RDAP引导服务注册表的下载需求可能异常高。需要审查并可能需要加强登记册出版所依据的技术基础设施。
As discussed in Section 8, software that accesses these registries will depend on the HTTP Expires header field to limit their query rate. It is, therefore, important for that header field to be properly set to provide timely information as the registries change, while maintaining a reasonable load on the IANA servers. The HTTP Content-Type returned to clients accessing these JSON- formatted registries MUST be "application/json", as defined in [RFC7159].
如第8节所述，访问这些注册表的软件将依赖HTTP Expires头字段来限制其查询速率。因此，必须正确设置该标头字段，以便在注册表更改时及时提供信息，同时在IANA服务器上保持合理的负载。返回给访问这些JSON格式注册表的客户端的HTTP内容类型必须是[RFC7159]中定义的“application/JSON”。
Because of how information in the RDAP Bootstrap Services Registries is grouped and formatted, the registry entries may not be sortable. It is, therefore, not required or expected that the entries be sorted in any way.
由于RDAP引导服务注册表中的信息是如何分组和格式化的，注册表项可能无法排序。因此，不要求或不期望以任何方式对条目进行排序。
Entries in this registry contain at least the following:
此注册表中的条目至少包含以下内容：
o a CIDR [RFC4632] specification of the network block being registered.
o 正在注册的网络块的CIDR[RFC4632]规范。
o one or more URLs that provide the RDAP service regarding this registration.
o 提供有关此注册的RDAP服务的一个或多个URL。
Entries in this registry contain at least the following:
此注册表中的条目至少包含以下内容：
o an IPv6 prefix [RFC4291] specification of the network block being registered.
o 正在注册的网络块的IPv6前缀[RFC4291]规范。
o one or more URLs that provide the RDAP service regarding this registration.
o 提供有关此注册的RDAP服务的一个或多个URL。
Entries in this registry contain at least the following:
此注册表中的条目至少包含以下内容：
o a range of Autonomous System numbers being registered.
o 正在注册的一系列自主系统编号。
o one or more URLs that provide the RDAP service regarding this registration.
o 提供有关此注册的RDAP服务的一个或多个URL。
Entries in this registry contain at least the following:
此注册表中的条目至少包含以下内容：
o a domain name attached to the root being registered.
o 附加到正在注册的根目录的域名。
o one or more URLs that provide the RDAP service regarding this registration.
o 提供有关此注册的RDAP服务的一个或多个URL。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, July 2002, <http://www.rfc-editor.org/info/rfc3339>.
[RFC3339]Klyne，G.和C.Newman，“互联网上的日期和时间：时间戳”，RFC33392002年7月<http://www.rfc-editor.org/info/rfc3339>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006, <http://www.rfc-editor.org/info/rfc4291>.
[RFC4291]Hinden，R.和S.Deering，“IP版本6寻址体系结构”，RFC 42912006年2月<http://www.rfc-editor.org/info/rfc4291>.
[RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan", BCP 122, RFC 4632, August 2006, <http://www.rfc-editor.org/info/rfc4632>.
[RFC4632]Fuller，V.和T.Li，“无类域间路由（CIDR）：互联网地址分配和聚合计划”，BCP 122，RFC 4632，2006年8月<http://www.rfc-editor.org/info/rfc4632>.
[RFC5890] Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, August 2010, <http://www.rfc-editor.org/info/rfc5890>.
[RFC5890]Klensin，J.“应用程序的国际化域名（IDNA）：定义和文档框架”，RFC 58902010年8月<http://www.rfc-editor.org/info/rfc5890>.
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", RFC 7159, March 2014, <http://www.rfc-editor.org/info/rfc7159>.
[RFC7159]Bray，T.，Ed.“JavaScript对象表示法（JSON）数据交换格式”，RFC 7159，2014年3月<http://www.rfc-editor.org/info/rfc7159>.
[REDIRECT-RDAP] Martinez, C., Zhou, L., and G. Rada, "Redirection Service for Registration Data Access Protocol", Work in Progress, draft-ietf-weirds-redirects-04, July 2014.
[REDIRECT-RDAP]Martinez，C.，Zhou，L.，和G.Rada，“注册数据访问协议的重定向服务”，正在进行的工作，草稿-ietf-weirds-redirects-042014年7月。
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, August 2008, <http://www.rfc-editor.org/info/rfc5246>.
[RFC5246]Dierks，T.和E.Rescorla，“传输层安全（TLS）协议版本1.2”，RFC 5246，2008年8月<http://www.rfc-editor.org/info/rfc5246>.
[RFC7071] Borenstein, N. and M. Kucherawy, "A Media Type for Reputation Interchange", RFC 7071, November 2013, <http://www.rfc-editor.org/info/rfc7071>.
[RFC7071]Borenstein，N.和M.Kucherawy，“声誉交换的媒体类型”，RFC 70712013年11月<http://www.rfc-editor.org/info/rfc7071>.
[RFC7234] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching", RFC 7234, June 2014, <http://www.rfc-editor.org/info/rfc7234>.
[RFC7234]Fielding，R.，Ed.，Nottingham，M.，Ed.，和J.Reschke，Ed.，“超文本传输协议（HTTP/1.1）：缓存”，RFC 7234，2014年6月<http://www.rfc-editor.org/info/rfc7234>.
[RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an Attack", BCP 188, RFC 7258, May 2014, <http://www.rfc-editor.org/info/rfc7258>.
[RFC7258]Farrell，S.和H.Tschofenig，“普遍监控是一种攻击”，BCP 188，RFC 7258，2014年5月<http://www.rfc-editor.org/info/rfc7258>.
[RFC7480] Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the Registration Data Access Protocol (RDAP)", RFC 7480, March 2015, <http://www.rfc-editor.org/info/rfc7480>.
[RFC7480]Newton，A.，Ellacott，B.，和N.Kong，“注册数据访问协议（RDAP）中的HTTP使用”，RFC 7480，2015年3月<http://www.rfc-editor.org/info/rfc7480>.
[RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the Registration Data Access Protocol", RFC 7481, March 2015, <http://www.rfc-editor.org/info/rfc7481>.
[RFC7481]Hollenbeck，S.和N.Kong，“注册数据访问协议的安全服务”，RFC 74812015年3月<http://www.rfc-editor.org/info/rfc7481>.
[RFC7482] Newton, A. and S. Hollenbeck, "Registration Data Access Protocol Query Format", RFC 7482, March 2015, <http://www.rfc-editor.org/info/rfc7482>.
[RFC7482]Newton，A.和S.Hollenbeck，“注册数据访问协议查询格式”，RFC 7482，2015年3月<http://www.rfc-editor.org/info/rfc7482>.
[RFC7483] Newton, A. and S. Hollenbeck, "JSON Responses for the Registration Data Access Protocol (RDAP)", RFC 7483, March 2015, <http://www.rfc-editor.org/info/rfc7483>.
[RFC7483]Newton，A.和S.Hollenbeck，“注册数据访问协议（RDAP）的JSON响应”，RFC 7483，2015年3月<http://www.rfc-editor.org/info/rfc7483>.
[asreg] IANA, "Autonomous System (AS) Numbers", <http://www.iana.org/assignments/as-numbers>.
[asreg]IANA，“自主系统（AS）编号”<http://www.iana.org/assignments/as-numbers>.
[domainreg] IANA, "Root Zone Database", <http://www.iana.org/domains/root/db>.
[domainreg]IANA，“根区域数据库”<http://www.iana.org/domains/root/db>.
[ipv4reg] IANA, "IPv4 Address Space Registry", <http://www.iana.org/assignments/ipv4-address-space>.
[ipv4reg]IANA，“IPv4地址空间注册表”<http://www.iana.org/assignments/ipv4-address-space>.
[ipv6reg] IANA, "IPv6 Global Unicast Address Assignments", <http://www.iana.org/assignments/ ipv6-unicast-address-assignments>.
[ipv6reg]IANA，“IPv6全局单播地址分配”<http://www.iana.org/assignments/ ipv6单播地址分配>。
Acknowledgements
致谢
The WEIRDS working group had multiple discussions on this topic, including a session during IETF 84, where various methods such as in-DNS and others were debated. The idea of using IANA registries was discovered by the author during discussions with his colleagues as well as by a comment from Andy Newton. All the people involved in these discussions are herein acknowledged. Linlin Zhou, Jean-Philippe Dionne, John Levine, Kim Davies, Ernie Dainow, Scott Hollenbeck, Arturo Servin, Andy Newton, Murray Kucherawy, Tom Harrison, Naoki Kambe, Alexander Mayrhofer, Edward Lewis, Pete Resnick, Alessandro Vesely, Bert Greevenbosch, Barry Leiba, Jari Arkko, Kathleen Moriaty, Stephen Farrell, Richard Barnes, and Jean-Francois Tremblay have provided input and suggestions to this document. Guillaume Leclanche was a coauthor of this document for some revisions; his support is therein acknowledged and greatly appreciated. The section on formal definition was inspired by Section 6.2 of [RFC7071].
WEIRDS工作组就此主题进行了多次讨论，包括IETF 84期间的一次会议，会上讨论了各种方法，如DNS和其他方法。作者在与同事讨论时以及安迪·牛顿的评论中发现了使用IANA注册中心的想法。所有参与这些讨论的人在此表示感谢。周林林、让·菲利普·迪翁、约翰·莱文、金·戴维斯、厄尼·戴诺、斯科特·霍伦贝克、阿图罗·塞文、安迪·牛顿、默里·库奇拉维、汤姆·哈里森、内奥基·坎贝、亚历山大·梅尔霍夫、爱德华·刘易斯、皮特·雷斯尼克、亚历山德罗·维斯利、伯特·格里文博什、巴里·莱巴、贾里·阿克科、凯瑟琳·莫里亚蒂、斯蒂芬·法雷尔、理查德·巴恩斯、，Jean-Francois Tremblay为本文件提供了意见和建议。Guillaume Leclanche是该文件的合著者，负责一些修订；他的支持在此得到承认和高度赞赏。关于形式定义的部分受[RFC7071]第6.2节的启发。
Author's Address
作者地址
Marc Blanchet Viagenie 246 Aberdeen Quebec, QC G1R 2E1 Canada
Marc Blanchet Viagenie 246魁北克省阿伯丁市，QC G1R 2E1加拿大
EMail: Marc.Blanchet@viagenie.ca
URI: http://viagenie.ca
EMail: Marc.Blanchet@viagenie.ca
URI: http://viagenie.ca