On 10/4/24 04:44, Mario Loffredo wrote:
[ML] I was talking about "unrequested extensions" which can be
different from "unknown extensions". I remind you that:
1) some custom extensions reported in the RDAP Extensions registry are
returned by default, most likely to make the RDAP response consistent
with the WHOIS response. After all, up to now, clients haven't been
allowed to specify their preferences about response extensions hence
servers have been free to extend their responses as needed;
2) based on what is stated by some RFCs, the server may autonomously
return response extensions when certain conditions occurred (see the
redacted property in RFC9537 and the paging_metadata property in
RFC8977) or to provide clients with additional information about its
capabilities (see the properties added to the "/help"response in
RFC9536 and RFC9560).
All of the response extensions above may be returned by servers
without being requested by clients.
What do you propose to address this topic ?
Either a client has code to handle an extension or it doesn't, so I
don't know how that is helpful to a piece of software. However, for
troubleshooting it might be worth putting it in the "version"
information in the versioning extension.
In addition to it, I see a potential issue with a "/help" request
including the extensions parameter and the related response.
Quoting Section 4.1 of RFC9083, Section 2.1 of
draft-ietf-regext-rdap-extensions states that:
The "/help" response returns an
"rdapConformance" member containing the identifiers for all
extensions used by the server.
Section 3 of draft-ietf-regext-rdap-x-media-type states that:
When there is a mismatch between extension parameters and the
rdapConformance
array, clients SHOULD give preference to the rdapConformance array
So, in general, whatever could be the extensions parameter of a
"/help" request (most likely only "rdap_level_0"), the server would
ignore it to build the response.
Don't you think the client could response could misunderstand that
response ?
That statement in Section 3 is only provided for guidance to clients
when there is a mismatch in a server response between the extensions
parameter and the rdapConformance array. In other words, the server gave
conflicting information therefore follow the "rdapConformance" array.
Why? Because we had to pick one.
-andy
_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org
