Introduce version field in DTP transfer request/response transaction and handle mismatch. This is a *BREAKING* at the wire level

[jeanbaptistelab]

No description provided.

[troelsjessen]

Instead of just putting a version field in the request, what about putting a min and max version supported by the client? And then add a selected version field in the response from the server.
16 bits per field should do :-)

[jeanbaptistelab]

Instead of just putting a version field in the request, what about putting a min and max version supported by the client? And then add a selected version field in the response from the server. 16 bits per field should do :-)

Yes, that's an option. I choose a "uint32_t" for this field so as to not introduce packing ambiguities. As this is the first change that introduces version concept of the wire protocol, I thought that for now, it would be enough to simply bail out. When working on version 2 of the protocol, we can revisit this and implement a solution where the client can handle multiple versions ?