Last Call Review of draft-ietf-regext-rdap-rir-search-14
review-ietf-regext-rdap-rir-search-14-artart-lc-levine-2025-02-05-00

For this ART area review, I looked at the document as someone who is reasonably
familiar with RDAP, having written some RDAP clients that look up information
about both domains and IPs.  It is clear enough and I was able to try a few
experimental searches that returned what I expected.

Result: Ready with Nits

Section 2.1 says that search patterns are the ones in section 4.1 of RFC9082. 
That section describes patterns with a trailing *, with a special case for a
domain suffix like "exam*.com".  That special case doesn't make much sense for
searching RIR data.  It would be helpful either to exclude that case, or
clarify that yes, you can search for patterns with a trailing domain suffix.

Section 3.1 says the status keyword can have any of the values in section 4.6
of RFC9083, again, many of which don't make sense for RIR searches. (pending
create? renew prohibited?) Section 3.3 describes status searching but only uses
"active" or "inactive". It would be helpful to clarify either that you can use
all of the 9083 values even though most of them will never match, or list the
values that are useful.

In section 3.4, I can't tell why you would use an up-active or top-active
search rather than up/foo?status=active or top/bar?status=active.  It looks
like they're equivalent.

In section 10.2 the link to the Link Relations registry links to the wrong
registry. That's very meta.