Hi Mario, On 09.01.25 12:17, Mario Loffredo wrote:
In conclusion, I do believe that the RTT-flow is needed to efficiently implement a possible transition process and the rdap-versioning spec is helpful in this respect.
This was exactly my point, that with the current draft 2-RTT would be eventually a must making the version negotiation client driven.
This poses a serious issue with redirects, where you would have to interrupt automatic redirect of your client and do 2-RTT with the redirect target to replace query parameters fitting the redirect target.
My alternative proposal was heading into direction of fully server driven content negotiation leveraging properties of semantic versioning. So client telling what versions it supports without prior knowledge of versions supported by the server and the server responding with a best fitting answer instead of falling back to the default version as the draft proposes now.
Kind Regards, Pawel
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
