Hi, On 02.07.26 14:41, Andy Newton wrote:
Additional suggested change:Section 5.4.1 OLD Removing a required protocol element from a response; NEW Removing a required protocol element from a response that has not yet been fully deprecated;Is this really necessary? Why would a protocol element be in an extension if it was fully deprecated?[ML2] This is inherent in managing the transition period from the old to the new one. At some point, the old version will be removed from the response. Therefore, stating that removing a required protocol element from a response is a breaking change seems to me equivalent to stating that required protocol elements can never be removed, even if they have been completely deprecated and all clients have switched from the old version to the new one.I see your point. I'll add this.
I just wanted to point out, that fulfilment of this condition can never be stated with certainty by the server "clients have switched from the old version to the new one.".
Basically client has no way to tell the server if it switched or not, because it happens only after the response has been received from the server.
Also in most cases not every client is even known to the server, when out-of-band approaches would come into consideration. Only in case of restricted access RDAP with authentication of clients this may be considered at all.
In terms of interoperability it is something different if the client would notice the extension it used to process is not there any longer as opposed to receiving a response with a known extension identifier but with the content which cannot be processed.
Kind Regards, Pawel
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
