> Le 12 juill. 2023 à 09:35, Andrew Newton <a...@hxr.us> a écrit : > > Thanks for the review Pawel. My response is in-line: > > On Wed, Jul 12, 2023 at 2:41 AM Pawel Kowalik <kowa...@denic.de> wrote: >> > >> >> The last question to the discovery part. Shall client have a possibility >> to find out support for this extension prior to a real request, for >> example by OPTIONS http request? I understand this is not a real >> extension, so it would not appear in RDAP conformance when requesting >> /help path. > > This document does not disallow use of rdap-x in OPTIONS, so I guess > they could. Are you advocating some specific behavior? Is there a CORS > scenario we should think of? > > And though this is not an RDAP extension, a client using /help would > know if a server supports rdap-x. > > I'm a bit skeptical of RDAP specific discovery scenarios. I know > browsers will do HEAD and OPTIONS requests, but that's not RDAP > specific. To my knowledge, there are no RDAP clients that do a /help > and then change their behavior.
Maybe. But currently RDAP clients did not have to. If the clients now need to adapt their behaviour because of negotiation, then we shall define a way. /help or else, I don’t care much, but the fact that the clients are not doing it right now is irrelevant to this discussion, at least to me. Marc. > /help is used by humans, if at all. > > -andy > > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
