<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" consensus="true" docName="draft-ietf-regext-rfc7484bis-06" indexInclude="true" ipr="trust200902" number="9224" obsoletes="7484" prepTime="2022-03-31T15:31:24" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocInclude="true" xml:lang="en">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-regext-rfc7484bis-06" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9224" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="Finding Authoritative RDAP Service">Finding the Authoritative Registration Data Access Protocol (RDAP) Service</title>
    <seriesInfo name="RFC" value="9224" stream="IETF"/>
    <seriesInfo name="STD" value="95" stream="IETF"/>
    <author initials="M." surname="Blanchet" fullname="Marc Blanchet">
      <organization showOnFrontPage="true">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 month="03" year="2022"/>
    <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 pn="section-abstract">
      <t indent="0" pn="section-abstract-1">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 RFC 7484.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            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 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9224" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2022 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) 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 Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conventions-used-in-this-do">Conventions Used in This Document</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-structure-of-the-rdap-boots">Structure of the RDAP Bootstrap Service Registries</xref></t>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-bootstrap-service-registry-">Bootstrap Service Registry for Domain Name Space</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-bootstrap-service-registrie">Bootstrap Service Registries for Internet Numbers</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2">
              <li pn="section-toc.1-1.5.2.1">
                <t indent="0" pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-bootstrap-service-registry-f">Bootstrap Service Registry for IPv4 Address Space</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.2">
                <t indent="0" pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-bootstrap-service-registry-fo">Bootstrap Service Registry for IPv6 Address Space</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.3">
                <t indent="0" pn="section-toc.1-1.5.2.3.1"><xref derivedContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-bootstrap-service-registry-for">Bootstrap Service Registry for AS Number Space</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-entity">Entity</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-non-existent-entries-or-rda">Non-existent Entries or RDAP URL Values</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-deployment-and-implementati">Deployment and Implementation Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="9" format="counter" sectionFormat="of" target="section-9"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-limitations">Limitations</xref></t>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="10" format="counter" sectionFormat="of" target="section-10"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-formal-definition">Formal Definition</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.10.2">
              <li pn="section-toc.1-1.10.2.1">
                <t indent="0" pn="section-toc.1-1.10.2.1.1"><xref derivedContent="10.1" format="counter" sectionFormat="of" target="section-10.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-imported-json-terms">Imported JSON Terms</xref></t>
              </li>
              <li pn="section-toc.1-1.10.2.2">
                <t indent="0" pn="section-toc.1-1.10.2.2.1"><xref derivedContent="10.2" format="counter" sectionFormat="of" target="section-10.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-registry-syntax">Registry Syntax</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.11">
            <t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="11" format="counter" sectionFormat="of" target="section-11"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.12">
            <t indent="0" pn="section-toc.1-1.12.1"><xref derivedContent="12" format="counter" sectionFormat="of" target="section-12"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.12.2">
              <li pn="section-toc.1-1.12.2.1">
                <t indent="0" pn="section-toc.1-1.12.2.1.1"><xref derivedContent="12.1" format="counter" sectionFormat="of" target="section-12.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-bootstrap-service-registry-for-">Bootstrap Service Registry for IPv4 Address Space</xref></t>
              </li>
              <li pn="section-toc.1-1.12.2.2">
                <t indent="0" pn="section-toc.1-1.12.2.2.1"><xref derivedContent="12.2" format="counter" sectionFormat="of" target="section-12.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-bootstrap-service-registry-for-i">Bootstrap Service Registry for IPv6 Address Space</xref></t>
              </li>
              <li pn="section-toc.1-1.12.2.3">
                <t indent="0" pn="section-toc.1-1.12.2.3.1"><xref derivedContent="12.3" format="counter" sectionFormat="of" target="section-12.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-bootstrap-service-registry-for-a">Bootstrap Service Registry for AS Number Space</xref></t>
              </li>
              <li pn="section-toc.1-1.12.2.4">
                <t indent="0" pn="section-toc.1-1.12.2.4.1"><xref derivedContent="12.4" format="counter" sectionFormat="of" target="section-12.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-bootstrap-service-registry-for-d">Bootstrap Service Registry for Domain Name Space</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.13">
            <t indent="0" pn="section-toc.1-1.13.1"><xref derivedContent="13" format="counter" sectionFormat="of" target="section-13"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.13.2">
              <li pn="section-toc.1-1.13.2.1">
                <t indent="0" pn="section-toc.1-1.13.2.1.1"><xref derivedContent="13.1" format="counter" sectionFormat="of" target="section-13.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.13.2.2">
                <t indent="0" pn="section-toc.1-1.13.2.2.1"><xref derivedContent="13.2" format="counter" sectionFormat="of" target="section-13.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.14">
            <t indent="0" pn="section-toc.1-1.14.1"><xref derivedContent="Appendix A" format="default" sectionFormat="of" target="section-appendix.a"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-changes-since-rfc-7484">Changes since RFC 7484</xref></t>
          </li>
          <li pn="section-toc.1-1.15">
            <t indent="0" pn="section-toc.1-1.15.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.16">
            <t indent="0" pn="section-toc.1-1.16.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-address">Author's Address</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">Querying and retrieving registration data from registries are defined
      in the Registration Data Access Protocol (RDAP) <xref target="RFC7480" format="default" sectionFormat="of" derivedContent="RFC7480"/> <xref target="RFC7481" format="default" sectionFormat="of" derivedContent="RFC7481"/> <xref target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/> <xref target="RFC9083" format="default" sectionFormat="of" derivedContent="RFC9083"/>. 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 indent="0" pn="section-1-2">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" format="default" sectionFormat="of" derivedContent="ipv4reg"/>, <xref target="ipv6reg" format="default" sectionFormat="of" derivedContent="ipv6reg"/>, <xref target="asreg" format="default" sectionFormat="of" derivedContent="asreg"/>, and <xref target="domainreg" format="default" sectionFormat="of" derivedContent="domainreg"/>. This document obsoletes <xref target="RFC7484" format="default" sectionFormat="of" derivedContent="RFC7484"/>.
