<?xml version="1.0" encoding="US-ASCII"?> encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<rfc category="std" xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-regext-rfc7484bis-06" obsoletes="7484">

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<?rfc rfcedstyle="yes" ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?> number="9224" obsoletes="7484" updates="" submissionType="IETF" category="std" consensus="true" xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3">

<front>
    <title abbrev="Finding Authoritative RDAP Service">Finding the Authoritative Registration Data Access Protocol (RDAP) Service</title>
    <seriesInfo name="RFC" value="9224"/>
    <seriesInfo name="STD" value="95"/>
    <author initials="M." surname="Blanchet" fullname="Marc Blanchet">
      <organization>Viagenie</organization>
      <address>
        <postal>
          <street>246 Aberdeen</street>
          <city>Quebec</city>
          <region>QC</region>
          <code>G1R 2E1</code>
          <country>Canada</country>
        </postal>
        <email>Marc.Blanchet@viagenie.ca</email>
        <uri>https://viagenie.ca</uri>
      </address>
    </author>

<date/>
    <date year="2022" month="March" />
    <area>art</area>
    <workgroup>regext</workgroup>
    <keyword>whois</keyword>
    <keyword>bootstrap</keyword>
    <keyword>domain</keyword>
    <keyword>IDN</keyword>
    <keyword>DNS</keyword>
    <keyword>AS</keyword>
    <keyword>IPv4</keyword>
    <keyword>IPv6</keyword>
    <keyword>JSON</keyword>
    <abstract>
      <t>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. This document obsoletes RFC7484.</t> RFC 7484.</t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>Querying and retrieving registration data from registries are defined
      in the Registration Data Access Protocol (RDAP) <xref target="RFC7480"/> target="RFC7480"
      format="default"/> <xref target="RFC7481"/> target="RFC7481" format="default"/> <xref target="RFC9082"/>
      target="RFC9082" format="default"/> <xref target="RFC9083"/>. target="RFC9083"
      format="default"/>. 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.</t>
      <t>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 <xref target="ipv4reg"/>, target="ipv4reg" format="default"/>, <xref target="ipv6reg"/>,
      target="ipv6reg" format="default"/>, <xref target="asreg"/>, target="asreg"
      format="default"/>, and <xref target="domainreg"/>. target="domainreg"
      format="default"/>. This document obsoletes <xref target="RFC7484"/>. target="RFC7484"
      format="default"/>.
</t>
      <t>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.
</t>
    </section>
    <section title="Conventions numbered="true" toc="default">
      <name>Conventions Used in This Document"> Document</name>

        <t>
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
    NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
    "MAY", "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
    "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
    NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
    "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and "OPTIONAL" "<bcp14>OPTIONAL</bcp14>" in this document are
    to be interpreted as described in BCP 14 BCP&nbsp;14 <xref target="RFC2119"/>
    <xref target="RFC8174"/> when, and only when, they appear in all capitals,
    as shown here.
        </t>

    </section>
    <section anchor="struct" title="Structure numbered="true" toc="default">
      <name>Structure of the RDAP Bootstrap Service Registries"> Registries</name>
      <t>The RDAP Bootstrap Service Registries, as specified in <xref
target="ianaconsiderations"/> target="ianaconsiderations" format="default"/> below, have been made available as JSON <xref
target="RFC8259"/> target="RFC8259" format="default"/> 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.
      </t>

      <t>Each element of the Services Array is a second-level array with two elements: in order, an Entry Array and a Service URL Array.</t>
      <t>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.</t>
      <t>An example structure of the JSON output of a an RDAP Bootstrap Service Registry is illustrated:
<figure>
<artwork>
</t>
      <sourcecode type="json"><![CDATA[
{
    "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"],
        [
          "https://example.org/"
        ]
      ]
    ]
}
</artwork>
</figure>
</t>
]]></sourcecode>
      <t>The formal syntax is described in <xref target="abnf"/>.</t> target="abnf" format="default"/>.</t>
      <t>The "version" corresponds to the format version of the registry. This specification defines version "1.0".</t>
      <t>The syntax of the "publication" value conforms to the Internet date/time format <xref target="RFC3339"/>. target="RFC3339" format="default"/>. The value is the latest update date of the registry by IANA.</t>
      <t>The optional "description" string can contain a comment regarding the content of the bootstrap object. </t>
      <t>Per <xref target="RFC7258"/>, target="RFC7258" format="default"/>, in each array of base RDAP URLs, the secure versions of the transport protocol SHOULD <bcp14>SHOULD</bcp14> be preferred and tried first. For example, if the base RDAP URLs array contains both HTTPS and HTTP URLs, the bootstrap client SHOULD <bcp14>SHOULD</bcp14> try the HTTPS version first.</t>
      <t>Base RDAP URLs MUST <bcp14>MUST</bcp14> have a trailing "/" character
      because they are concatenated to the various segments defined in <xref target="RFC9082"/>.</t>
      target="RFC9082" format="default"/>.</t>
      <t>JSON names MUST <bcp14>MUST</bcp14> follow the format recommendations of section 6 of
      <xref target="RFC7480"/>. target="RFC7480" sectionFormat="of" section="6"
      format="default"/>. Any unrecognized JSON object properties or values MUST
      <bcp14>MUST</bcp14> be ignored by implementations.</t>
      <t>Internationalized Domain Name labels used as entries or base RDAP URLs in the registries defined in this document MUST <bcp14>MUST</bcp14> be only represented using their A-label form as defined in <xref target="RFC5890"/>.</t> target="RFC5890" format="default"/>.</t>
      <t>All Domain Name labels used as entries or base RDAP URLs in the registries defined in this document MUST <bcp14>MUST</bcp14> be only represented in lowercase.</t>
    </section>
    <section anchor="domainrdapreg"
title="Bootstrap numbered="true" toc="default">
      <name>Bootstrap Service Registry for Domain Name Space"> Space</name>
      <t>The JSON output of this registry contains domain label entries attached to the root, grouped by base RDAP URLs, as shown in this example.
<figure>
<artwork>
</t>
      <sourcecode type="json"><![CDATA[
{
    "version": "1.0",
    "publication": "2024-01-07T10:11:12Z",
    "description": "Some text",
    "services": [
      [
        ["net", "com"],
        [
          "https://registry.example.com/myrdap/"
        ]
      ],
      [
        ["org", "mytld"],
        [
          "https://example.org/"
        ]
      ],
      [
        ["xn--zckzah"],
        [
          "https://example.net/rdap/xn--zckzah/",
          "http://example.net/rdap/xn--zckzah/"
        ]
      ]
    ]
}
</artwork>
</figure>
</t>
]]></sourcecode>
      <t>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 "Bootstrap Service Registry for
    Domain Name Space. 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 in the Service URL Array of the matching second-level array are the valid base RDAP URLs as described in <xref target="RFC9082"/>.</t> target="RFC9082" format="default"/>.</t>
      <t>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 <xref target="RFC9082"/> target="RFC9082" format="default"/> 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". </t>
      <t>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.</t>
      <t>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.</t>
      <t>The entry for the root of the domain name space is specified as "".</t>
    </section>

    <section anchor="iprdapreg"
title="Bootstrap numbered="true" toc="default">
      <name>Bootstrap Service Registries for Internet Numbers"> Numbers</name>
      <t>This section discusses IPv4 and IPv6 address space and Autonomous System numbers.</t>
      <t>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 in packet forwarding: 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 <xref target="RFC9082"/>. target="RFC9082" format="default"/>. 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.</t>
      <section title="Bootstrap numbered="true" toc="default">
        <name>Bootstrap Service Registry for IPv4 Address Space"> Space</name>
        <t>The JSON output of this registry contains IPv4 prefix entries, specified in Classless Inter-domain Routing (CIDR) format <xref target="RFC4632"/> target="RFC4632" format="default"/> and grouped by RDAP URLs, as shown in this example.
