On Tue, Oct 1, 2024 at 3:53 AM Mario Loffredo <mario.loffr...@iit.cnr.it> wrote: > > Hi Andy and Jasdip, > > > have some questions about draft-ietf-regext-rdap-x-media-type: > > 1) rdap_level_0 is included in "extensions" parameter, but it's not an > extension, i.e. it's not included in the RDAP Extensions registry. Should it > be removed? > > 2) If rdap_level_0 is an extension, is it required to be provided?
It's not an extension but is RDAP's own versioning mechanism. It's included for symmetry with the rdapConformance array and can be used for the same purpose. > > 3) If rdap_level_0 is required, what should be the server response when the > client doesn't include it or any required extension in the extension > parameter? A very good question. It should be required and a server should continue to serve information in conformance to rdap_level_0 (or return a 415 if it cannot conform to rdap_level_0 in a futuristic scenario where ther is an rdap_level_1 or whatever). > > 4) Should the server distinguish the optional and required extensions > supported? What are the definitions of an optional and required extension? How is that meaningful to a client? > > 5) With regard to your concern about the usage of query parameters, what > should be used instead in order to specify values in RDAP queries? > I mean, I could be good with using content negotiation to request for > response extensions but it looks to me unfit to convey values in a query and > we have already used that kind of query parameters in some RFCs. > Indeed, apart from the query parameters used in search queries (e.g. those > defined by RFC8977 and RFC8982) which can hardly be redirected, section 4.2 > of RFC9560 includes query parameters that don't aim to request for a response > extension and can be used in lookup queries. James Gould has already noted the hyperbolic heading in the rdap-x document, and we plan to change it. However, what you are looking for is in the rdap-extensions draft: https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-extensions-04#name-usage-in-query-parameters https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-extensions-04#redirects_author https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-extensions-04#referrals https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-extensions-04#security_considerations https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-extensions-04#privacy_considerations -andy _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