</t>
      <t indent="0" pn="section-1-3">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 numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-conventions-used-in-this-do">Conventions Used in This Document</name>
      <t indent="0" pn="section-2-1">
    The key words "<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 "<bcp14>OPTIONAL</bcp14>" in this document are
    to be interpreted as described in BCP 14 <xref target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/>
        <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> when, and only when, they appear in all capitals,
    as shown here.
      </t>
    </section>
    <section anchor="struct" numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-structure-of-the-rdap-boots">Structure of the RDAP Bootstrap Service Registries</name>
      <t indent="0" pn="section-3-1">The RDAP Bootstrap Service Registries, as specified in <xref target="ianaconsiderations" format="default" sectionFormat="of" derivedContent="Section 12"/> below, have been made available as JSON <xref target="RFC8259" format="default" sectionFormat="of" derivedContent="RFC8259"/> 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 indent="0" pn="section-3-2">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 indent="0" pn="section-3-3">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 indent="0" pn="section-3-4">An example structure of the JSON output of an RDAP Bootstrap Service Registry is illustrated:
</t>
      <sourcecode type="json" markers="false" pn="section-3-5">
{
    "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/"
        ]
      ]
    ]
}
</sourcecode>
      <t indent="0" pn="section-3-6">The formal syntax is described in <xref target="abnf" format="default" sectionFormat="of" derivedContent="Section 10"/>.</t>
      <t indent="0" pn="section-3-7">The "version" corresponds to the format version of the registry. This specification defines version "1.0".</t>
      <t indent="0" pn="section-3-8">The syntax of the "publication" value conforms to the Internet date/time format <xref target="RFC3339" format="default" sectionFormat="of" derivedContent="RFC3339"/>. The value is the latest update date of the registry by IANA.</t>
      <t indent="0" pn="section-3-9">The optional "description" string can contain a comment regarding the content of the bootstrap object. </t>
      <t indent="0" pn="section-3-10">Per <xref target="RFC7258" format="default" sectionFormat="of" derivedContent="RFC7258"/>, in each array of base RDAP URLs, the secure versions of the transport protocol <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 <bcp14>SHOULD</bcp14> try the HTTPS version first.</t>
      <t indent="0" pn="section-3-11">Base RDAP URLs <bcp14>MUST</bcp14> have a trailing "/" character
      because they are concatenated to the various segments defined in <xref target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/>.</t>
      <t indent="0" pn="section-3-12">JSON names <bcp14>MUST</bcp14> follow the format recommendations of
      <xref target="RFC7480" sectionFormat="of" section="6" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7480#section-6" derivedContent="RFC7480"/>. Any unrecognized JSON object properties or values
      <bcp14>MUST</bcp14> be ignored by implementations.</t>
      <t indent="0" pn="section-3-13">Internationalized Domain Name labels used as entries or base RDAP URLs in the registries defined in this document <bcp14>MUST</bcp14> be only represented using their A-label form as defined in <xref target="RFC5890" format="default" sectionFormat="of" derivedContent="RFC5890"/>.</t>
      <t indent="0" pn="section-3-14">All Domain Name labels used as entries or base RDAP URLs in the registries defined in this document <bcp14>MUST</bcp14> be only represented in lowercase.</t>
    </section>
    <section anchor="domainrdapreg" numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-bootstrap-service-registry-">Bootstrap Service Registry for Domain Name Space</name>
      <t indent="0" pn="section-4-1">The JSON output of this registry contains domain label entries attached to the root, grouped by base RDAP URLs, as shown in this example.