<figure>
<artwork>
</t>
        <sourcecode type="json"><![CDATA[
{
    "version": "1.0",
    "publication": "2024-01-07T10:11:12Z",
    "description": "RDAP Bootstrap file for example registries.",
    "services": [
      [
        ["198.51.100.0/24", "192.0.0.0/8"],
        [
          "https://rir1.example.com/myrdap/"
        ]
      ],
      [
        ["203.0.113.0/24", "192.0.2.0/24"],
        [
          "https://example.org/"
        ]
      ],
      [
        ["203.0.113.0/28"],
        [
          "https://example.net/rdaprir2/",
          "http://example.net/rdaprir2/"
        ]
      ]
    ]
}
</artwork>
</figure>
</t>
]]></sourcecode>
        <t>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 because it is 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, "https://example.org/". The {resource} specified in <xref target="RFC9082"/> target="RFC9082" format="default"/> 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".</t>
      </section>
      <section title="Bootstrap numbered="true" toc="default">
        <name>Bootstrap Service Registry for IPv6 Address Space"> Space</name>
        <t>The JSON output of this registry contains IPv6 prefix entries,
        using <xref target="RFC5952"/> target="RFC5952" format="default"/> text representation of
        the address prefixes format, grouped by base RDAP URLs, as shown in
        this example.
