On Tue, Nov 14, 2023 at 9:02 AM Gould, James <jgo...@verisign.com> wrote: > > Andy, > > I recommend covering the use of query parameters in RDAP in the > draft-newton-regext-rdap-extensions, since it's unclear and deserves > discussion on the mailing list. I personally don' t see how the use of query > parameters would not be compatible in RDAP, since RDAP is simply a REST > interface. Query parameters provide options in a REST request, so I don't > see how RDAP is so unique to disallow the use of query parameters. The net > of what you have stated is that query parameters can be used for RDAP search > but not for RDAP lookup based on implementation of the existing redirection > services that are only used for RDAP lookup. I believe a redirection service > should not filter any query parameters and I'm not aware of any language in > RFCs that would support redirection services filtering the query parameters. > If there is an issue with the use of query parameters in RDAP, then it should > apply to both RDAP search and lookup. If query parameters cannot be used in > RDAP, then we'll need to address the use of query parameters in RFC 9082 for > RDAP search. >
James, Unfortunately this is not an academic argument. In the link I provided to this thread, there is a real-world example. Like it or not, there are deployments that follow the advice in RFC 7480 and do perform the services given in Appendix C, and there are very good reasons for doing so (also in the RFC). As to query parameters in searches, see the thread here: https://mailarchive.ietf.org/arch/msg/regext/e-x5CCXxXXFYlM_E6KXMcdxyEXc/ -andy _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