</t>
      <sourcecode type="json" markers="false" pn="section-4-2">
{
    "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/"
        ]
      ]
    ]
}
</sourcecode>
      <t indent="0" pn="section-4-3">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 in the Service URL Array of the matching second-level array are the valid base RDAP URLs as described in <xref target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/>.</t>
      <t indent="0" pn="section-4-4">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" format="default" sectionFormat="of" derivedContent="RFC9082"/> 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 indent="0" pn="section-4-5">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 indent="0" pn="section-4-6">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 indent="0" pn="section-4-7">The entry for the root of the domain name space is specified as "".</t>
    </section>
    <section anchor="iprdapreg" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-bootstrap-service-registrie">Bootstrap Service Registries for Internet Numbers</name>
      <t indent="0" pn="section-5-1">This section discusses IPv4 and IPv6 address space and Autonomous System numbers.</t>
      <t indent="0" pn="section-5-2">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" format="default" sectionFormat="of" derivedContent="RFC9082"/>. 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 numbered="true" toc="include" removeInRFC="false" pn="section-5.1">
        <name slugifiedName="name-bootstrap-service-registry-f">Bootstrap Service Registry for IPv4 Address Space</name>
        <t indent="0" pn="section-5.1-1">The JSON output of this registry contains IPv4 prefix entries, specified in Classless Inter-domain Routing (CIDR) format <xref target="RFC4632" format="default" sectionFormat="of" derivedContent="RFC4632"/> and grouped by RDAP URLs, as shown in this example.
</t>
        <sourcecode type="json" markers="false" pn="section-5.1-2">
{
    "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/"
        ]
      ]
    ]
}
</sourcecode>
        <t indent="0" pn="section-5.1-3">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" format="default" sectionFormat="of" derivedContent="RFC9082"/> 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 numbered="true" toc="include" removeInRFC="false" pn="section-5.2">
        <name slugifiedName="name-bootstrap-service-registry-fo">Bootstrap Service Registry for IPv6 Address Space</name>
        <t indent="0" pn="section-5.2-1">The JSON output of this registry contains IPv6 prefix entries,
        using <xref target="RFC5952" format="default" sectionFormat="of" derivedContent="RFC5952"/> text representation of
        the address prefixes format, grouped by base RDAP URLs, as shown in
        this example.
</t>
        <sourcecode type="json" markers="false" pn="section-5.2-2">
{
    "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/"
        ]
      ]
    ]
}
</sourcecode>
        <t indent="0" pn="section-5.2-3">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" format="default" sectionFormat="of" derivedContent="RFC9082"/> is then appended to the base URL to complete the
        query. The complete query 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 numbered="true" toc="include" removeInRFC="false" pn="section-5.3">
        <name slugifiedName="name-bootstrap-service-registry-for">Bootstrap Service Registry for AS Number Space</name>
        <t indent="0" pn="section-5.3-1">The JSON output of this registry contains entries for AS number
	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.,
	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" format="default" sectionFormat="of" derivedContent="RFC5396"/>. Ranges
	<bcp14>MUST NOT</bcp14> overlap.
