Hi Gavin, Thanks for incorporating previous feedback. Agree with Pawel on the direction of this specification. :)
Some input on this version: Like the “rdap-bootstrap” relation type idea! As for the RIR Search relation types, it says: "Furthermore, servers SHOULD only use the "/redirects0_ref" path in an HTTP redirect when the link relationship type is one for a terminal relationship such as "rdap-top" and "rdap-bottom" (i.e., "rdap-up" and "rdap-down" do not explicitly express a relationship that is the end of a series of redirects).” I think beside the termination criterion here, another criterion in returning a single object could also be considered. Since “rdap-up” and “rdap-top” searches could both at most return one object whereas “rdap-down” and “rdap-bottom” searches could return zero or more, including one sometimes. Therefore, using "the "/redirects0_ref” path in an HTTP redirect should be possible for all these relation types, it seems. Also, could expound that IANA RDAP Bootstrap files would most likely be employed to determine such RIR1-to-RIR2 redirections. For these relation types, might help to informatively refer to RFC 9910. Thanks, Jasdip From: Gavin Brown <[email protected]> Date: Tuesday, February 17, 2026 at 10:23 AM To: [email protected] <[email protected]> Cc: [email protected] <[email protected]> Subject: [regext] Re: I-D Action: draft-ietf-regext-rdap-referrals-03.txt Greetings WG, This version includes feedback received since the previous version. Also, the title has been changed from “Efficient RDAP Referrals” to “Explicit RDAP Redirects”. We believe this title more accurately reflects the functionality currently described in the document. As a result of the change in terminology (from “referral” to “redirect”), the extension identifier has also been changed. The changes are described in more detail in the “Change Log” section: https://www.ietf.org/archive/id/draft-ietf-regext-rdap-referrals-03.html#name-changes-from-02-to-03 FAO chairs: Andy and I would like to request the HTTP Directorate to review of this document. Thanks, Andy & Gavin. On 17 Feb 2026, at 3:09 pm, [email protected] wrote: Internet-Draft draft-ietf-regext-rdap-referrals-03.txt is now available. It is a work item of the Registration Protocols Extensions (REGEXT) WG of the IETF. Title: Explicit RDAP Redirects Authors: Gavin Brown Andy Newton Name: draft-ietf-regext-rdap-referrals-03.txt Pages: 10 Dates: 2026-02-17 Abstract: This document describes an RDAP extension that allows RDAP clients to request to be redirected to a related RDAP record for a resource. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-referrals/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-regext-rdap-referrals-03.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-rdap-referrals-03 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