<figure>
<artwork>
</t>
        <sourcecode type="json"><![CDATA[
{
    "version": "1.0",
    "publication": "2024-01-07T10:11:12Z",
    "description": "RDAP Bootstrap file for example registries.",
    "services": [
      [
        ["2001:db8::/34"],
        [
          "https://rir2.example.com/myrdap/"
        ]
      ],
      [
        ["2001:db8:4000::/36", "2001:db8:ffff::/48"],
        [
          "https://example.org/"
        ]
      ],
      [
        ["2001:db8:1000::/36"],
        [
          "https://example.net/rdaprir2/",
          "http://example.net/rdaprir2/"
        ]
      ]
    ]
}
</artwork>
</figure>
</t>
]]></sourcecode>
        <t>For example, a query for "2001:db8:1000::/48" matches the
        "2001:db8::/34" entry and the "2001:db8:1000::/36" entry in the
        example registry above. The latter is chosen by the client because it
        is 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 <xref target="RFC9082"/> target="RFC9082"
        format="default"/> is then appended to the base URL to complete the
        query. The complete query is, therefore, is therefore
        "https://example.net/rdaprir2/ip/2001:db8:1000::/48". If the target
        RDAP server does not answer, the client can then use another URL
        prefix from the array.</t>
      </section>
      <section title="Bootstrap numbered="true" toc="default">
        <name>Bootstrap Service Registry for AS Number Space"> Space</name>

	<t>The JSON output of this registry contains Autonomous Systems entries for AS number ranges entries,
	ranges, 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. Each element of the
	array contains two AS numbers represented in decimal format, separated
	by a hyphen, that represents the range of AS numbers between the two
	AS numbers (inclusive), where values are in increasing order (e.g. (e.g.,
	100-200, not 200-100). A single AS number is represented as a range of
	two identical AS numbers. AS numbers are represented as 'asplain' as
	defined in <xref target="RFC5396"/>. target="RFC5396" format="default"/>. Ranges MUST NOT
	<bcp14>MUST NOT</bcp14> overlap.
<figure>
<artwork>
</t>
        <sourcecode type="json"><![CDATA[
{
    "version": "1.0",
    "publication": "2024-01-07T10:11:12Z",
    "description": "RDAP Bootstrap file for example registries.",
    "services": [
      [
        ["64496-64496"],
        [
          "https://rir3.example.com/myrdap/"
        ]
      ],
      [
        ["64497-64510", "65536-65551"],
        [
          "https://example.org/"
        ]
      ],
      [
        ["64512-65534"],
        [
          "http://example.net/rdaprir2/",
          "https://example.net/rdaprir2/"
        ]
      ]
    ]
}
</artwork>
</figure>
</t>
]]></sourcecode>
        <t>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 <xref target="RFC9082"/> target="RFC9082" format="default"/> 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.</t>
      </section>
    </section>
    <section title="Entity"> numbered="true" toc="default">
      <name>Entity</name>

      <t>Entities (such as contacts, registrants, or registrars) can be queried by handle as described in <xref target="RFC9082"/>. target="RFC9082" format="default"/>. Since there is no global namespace name space 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 qualified URL that can be queried. The mechanism described in <xref target="RFC8521"/> MAY target="RFC8521" format="default"/> <bcp14>MAY</bcp14> also be used.</t>
    </section>
    <section title="Non-existent numbered="true" toc="default">
      <name>Non-existent Entries or RDAP URL Values"> Values</name>
      <t>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 <bcp14>SHOULD</bcp14> provide an appropriate error message to the user.</t>
    </section>

    <section anchor="deploy" title="Deployment numbered="true" toc="default">
      <name>Deployment and Implementation Considerations"> Considerations</name>
      <t>This method relies on the fact that RDAP clients are fetching the
      IANA registries to then find the servers locally. Clients SHOULD NOT <bcp14>SHOULD
      NOT</bcp14> fetch the registry on every RDAP request. Clients SHOULD
      <bcp14>SHOULD</bcp14> cache the registry, but use underlying protocol
      signaling, such as the HTTP Expires header field <xref target="RFC7234"/>, target="RFC7234"
      format="default"/>, to identify when it is time to refresh the cached
      registry.</t>
      <t>Some authorities of registration data may work together on sharing their information for a common service, including mutual redirection <xref target="REDIRECT-RDAP"/>.</t> target="I-D.ietf-weirds-redirects" format="default"/>.</t>
      <t>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.</t>
    </section>
    <section title="Limitations"> numbered="true" toc="default">
      <name>Limitations</name>
      <t>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:
      <list style="symbols">
        <t>entities</t>
        <t>queries
      </t>
      <ul spacing="normal">
        <li>entities</li>
        <li>queries using search patterns that do not contain a terminating string that matches some entries in the registries</t>
        <t>nameservers</t>
        <t>help</t>
      </list>
    </t> registries</li>
        <li>nameservers</li>
        <li>help</li>
      </ul>
    </section>
    <section anchor="abnf" title="Formal Definition"> numbered="true" toc="default">
      <name>Formal Definition</name>
      <t>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 <xref target="RFC8259"/>. target="RFC8259" format="default"/>. Those elements are used to describe the JSON structure of the registries.</t>
      <section title="Imported numbered="true" toc="default">
        <name>Imported JSON Terms">

<t>
<list style="symbols">
  <t>OBJECT: a Terms</name>

	<dl>

	  <dt>OBJECT:
	  </dt>
	  <dd>a JSON object, defined in Section 4 of <xref target="RFC8259"/></t>
  <t>MEMBER: a target="RFC8259"
          sectionFormat="of" section="4" format="default"/>
	  </dd>

	  <dt>MEMBER:
	  </dt>
	  <dd>a member of a JSON object, defined in Section 4 of <xref target="RFC8259"/></t>
  <t>MEMBER-NAME: the
          target="RFC8259" format="default" sectionFormat="of" section="4"
          />
	  </dd>

	  <dt>MEMBER-NAME:
	  </dt>
	  <dd>the name of a MEMBER, defined as a "string" in
      Section 4 of
      <xref target="RFC8259"/></t>
  <t>MEMBER-VALUE: the target="RFC8259" sectionFormat="of" section="4" format="default"/>
	  </dd>

	  <dt>MEMBER-VALUE:
	  </dt>
	  <dd>the value of a MEMBER, defined as a "value" in
      Section 4 of
          <xref target="RFC8259"/></t>
  <t>ARRAY:  an target="RFC8259" sectionFormat="of" section="4" format="default"/>
	  </dd>

	  <dt>ARRAY:
	  </dt>
	  <dd>an array, defined in Section 5 of <xref target="RFC8259"/></t>
  <t>ARRAY-VALUE: an target="RFC8259"
          format="default" sectionFormat="of" section="5"/>
	  </dd>

	  <dt>ARRAY-VALUE:
	  </dt>
	  <dd>an element of an ARRAY, defined in Section 5 of <xref target="RFC8259"/></t>
  <t>STRING: a
          target="RFC8259" sectionFormat="of" section="5"
          format="default"/>
	  </dd>

	  <dt>STRING:
	  </dt>
	  <dd>a "string", as defined in Section 7 of <xref target="RFC8259"/></t>
 </list>
</t> target="RFC8259"
          format="default" sectionFormat="of" section="7"/>
	  </dd>
</dl>

</section>
      <section title="Registry Syntax"> numbered="true" toc="default">
        <name>Registry Syntax</name>
        <t>Using the above terms for the JSON structures, the syntax of a
   registry is defined as follows:
<list style="symbols">
 <t>rdap-bootstrap-registry: an
</t>

<dl>
  <dt>rdap-bootstrap-registry:
  </dt>
  <dd>an OBJECT containing a MEMBER version and a MEMBER publication, an optional MEMBER description, and a MEMBER services-list</t>
 <t>version: a services-list
  </dd>

  <dt>version:
  </dt>
  <dd>a MEMBER with MEMBER-NAME "version" and MEMBER-VALUE a STRING</t>
 <t>publication: a STRING
  </dd>

    <dt>publication:
  </dt>
  <dd>a MEMBER with MEMBER-NAME "publication" and MEMBER-VALUE a STRING</t>
 <t>description: a STRING
  </dd>

    <dt>description:
  </dt>
  <dd>a MEMBER with MEMBER-NAME "description" and MEMBER-VALUE a STRING</t>
 <t>services-list: a STRING
  </dd>

    <dt>services-list:
  </dt>
  <dd>a MEMBER with MEMBER-NAME "services" and MEMBER-VALUE a services-array</t>
 <t>services-array: an services-array
  </dd>

    <dt>services-array:
  </dt>
  <dd>an ARRAY, where each ARRAY-VALUE is a service</t>
 <t>service: an service
  </dd>

    <dt>service:
  </dt>
  <dd>an ARRAY of 2 elements, where the first ARRAY-VALUE is an entry-list and the second ARRAY-VALUE is a service-uri-list</t>
 <t>entry-list: an service-uri-list
  </dd>

    <dt>entry-list:
  </dt>
  <dd>an ARRAY, where each ARRAY-VALUE is an entry</t>
 <t>entry: a STRING</t>
 <t>service-uri-list: an entry
  </dd>

    <dt>entry:
  </dt>
  <dd>a STRING
  </dd>

    <dt>service-uri-list:
  </dt>
  <dd>an ARRAY, where each ARRAY-VALUE is a service-uri</t>
 <t>service-uri: a STRING</t>
   </list>
  </t> service-uri
  </dd>

    <dt>service-uri:
  </dt>
  <dd>a STRING
  </dd>
</dl>

</section>
    </section>
    <section title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>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, 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 uses TLS <xref target="RFC8446"/>. target="RFC8446" format="default"/>.
      </t>
      <t>Additional considerations on using RDAP are described in <xref target="RFC7481"/>.</t>
  </section>
<section title="Implementation Status">
<t> NOTE: Please remove this section and the reference to RFC 7942 prior to publication as an RFC.</t>

<t>This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in <xref target="RFC7942"/>. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs.  Please note that the listing of any individual implementation here does not imply endorsement by the IETF.  Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors.  This is not intended as, and must not be construed to be, a catalog of available implementations or their features.  Readers are advised to note that other implementations may exist.</t>

<t>According to <xref target="RFC7942"/>, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature.  It is up to the individual working groups to use this information as they see fit". </t>
<section title="RDAP Browser Mobile Application">
 <t>
  <list>
    <t>Responsible Organization: Viagenie</t>
    <t>Author: Marc Blanchet</t>
    <t>Location: https://viagenie.ca/rdapbrowser/</t>
    <t>Description: RDAP Browser is an RDAP client for domain names, IP addresses and AS numbers fetching the IANA registries described in this document to find the right authoritative RDAP server. End user can query any domain name, IP address or AS number and the registration data will be shown on the screen.</t>
    <t>Level of Maturity: Production (i.e. in the Android and iOS App stores since August 2019)</t>
    <t>Contact Information: rdapbrowser@viagenie.ca</t>
    <t>Information last updated: March 2021</t>
  </list>
 </t>
</section>
<section title="ICANN Lookup Web Application">
 <t>
  <list>
    <t>Responsible Organization: ICANN </t>
    <t>Location: https://lookup.icann.org</t>
    <t>Description: ICANN's Domain Name Registration Data Lookup is an RDAP client for domain names fetching the IANA regis tries described in this document to find the right authoritative RDAP server. End user can query any domain name and the registration data will be shown on the screen.</t>
    <t>Level of Maturity: Production</t>
    <t>Information last updated: March 2021</t>
  </list>
 </t>
</section>
      <section title="ARIN Implementation">
        <t>
          <list>
            <t>Responsible Organization: ARIN</t>
            <t>Base URL: https://rdap-bootstrap.arin.net/bootstrap ( Sample query: https://rdap-bootstrap.arin.net/bootstrap/autnum/1 )</t>
            <t>Description: ARIN RDAP Bootstrap server aids clients by reading the bootstrapping information published by IANA and using it to send HTTP redirects to RDAP queries. RDAP clients https://search.arin.net/ and NicInfo ( https://github.com/arineng/nicinfo ) use this bootstrap service. The underlying server software is open-sourced at https://github.com/arineng/rdap_bootstrap_server .</t>
            <t>Level of Maturity: Production</t>
            <t>Contact Information: info@arin.net</t>
            <t>Information Last Updated: Nov 2020</t>
          </list>
        </t>
      </section> target="RFC7481" format="default"/>.</t>
    </section>

    <section anchor="ianaconsiderations" title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>

      <t>IANA has created the RDAP Bootstrap Services Registries, Registries listed below, below
 and made them available as JSON objects.  The contents of these registries are described in Sections <xref target="struct"/>, target="struct" format="counter"/>, <xref target="domainrdapreg"/>, target="domainrdapreg" format="counter"/>, and <xref target="iprdapreg"/>, target="iprdapreg" format="counter"/>, with the formal syntax specified in <xref target="abnf"/>. target="abnf" format="default"/>. The registries MUST <bcp14>MUST</bcp14> be accessible only through HTTPS (TLS <xref target="RFC8446"/>) target="RFC8446" format="default"/>) transport.</t>
      <t>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 (<xref target="ipv4reg"/>, target="ipv4reg" format="default"/>, <xref target="ipv6reg"/>, target="ipv6reg" format="default"/>, <xref target="asreg"/>, target="asreg" format="default"/>, and <xref target="domainreg"/>), target="domainreg" format="default"/>), with the addition of new RDAP server information.</t>
      <t>IANA updates RDAP Bootstrap Services Registries entries from the
      allocation registries as those registries are updated.</t>
      <t>This document does not change any policies related to the allocation