</t>
        <sourcecode type="json" markers="false" pn="section-5.3-2">
{
    "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/"
        ]
      ]
    ]
}
</sourcecode>
        <t indent="0" pn="section-5.3-3">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" format="default" sectionFormat="of" derivedContent="RFC9082"/> 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 numbered="true" toc="include" removeInRFC="false" pn="section-6">
      <name slugifiedName="name-entity">Entity</name>
      <t indent="0" pn="section-6-1">Entities (such as contacts, registrants, or registrars) can be queried by handle as described in <xref target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/>. Since there is no global 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" format="default" sectionFormat="of" derivedContent="RFC8521"/> <bcp14>MAY</bcp14> also be used.</t>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-7">
      <name slugifiedName="name-non-existent-entries-or-rda">Non-existent Entries or RDAP URL Values</name>
      <t indent="0" pn="section-7-1">The registries may not contain the requested value. In these cases, there is no known RDAP server for that requested value, and the client <bcp14>SHOULD</bcp14> provide an appropriate error message to the user.</t>
    </section>
    <section anchor="deploy" numbered="true" toc="include" removeInRFC="false" pn="section-8">
      <name slugifiedName="name-deployment-and-implementati">Deployment and Implementation Considerations</name>
      <t indent="0" pn="section-8-1">This method relies on the fact that RDAP clients are fetching the
      IANA registries to then find the servers locally. Clients <bcp14>SHOULD NOT</bcp14> fetch the registry on every RDAP request. Clients
      <bcp14>SHOULD</bcp14> cache the registry, but use underlying protocol
      signaling, such as the HTTP Expires header field <xref target="RFC7234" format="default" sectionFormat="of" derivedContent="RFC7234"/>, to identify when it is time to refresh the cached
      registry.</t>
      <t indent="0" pn="section-8-2">Some authorities of registration data may work together on sharing their information for a common service, including mutual redirection <xref target="I-D.ietf-weirds-redirects" format="default" sectionFormat="of" derivedContent="REDIRECT-RDAP"/>.</t>
      <t indent="0" pn="section-8-3">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 numbered="true" toc="include" removeInRFC="false" pn="section-9">
      <name slugifiedName="name-limitations">Limitations</name>
      <t indent="0" pn="section-9-1">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:
      </t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-9-2">
        <li pn="section-9-2.1">entities</li>
        <li pn="section-9-2.2">queries using search patterns that do not contain a terminating string that matches some entries in the registries</li>
        <li pn="section-9-2.3">nameservers</li>
        <li pn="section-9-2.4">help</li>
      </ul>
    </section>
    <section anchor="abnf" numbered="true" toc="include" removeInRFC="false" pn="section-10">
      <name slugifiedName="name-formal-definition">Formal Definition</name>
      <t indent="0" pn="section-10-1">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" format="default" sectionFormat="of" derivedContent="RFC8259"/>. Those elements are used to describe the JSON structure of the registries.</t>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-10.1">
        <name slugifiedName="name-imported-json-terms">Imported JSON Terms</name>
        <dl indent="3" newline="false" spacing="normal" pn="section-10.1-1">
          <dt pn="section-10.1-1.1">OBJECT:
          </dt>
          <dd pn="section-10.1-1.2">a JSON object, defined in <xref target="RFC8259" sectionFormat="of" section="4" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8259#section-4" derivedContent="RFC8259"/>
          </dd>
          <dt pn="section-10.1-1.3">MEMBER:
          </dt>
          <dd pn="section-10.1-1.4">a member of a JSON object, defined in <xref target="RFC8259" format="default" sectionFormat="of" section="4" derivedLink="https://rfc-editor.org/rfc/rfc8259#section-4" derivedContent="RFC8259"/>
          </dd>
          <dt pn="section-10.1-1.5">MEMBER-NAME:
          </dt>
          <dd pn="section-10.1-1.6">the name of a MEMBER, defined as a "string" in                       
      <xref target="RFC8259" sectionFormat="of" section="4" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8259#section-4" derivedContent="RFC8259"/>
          </dd>
          <dt pn="section-10.1-1.7">MEMBER-VALUE:
          </dt>
          <dd pn="section-10.1-1.8">the value of a MEMBER, defined as a "value" in                      
          <xref target="RFC8259" sectionFormat="of" section="4" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8259#section-4" derivedContent="RFC8259"/>
          </dd>
          <dt pn="section-10.1-1.9">ARRAY:
          </dt>
          <dd pn="section-10.1-1.10">an array, defined in <xref target="RFC8259" format="default" sectionFormat="of" section="5" derivedLink="https://rfc-editor.org/rfc/rfc8259#section-5" derivedContent="RFC8259"/>
          </dd>
          <dt pn="section-10.1-1.11">ARRAY-VALUE:
          </dt>
          <dd pn="section-10.1-1.12">an element of an ARRAY, defined in <xref target="RFC8259" sectionFormat="of" section="5" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8259#section-5" derivedContent="RFC8259"/>
          </dd>
          <dt pn="section-10.1-1.13">STRING:
          </dt>
          <dd pn="section-10.1-1.14">a "string", as defined in <xref target="RFC8259" format="default" sectionFormat="of" section="7" derivedLink="https://rfc-editor.org/rfc/rfc8259#section-7" derivedContent="RFC8259"/>
          </dd>
        </dl>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-10.2">
        <name slugifiedName="name-registry-syntax">Registry Syntax</name>
        <t indent="0" pn="section-10.2-1">Using the above terms for the JSON structures, the syntax of a
   registry is defined as follows:
</t>
        <dl indent="3" newline="false" spacing="normal" pn="section-10.2-2">
          <dt pn="section-10.2-2.1">rdap-bootstrap-registry:
          </dt>
          <dd pn="section-10.2-2.2">an OBJECT containing a MEMBER version and a MEMBER publication, an optional MEMBER description, and a MEMBER services-list
  </dd>
          <dt pn="section-10.2-2.3">version:
          </dt>
          <dd pn="section-10.2-2.4">a MEMBER with MEMBER-NAME "version" and MEMBER-VALUE a STRING
  </dd>
          <dt pn="section-10.2-2.5">publication: 
          </dt>
          <dd pn="section-10.2-2.6">a MEMBER with MEMBER-NAME "publication" and MEMBER-VALUE a STRING
  </dd>
          <dt pn="section-10.2-2.7">description:
          </dt>
          <dd pn="section-10.2-2.8">a MEMBER with MEMBER-NAME "description" and MEMBER-VALUE a STRING
  </dd>
          <dt pn="section-10.2-2.9">services-list:
          </dt>
          <dd pn="section-10.2-2.10">a MEMBER with MEMBER-NAME "services" and MEMBER-VALUE a services-array
  </dd>
          <dt pn="section-10.2-2.11">services-array:
          </dt>
          <dd pn="section-10.2-2.12">an ARRAY, where each ARRAY-VALUE is a service
  </dd>
          <dt pn="section-10.2-2.13">service:
          </dt>
          <dd pn="section-10.2-2.14">an ARRAY of 2 elements, where the first ARRAY-VALUE is an entry-list and the second ARRAY-VALUE is a service-uri-list
  </dd>
          <dt pn="section-10.2-2.15">entry-list:
          </dt>
          <dd pn="section-10.2-2.16">an ARRAY, where each ARRAY-VALUE is an entry
  </dd>
          <dt pn="section-10.2-2.17">entry: 
          </dt>
          <dd pn="section-10.2-2.18">a STRING
  </dd>
          <dt pn="section-10.2-2.19">service-uri-list:
          </dt>
          <dd pn="section-10.2-2.20">an ARRAY, where each ARRAY-VALUE is a service-uri
  </dd>
          <dt pn="section-10.2-2.21">service-uri:
          </dt>
          <dd pn="section-10.2-2.22">a STRING
  </dd>
        </dl>
      </section>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-11">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-11-1">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 uses TLS <xref target="RFC8446" format="default" sectionFormat="of" derivedContent="RFC8446"/>.
      </t>
      <t indent="0" pn="section-11-2">Additional considerations on using RDAP are described in <xref target="RFC7481" format="default" sectionFormat="of" derivedContent="RFC7481"/>.</t>
    </section>
    <section anchor="ianaconsiderations" numbered="true" toc="include" removeInRFC="false" pn="section-12">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-12-1">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 Sections <xref target="struct" format="counter" sectionFormat="of" derivedContent="3"/>, <xref target="domainrdapreg" format="counter" sectionFormat="of" derivedContent="4"/>, and <xref target="iprdapreg" format="counter" sectionFormat="of" derivedContent="5"/>, with the formal syntax specified in <xref target="abnf" format="default" sectionFormat="of" derivedContent="Section 10"/>. The registries <bcp14>MUST</bcp14> be accessible only through HTTPS (TLS <xref target="RFC8446" format="default" sectionFormat="of" derivedContent="RFC8446"/>) transport.</t>
      <t indent="0" pn="section-12-2">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" format="default" sectionFormat="of" derivedContent="ipv4reg"/>, <xref target="ipv6reg" format="default" sectionFormat="of" derivedContent="ipv6reg"/>, <xref target="asreg" format="default" sectionFormat="of" derivedContent="asreg"/>, and <xref target="domainreg" format="default" sectionFormat="of" derivedContent="domainreg"/>), with the addition of new RDAP server information.</t>
      <t indent="0" pn="section-12-3">IANA updates RDAP Bootstrap Services Registries entries from the
      allocation registries as those registries are updated.</t>
      <t indent="0" pn="section-12-4">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 indent="0" pn="section-12-5">IANA has created a new top-level category on the Protocol Registries 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
