Hi Gavin, Andy, Wanted to input couple of more thoughts:
It might help to also exemplify a “geofeed” relation from RFC 9877 [1] since that would highlight the usefulness of an explicit redirect. In this case, a user is saying, “Yah, I know that the RIRs publish network registration data through RDAP but my immediate concern is to just get the geofeed URI for an IP address." If we do end up considering the “rdap-base-down” and “rdap-base-up” relations, beside the “rdap-bootstrap” relation, since they all would start with a base URI (collection of resources), to inform implementors better, it might help to expound how to construct the redirect URI for an RDAP redirect request with such a relation: append the lookup path from that request to the base URI from "href” for such a web link. This would be in contrast with when ”href" from a web link is already for a “leaf” resource (e.g., a lookup URI for domain info from a downstream registrar). Hope this is useful. :) Jasdip [1] https://www.rfc-editor.org/rfc/rfc9877.html#name-example From: Jasdip Singh <[email protected]> Date: Tuesday, July 7, 2026 at 1:39 PM To: Andy Newton <[email protected]>; Pawel Kowalik <[email protected]>; [email protected] <[email protected]> Subject: [regext] Re: I-D Action: draft-ietf-regext-rdap-referrals-04.txt Hi Andy, From: Andy Newton <[email protected]> Date: Tuesday, July 7, 2026 at 11:13 AM To: Jasdip Singh <[email protected]>; Pawel Kowalik <[email protected]>; [email protected] <[email protected]> Subject: [regext] Re: I-D Action: draft-ietf-regext-rdap-referrals-04.txt > If this extension's purpose is to simply select the most appropriate link > from a lookup response, then proposing a new “rdap-bootstrap” relation (and > related use case) seems extraneous, given RFC 9224 already enables a server > to redirect for IANA allocations to other registries. We might have discussed > this before. :) We probably did, and I forgot where we landed. So, without previous recollection... the rdap-bootstrap case can be used when a bootstrap server has other redirect behavior. For example, it is possible that a bootstrap server can construct its redirects from the NRO extended stats files thus offering clients a direct path to the server holding the resource instead of bouncing between RIRs. And there are other example I can think about, such as a bootstrap server that offers IP to ASN mapped redirects. All this is to say that "rdap-bootstrap" is a way for the client to say "I want the 9224 redirect". It also allows a typical resource server to function as a bootstrap server. For example, the server at .example should produce a 404 for "foo.not_an_example" but if handed "rdap-bootstrap" could then redirect to a more appropriate place. [JS] Yes, these scenarios make sense. Thanks for the explanation. Jasdip
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
