Mario,
Snipping a bunch of stuff :)
...
On 10/9/24 03:53, Mario Loffredo wrote:
Hi Andy,
But, provided that some custom and standard specifications allow a
server to return response extensions by itself, I do believe that the
document should clarify what the server is expected to do when the
client doesn't specify them in the extensions parameter.
Should the server return a response or should it return an error?
It should not return an error because that would be incompatible with
today's behavior.
I agree that this needs to be specified. Thanks. Issue here:
https://github.com/anewton1998/draft-regext-ext-json-media-type/issues/36
Per your answer to my prior question about the server handling the
case where the client omits rdap_level_0, I guess the first option
because otherwise this draft should also update some existing
specifications.
But this means that the client could mention only the extensions which
are considered optional by the server and omit the other ones.
A client will never be able to override server policy. It can "request"
but it cannot "demand". :)
If we will ever deprecate rdap_level_0 to move to rdap_level_1, at any
time of the transition process, only one of them will be optional and
the other one will be returned by default.
That sounds right to me.
-andy
_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org