registries; IANA has provided a mechanism for collecting the RDAP server information.</t>

<t>IANA has created a new top-level category on the Protocol Registries page,
&lt;https://www.iana.org/protocols&gt;. page:
     <eref target="https://www.iana.org/protocols" brackets="angle"/>. 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, format by the general public, and that registry's URI
is listed directly on the Protocol Registries page.
</t>
      <t>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.</t>
      <t>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 has been put in place by IANA to support the load. Since the publication of  <xref target="RFC7484"/>, target="RFC7484" format="default"/>, no issue issues have been reported regarding the load or the service. </t>
      <t>As discussed in <xref target="deploy"/>, target="deploy" format="default"/>, 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.</t>
      <t>The HTTP Content-Type returned to clients accessing these JSON-formatted registries MUST <bcp14>MUST</bcp14> be "application/json", as defined in <xref target="RFC8259"/>.</t> target="RFC8259" format="default"/>.</t>
      <t>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 ordered in any way.</t>

<t>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 published by the RFC Editor". RFC-Editor, please remove this paragraph before publication</t>

      <section title="Bootstrap numbered="true" toc="default">
        <name>Bootstrap Service Registry for IPv4 Address Space"> Space</name>
        <t>Entries in this registry contain at least the following:
 <list style="symbols">
  <t>a
        </t>
        <ul spacing="normal">
          <li>a CIDR <xref target="RFC4632"/> target="RFC4632" format="default"/> specification of the network block being registered.</t>
  <t>one registered</li>
          <li>one or more URLs that provide the RDAP service regarding this registration. </t>
 </list>
