7. Operational Considerations

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

7.  Operational Considerations

   When using a link object for a single-result search, a server may
   replace a search URL with a lookup URL, because the behaviour of the
   lookup URL is the same as that of the search URL at the time the
   response is generated.  One difference between these approaches is
   that when using the lookup URL, the server is effectively performing
   the search on behalf of the client as at the time of response
   generation.  If there is no change to the relevant database state
   between the time when the original response is generated and the time
   when the client resolves the link relation target, then the search
   URL and the lookup URL will lead to the same result.  However, if
   there is a change to the relevant database state, then the lookup URL
   may lead to a different result from that of the search URL.  Server
   operators should consider which type of URL will be more effective
   for their clients when implementing this specification.

   Where this document includes HTTP reason phrases, that is purely for
   the benefit of the reader and is not an indication that those phrases
   need to be used as-is in responses.