on-demand download in the JSON format by the general public, and that registry's URI
is listed directly on the Protocol Registries page.
</t>
      <t indent="0" pn="section-12-6">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 indent="0" pn="section-12-7">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" format="default" sectionFormat="of" derivedContent="RFC7484"/>, no issues have been reported regarding the load or the service. </t>
      <t indent="0" pn="section-12-8">As discussed in <xref target="deploy" format="default" sectionFormat="of" derivedContent="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.</t>
      <t indent="0" pn="section-12-9">The HTTP Content-Type returned to clients accessing these JSON-formatted registries <bcp14>MUST</bcp14> be "application/json", as defined in <xref target="RFC8259" format="default" sectionFormat="of" derivedContent="RFC8259"/>.</t>
      <t indent="0" pn="section-12-10">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>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-12.1">
        <name slugifiedName="name-bootstrap-service-registry-for-">Bootstrap Service Registry for IPv4 Address Space</name>
        <t indent="0" pn="section-12.1-1">Entries in this registry contain at least the following:
        </t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-12.1-2">
          <li pn="section-12.1-2.1">a CIDR <xref target="RFC4632" format="default" sectionFormat="of" derivedContent="RFC4632"/> specification of the network block being registered</li>
          <li pn="section-12.1-2.2">one or more URLs that provide the RDAP service regarding this registration</li>
        </ul>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-12.2">
        <name slugifiedName="name-bootstrap-service-registry-for-i">Bootstrap Service Registry for IPv6 Address Space</name>
        <t indent="0" pn="section-12.2-1">Entries in this registry contain at least the following:
        </t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-12.2-2">
          <li pn="section-12.2-2.1">an IPv6 prefix <xref target="RFC5952" format="default" sectionFormat="of" derivedContent="RFC5952"/> specification of the network block being registered</li>
          <li pn="section-12.2-2.2">one or more URLs that provide the RDAP service regarding this registration
 </li>
        </ul>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-12.3">
        <name slugifiedName="name-bootstrap-service-registry-for-a">Bootstrap Service Registry for AS Number Space</name>
        <t indent="0" pn="section-12.3-1">Entries in this registry contain at least the following:
        </t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-12.3-2">
          <li pn="section-12.3-2.1">a range of Autonomous System numbers being registered</li>
          <li pn="section-12.3-2.2">one or more URLs that provide the RDAP service regarding this
          registration
 </li>
        </ul>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-12.4">
        <name slugifiedName="name-bootstrap-service-registry-for-d">Bootstrap Service Registry for Domain Name Space</name>
        <t indent="0" pn="section-12.4-1">Entries in this registry contain at least the following:
        </t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-12.4-2">
          <li pn="section-12.4-2.1">a domain name attached to the root being registered</li>
          <li pn="section-12.4-2.2">one or more URLs that provide the RDAP service regarding this registration
 </li>
        </ul>
      </section>
    </section>
  </middle>
  <back>
    <displayreference target="I-D.ietf-weirds-redirects" to="REDIRECT-RDAP"/>
    <references pn="section-13">
      <name slugifiedName="name-references">References</name>
      <references pn="section-13.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author initials="S." surname="Bradner" fullname="S. Bradner">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1997" month="March"/>
            <abstract>
              <t indent="0">In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC3339" target="https://www.rfc-editor.org/info/rfc3339" quoteTitle="true" derivedAnchor="RFC3339">
          <front>
            <title>Date and Time on the Internet: Timestamps</title>
            <author initials="G." surname="Klyne" fullname="G. Klyne">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="C." surname="Newman" fullname="C. Newman">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2002" month="July"/>
            <abstract>
              <t indent="0">This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3339"/>
          <seriesInfo name="DOI" value="10.17487/RFC3339"/>
        </reference>
        <reference anchor="RFC4632" target="https://www.rfc-editor.org/info/rfc4632" quoteTitle="true" derivedAnchor="RFC4632">
          <front>
            <title>Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan</title>
            <author initials="V." surname="Fuller" fullname="V. Fuller">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="T." surname="Li" fullname="T. Li">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2006" month="August"/>
            <abstract>
              <t indent="0">This memo discusses the strategy for address assignment of the existing 32-bit IPv4 address space with a view toward conserving the address space and limiting the growth rate of global routing state. This document obsoletes the original Classless Inter-domain Routing (CIDR) spec in RFC 1519, with changes made both to clarify the concepts it introduced and, after more than twelve years, to update the Internet community on the results of deploying the technology described.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="122"/>
          <seriesInfo name="RFC" value="4632"/>
          <seriesInfo name="DOI" value="10.17487/RFC4632"/>
        </reference>
        <reference anchor="RFC5396" target="https://www.rfc-editor.org/info/rfc5396" quoteTitle="true" derivedAnchor="RFC5396">
          <front>
            <title>Textual Representation of Autonomous System (AS) Numbers</title>
            <author initials="G." surname="Huston" fullname="G. Huston">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="G." surname="Michaelson" fullname="G. Michaelson">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2008" month="December"/>
            <abstract>
              <t indent="0">A textual representation for Autonomous System (AS) numbers is defined as the decimal value of the AS number.  This textual representation is to be used by all documents, systems, and user interfaces referring to AS numbers.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5396"/>
          <seriesInfo name="DOI" value="10.17487/RFC5396"/>
        </reference>
        <reference anchor="RFC5890" target="https://www.rfc-editor.org/info/rfc5890" quoteTitle="true" derivedAnchor="RFC5890">
          <front>
            <title>Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework</title>
            <author initials="J." surname="Klensin" fullname="J. Klensin">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2010" month="August"/>
            <abstract>
              <t indent="0">This document is one of a collection that, together, describe the protocol and usage context for a revision of Internationalized Domain Names for Applications (IDNA), superseding the earlier version.  It describes the document collection and provides definitions and other material that are common to the set.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5890"/>
          <seriesInfo name="DOI" value="10.17487/RFC5890"/>
        </reference>
        <reference anchor="RFC5952" target="https://www.rfc-editor.org/info/rfc5952" quoteTitle="true" derivedAnchor="RFC5952">
          <front>
            <title>A Recommendation for IPv6 Address Text Representation</title>
            <author initials="S." surname="Kawamura" fullname="S. Kawamura">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Kawashima" fullname="M. Kawashima">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2010" month="August"/>
            <abstract>
              <t indent="0">As IPv6 deployment increases, there will be a dramatic increase in the need to use IPv6 addresses in text.  While the IPv6 address architecture in Section 2.2 of RFC 4291 describes a flexible model for text representation of an IPv6 address, this flexibility has been causing problems for operators, system engineers, and users.  This document defines a canonical textual representation format.  It does not define a format for internal storage, such as within an application or database.  It is expected that the canonical format will be followed by humans and systems when representing IPv6 addresses as text, but all implementations must accept and be able to handle any legitimate RFC 4291 format.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5952"/>
          <seriesInfo name="DOI" value="10.17487/RFC5952"/>
        </reference>
        <reference anchor="RFC7258" target="https://www.rfc-editor.org/info/rfc7258" quoteTitle="true" derivedAnchor="RFC7258">
          <front>
            <title>Pervasive Monitoring Is an Attack</title>
            <author initials="S." surname="Farrell" fullname="S. Farrell">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="H." surname="Tschofenig" fullname="H. Tschofenig">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2014" month="May"/>
            <abstract>
              <t indent="0">Pervasive monitoring is a technical attack that should be mitigated in the design of IETF protocols, where possible.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="188"/>
          <seriesInfo name="RFC" value="7258"/>
          <seriesInfo name="DOI" value="10.17487/RFC7258"/>
        </reference>
        <reference anchor="RFC7480" target="https://www.rfc-editor.org/info/rfc7480" quoteTitle="true" derivedAnchor="RFC7480">
          <front>
            <title>HTTP Usage in the Registration Data Access Protocol (RDAP)</title>
            <author initials="A." surname="Newton" fullname="A. Newton">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="B." surname="Ellacott" fullname="B. Ellacott">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="N." surname="Kong" fullname="N. Kong">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2015" month="March"/>
            <abstract>
              <t indent="0">This document is one of a collection that together describes the Registration Data Access Protocol (RDAP).  It describes how RDAP is transported using the Hypertext Transfer Protocol (HTTP).  RDAP is a successor protocol to the very old WHOIS protocol.  The purpose of this document is to clarify the use of standard HTTP mechanisms for this application.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="95"/>
          <seriesInfo name="RFC" value="7480"/>
          <seriesInfo name="DOI" value="10.17487/RFC7480"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" quoteTitle="true" derivedAnchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author initials="B." surname="Leiba" fullname="B. Leiba">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2017" month="May"/>
            <abstract>
              <t indent="0">RFC 2119 specifies common key words that may be used in protocol  specifications.  This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the  defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC8259" target="https://www.rfc-editor.org/info/rfc8259" quoteTitle="true" derivedAnchor="RFC8259">
          <front>
            <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
            <author initials="T." surname="Bray" fullname="T. Bray" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2017" month="December"/>
            <abstract>
              <t indent="0">JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format.  It was derived from the ECMAScript Programming Language Standard.  JSON defines a small set of formatting rules for the portable representation of structured data.</t>
              <t indent="0">This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="90"/>
          <seriesInfo name="RFC" value="8259"/>
          <seriesInfo name="DOI" value="10.17487/RFC8259"/>
        </reference>
      </references>
      <references pn="section-13.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="asreg" target="https://www.iana.org/assignments/as-numbers" quoteTitle="true" derivedAnchor="asreg">
          <front>
            <title>Autonomous System (AS) Numbers</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="domainreg" target="https://www.iana.org/domains/root/db" quoteTitle="true" derivedAnchor="domainreg">
          <front>
            <title>Root Zone Database</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="ipv4reg" target="https://www.iana.org/assignments/ipv4-address-space" quoteTitle="true" derivedAnchor="ipv4reg">
          <front>
            <title>IANA IPv4 Address Space Registry</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="ipv6reg" target="https://www.iana.org/assignments/ipv6-unicast-address-assignments" quoteTitle="true" derivedAnchor="ipv6reg">
          <front>
            <title>IPv6 Global Unicast Address Assignments</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="I-D.ietf-weirds-redirects" quoteTitle="true" target="https://datatracker.ietf.org/doc/html/draft-ietf-weirds-redirects-04" derivedAnchor="REDIRECT-RDAP">
          <front>
            <title>Redirection Service for Registration Data Access Protocol</title>
            <author initials="C.M." surname="Martinez" fullname="Carlos M. Martinez" role="editor"/>
            <author initials="L." surname="Zhou" fullname="Linlin Zhou" role="editor"/>
            <author initials="G." surname="Rada" fullname="Gerardo Rada"/>
            <date month="July" year="2014"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-weirds-redirects-04"/>
          <refcontent>Work in Progress</refcontent>
        </reference>
        <reference anchor="RFC7071" target="https://www.rfc-editor.org/info/rfc7071" quoteTitle="true" derivedAnchor="RFC7071">
          <front>
            <title>A Media Type for Reputation Interchange</title>
            <author initials="N." surname="Borenstein" fullname="N. Borenstein">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Kucherawy" fullname="M. Kucherawy">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2013" month="November"/>
            <abstract>
              <t indent="0">This document defines the format of reputation response data ("reputons"), the media type for packaging it, and definition of a registry for the names of reputation applications and response sets.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7071"/>
          <seriesInfo name="DOI" value="10.17487/RFC7071"/>
        </reference>
        <reference anchor="RFC7234" target="https://www.rfc-editor.org/info/rfc7234" quoteTitle="true" derivedAnchor="RFC7234">
          <front>
            <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
            <author initials="R." surname="Fielding" fullname="R. Fielding" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Nottingham" fullname="M. Nottingham" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Reschke" fullname="J. Reschke" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2014" month="June"/>
            <abstract>
              <t indent="0">The Hypertext Transfer Protocol (HTTP) is a stateless \%application- level protocol for distributed, collaborative, hypertext information systems.  This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7234"/>
          <seriesInfo name="DOI" value="10.17487/RFC7234"/>
        </reference>
        <reference anchor="RFC7481" target="https://www.rfc-editor.org/info/rfc7481" quoteTitle="true" derivedAnchor="RFC7481">
          <front>
            <title>Security Services for the Registration Data Access Protocol (RDAP)</title>
            <author initials="S." surname="Hollenbeck" fullname="S. Hollenbeck">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="N." surname="Kong" fullname="N. Kong">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2015" month="March"/>
            <abstract>
              <t indent="0">The Registration Data Access Protocol (RDAP) provides "RESTful" web services to retrieve registration metadata from Domain Name and Regional Internet Registries.  This document describes information security services, including access control, authentication, authorization, availability, data confidentiality, and data integrity for RDAP.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="95"/>
          <seriesInfo name="RFC" value="7481"/>
          <seriesInfo name="DOI" value="10.17487/RFC7481"/>
        </reference>
        <reference anchor="RFC7484" target="https://www.rfc-editor.org/info/rfc7484" quoteTitle="true" derivedAnchor="RFC7484">
          <front>
            <title>Finding the Authoritative Registration Data (RDAP) Service</title>
            <author initials="M." surname="Blanchet" fullname="M. Blanchet">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2015" month="March"/>
            <abstract>
              <t indent="0">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.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7484"/>
          <seriesInfo name="DOI" value="10.17487/RFC7484"/>
        </reference>
        <reference anchor="RFC8446" target="https://www.rfc-editor.org/info/rfc8446" quoteTitle="true" derivedAnchor="RFC8446">
          <front>
            <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
            <author initials="E." surname="Rescorla" fullname="E. Rescorla">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2018" month="August"/>
            <abstract>
              <t indent="0">This document specifies version 1.3 of the Transport Layer Security (TLS) protocol.  TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
              <t indent="0">This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961.  This document also specifies new requirements for TLS 1.2 implementations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8446"/>
          <seriesInfo name="DOI" value="10.17487/RFC8446"/>
        </reference>
        <reference anchor="RFC8521" target="https://www.rfc-editor.org/info/rfc8521" quoteTitle="true" derivedAnchor="RFC8521">
          <front>
            <title>Registration Data Access Protocol (RDAP) Object Tagging</title>
            <author initials="S." surname="Hollenbeck" fullname="S. Hollenbeck">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Newton" fullname="A. Newton">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2018" month="November"/>
            <abstract>
              <t indent="0">The Registration Data Access Protocol (RDAP) includes a method that can be used to identify the authoritative server for processing domain name, IP address, and autonomous system number queries.  The method does not describe how to identify the authoritative server for processing other RDAP query types, such as entity queries.  This limitation exists because the identifiers associated with these query types are typically unstructured.  This document updates RFC 7484 by describing an operational practice that can be used to add structure to RDAP identifiers and that makes it possible to identify the authoritative server for additional RDAP queries.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="221"/>
          <seriesInfo name="RFC" value="8521"/>
          <seriesInfo name="DOI" value="10.17487/RFC8521"/>
        </reference>
        <reference anchor="RFC9082" target="https://www.rfc-editor.org/info/rfc9082" quoteTitle="true" derivedAnchor="RFC9082">
          <front>
            <title>Registration Data Access Protocol (RDAP) Query Format</title>
            <author initials="S." surname="Hollenbeck" fullname="S. Hollenbeck">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Newton" fullname="A. Newton">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2021" month="June"/>
            <abstract>
              <t indent="0">This document describes uniform patterns to construct HTTP URLs that may be used to retrieve registration information from registries (including both Regional Internet Registries (RIRs) and Domain Name Registries (DNRs)) using "RESTful" web access patterns.  These uniform patterns define the query syntax for the Registration Data Access Protocol (RDAP). This document obsoletes RFC 7482.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="95"/>
          <seriesInfo name="RFC" value="9082"/>
          <seriesInfo name="DOI" value="10.17487/RFC9082"/>
        </reference>
        <reference anchor="RFC9083" target="https://www.rfc-editor.org/info/rfc9083" quoteTitle="true" derivedAnchor="RFC9083">
          <front>
            <title>JSON Responses for the Registration Data Access Protocol (RDAP)</title>
            <author initials="S." surname="Hollenbeck" fullname="S. Hollenbeck">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Newton" fullname="A. Newton">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2021" month="June"/>
            <abstract>
              <t indent="0">This document describes JSON data structures representing registration information maintained by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs).  These data structures are used to form Registration Data Access Protocol (RDAP) query responses. This document obsoletes RFC 7483.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="95"/>
          <seriesInfo name="RFC" value="9083"/>
          <seriesInfo name="DOI" value="10.17487/RFC9083"/>
        </reference>
      </references>
    </references>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-changes-since-rfc-7484">Changes since RFC 7484</name>
      <t indent="0" pn="section-appendix.a-1">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 numbered="false" toc="include" removeInRFC="false" pn="section-appendix.b">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.b-1">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 <contact fullname="Andy Newton"/>. All the people involved in these discussions are
herein acknowledged. <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.</t>
      <t indent="0" pn="section-appendix.b-2">
<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 <xref target="RFC7071" sectionFormat="of" section="6.2" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7071#section-6.2" derivedContent="RFC7071"/>.  This new version [This document] received comments and
suggestions 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 for RFC 7484 were
submitted by <contact fullname="Pieter Vandepitte"/> and were applied to this
document.
</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.c">
      <name slugifiedName="name-authors-address">Author's Address</name>
      <author initials="M." surname="Blanchet" fullname="Marc Blanchet">
        <organization showOnFrontPage="true">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>
    </section>
  </back>
</rfc>