</t> registration</li>
        </ul>
      </section>
      <section title="Bootstrap numbered="true" toc="default">
        <name>Bootstrap Service Registry for IPv6 Address Space"> Space</name>
        <t>Entries in this registry contain at least the following:
 <list style="symbols">
  <t>an
        </t>
        <ul spacing="normal">
          <li>an IPv6 prefix <xref target="RFC5952"/> target="RFC5952" format="default"/> specification of the network block being registered.</t>
  <t>one registered</li>
          <li>one or more URLs that provide the RDAP service regarding this registration.
 </t>
 </list>
</t> registration
 </li>
        </ul>
      </section>
      <section title="Bootstrap numbered="true" toc="default">
        <name>Bootstrap Service Registry for AS Number Space"> Space</name>
        <t>Entries in this registry contain at least the following:
 <list style="symbols">
  <t>a
        </t>
        <ul spacing="normal">
          <li>a range of Autonomous System numbers being registered.</t>
  <t>one registered</li>
          <li>one or more URLs that provide the RDAP service regarding this registration.
 </t>
 </list>
</t>
          registration
 </li>
        </ul>
      </section>
      <section title="Bootstrap numbered="true" toc="default">
        <name>Bootstrap Service Registry for Domain Name Space"> Space</name>
        <t>Entries in this registry contain at least the following:
 <list style="symbols">
  <t>a
        </t>
        <ul spacing="normal">
          <li>a domain name attached to the root being registered.</t>
  <t>one registered</li>
          <li>one or more URLs that provide the RDAP service regarding this registration.
 </t>
 </list>
