1. Introduction

This section preserves the RFC text for RDAP RIR search, including rirSearch1, ips, autnums, ipSearchResults, autnumSearchResults, relation links, JSON examples, response behavior, reverse search, conformance, and IANA registrations.

Original RFC Text

1.  Introduction

   The Registration Data Access Protocol (RDAP) [RFC7480] is used by
   Regional Internet Registries (RIRs) and Domain Name Registries (DNRs)
   to provide access to their resource registration information.  The
   core specifications for RDAP define basic search functionality, but
   this is limited to domains, nameservers, and entities.  No searches
   were defined for IP networks or autonomous system numbers.  In an
   effort to have RDAP reach feature parity with the existing RIR WHOIS
   [RFC3912] services in this respect, this document defines additional
   search options for IP networks and autonomous system numbers.

   While this document is written in terms of RIRs and DNRs for the sake
   of consistency with earlier RDAP documents such as [RFC9082] and
   [RFC9083], the functionality described here may be used by any RDAP
   server operator that hosts Internet Number Resource (INR) objects.

1.1.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   Indentation and whitespace in examples are provided only to
   illustrate element relationships and are not required features of
   this specification.

   "..." in examples is used as shorthand for elements defined outside
   of this document, as well as to abbreviate elements that are too
   long.