</t> registration
 </li>
        </ul>
      </section>
    </section>

  </middle>

  <back>
  <references title="Normative References">
    <?rfc include="reference.RFC.2119"?>
    <?rfc include="reference.RFC.3339"?>
    <?rfc include="reference.RFC.4632"?>
    <?rfc include="reference.RFC.5396"?>
    <?rfc include="reference.RFC.5890"?>
    <?rfc include="reference.RFC.5952"?>
    <?rfc include="reference.RFC.7258"?>
    <?rfc include="reference.RFC.7480"?>
    <?rfc include="reference.RFC.8174"?>
    <?rfc include="reference.RFC.8259"?>

<displayreference target="I-D.ietf-weirds-redirects" to="REDIRECT-RDAP"/>

    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4632.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5396.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5890.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5952.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7258.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7480.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/>
      </references>

  <references title="Informative References">

    <?rfc include="reference.RFC.7071"?>
    <?rfc include="reference.RFC.7234"?>
    <?rfc include="reference.RFC.7481"?>
    <?rfc include="reference.RFC.7484"?>
    <?rfc include="reference.RFC.7942"?>
    <?rfc include="reference.RFC.8446"?>
    <?rfc include="reference.RFC.8521"?>
    <?rfc include="reference.RFC.9082"?>
    <?rfc include="reference.RFC.9083"?>

<!--I-D.ietf-weirds-redirects, Expired - not in queue-->
      <references>
        <name>Informative References</name>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7071.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7234.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7481.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7484.xml"/>

        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8521.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9082.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9083.xml"/>

<reference anchor='REDIRECT-RDAP'> anchor="I-D.ietf-weirds-redirects">
<front>
<title>Redirection Service for Registration Data Access Protocol</title>
<author initials='C' initials='C.M.' surname='Martinez' fullname='Carlos Martinez'>
    <organization />
</author> M. Martinez' role='editor'/>

<author initials='L' initials='L.' surname='Zhou' fullname='Linlin Zhou'>
    <organization Zhou' role='editor' />
</author>

<author initials='G' initials='G.' surname='Rada' fullname='Gerardo Rada'>
    <organization Rada' />
</author>
<date month='July' year='2014' /> year='2014'/>
</front>
<seriesInfo name='Work in Progress,' value='draft-ietf-weirds-redirects-04' /> name="Internet-Draft" value="draft-ietf-weirds-redirects-04"/>

</reference>

        <reference anchor="ipv4reg" target="https://www.iana.org/assignments/ipv4-address-space">
      <front><title>IPv4
          <front>
            <title>IANA IPv4 Address Space Registry</title>
            <author>
    <organization>IANA</organization></author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>

        <reference anchor="ipv6reg" target="https://www.iana.org/assignments/ipv6-unicast-address-assignments">
      <front><title>IPv6
          <front>
            <title>IPv6 Global Unicast Address Assignments</title>
            <author>
    <organization>IANA</organization></author>
    <date/></front>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>

        <reference anchor="asreg" target="https://www.iana.org/assignments/as-numbers">
      <front><title>Autonomous
          <front>
            <title>Autonomous System (AS) Numbers</title>
            <author>
    <organization>IANA</organization></author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>

        <reference anchor="domainreg" target="https://www.iana.org/domains/root/db">
      <front><title>Root
          <front>
            <title>Root Zone Database</title>
            <author>
    <organization>IANA</organization></author>
      <date/></front>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
      </references>
    </references>

    <section numbered="true" toc="default">
      <name>Changes since RFC 7484</name>
      <t>There are no substantive changes except for minor clarifications.
      This update is primarily to meet the requirements for moving to an Internet
      Standard.</t>
    </section>

    <section title="Acknowledgements" numbered="no"> numbered="false" toc="default">
      <name>Acknowledgements</name>

<t>The WEIRDS working group Working Group had multiple discussions on this topic, including
a session during IETF 84, where various methods such as
     in&nbhy;DNS 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. <contact
fullname="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 <contact fullname="Linlin Zhou"/>, <contact
fullname="Jean-Philippe Dionne"/>, <contact fullname="John Levine"/>, <contact
fullname="Kim Davies"/>, <contact fullname="Ernie Dainow"/>, <contact
fullname="Scott Hollenbeck"/>, <contact fullname="Arturo Servin"/>, <contact
fullname="Andy Newton"/>, <contact fullname="Murray Kucherawy"/>, <contact
fullname="Tom Harrison"/>, <contact fullname="Naoki Kambe"/>, <contact
fullname="Alexander Mayrhofer"/>, <contact fullname="Edward Lewis"/>, <contact
fullname="Pete Resnick"/>, <contact fullname="Alessandro Vesely"/>, <contact
fullname="Bert Greevenbosch"/>, <contact fullname="Barry Leiba"/>, <contact
fullname="Jari Arkko"/>, <contact fullname="Kathleen Moriaty"/>, <contact
fullname="Stephen Farrell"/>, <contact fullname="Richard Barnes"/>, and
<contact fullname="Jean-Francois Tremblay"/> provided input and suggestions to
the first version of this document. Guillaume Leclanche document.</t>
<t>
<contact fullname="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 <xref target="RFC7071"/>. target="RFC7071" sectionFormat="of" section="6.2"
format="default"/>.  This new version got [This document] received comments and
suggestions from: Gavin Brown, Patrick Mevzek, John Levine, Jasdip Singh, George Michaelson, Scott Hollenbeck, Russ Housley, Joel Halpern, Lars Eggert, Benjamin Kaduk, Scott Kelly, Eric Vyncke, John Scudder, Erik Kline, Robert Wilton. from <contact fullname="Gavin Brown"/>, <contact fullname="Patrick
Mevzek"/>, <contact fullname="John Levine"/>, <contact fullname="Jasdip
Singh"/>, <contact fullname="George Michaelson"/>, <contact fullname="Scott
Hollenbeck"/>, <contact fullname="Russ Housley"/>, <contact fullname="Joel
Halpern"/>, <contact fullname="Lars Eggert"/>, <contact fullname="Benjamin
Kaduk"/>, <contact fullname="Scott Kelly"/>, <contact fullname="Éric
Vyncke"/>, <contact fullname="John Scudder"/>, <contact fullname="Erik
Kline"/>, and <contact fullname="Robert Wilton"/>. Errata of RFC7484 for RFC 7484 were
submitted by Pieter Vandepitte <contact fullname="Pieter Vandepitte"/> and were applied to this version.</t>
  </section>
<section title="Changes since RFC7484" numbered="no">
    <t>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.</t>
document.
</t>

</section>

  </back>
</rfc>