-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Requester shall use the selected version in all future communication of other requests. #48
Comments
Fix DMTF#48 Signed-off-by: yi1 li <yi1.li@intel.com>
Fix DMTF#48 spdm_connection_info_t should only store one negotiated spdm version. Signed-off-by: yi1 li <yi1.li@intel.com>
Fix DMTF#48 Signed-off-by: yi1 li <yi1.li@intel.com>
Fix DMTF#48 spdm_connection_info_t should only store one negotiated spdm version. Signed-off-by: yi1 li <yi1.li@intel.com>
Fix #48 Signed-off-by: yi1 li <yi1.li@intel.com>
Fix #48 spdm_connection_info_t should only store one negotiated spdm version. Signed-off-by: yi1 li <yi1.li@intel.com>
I was wondering the error handling of "After GET_CAPABILITY, the responder will know this is the version selected by the requester and always stick it it." After the version is negotiated (either from cache or set by GET_CAPABILITIES), If requester sends a command with a version other than the negotiated one, current responder seems to ignore the error and continue to process it with the previously negotiated version. Shouldn't the responder validate the version against the negotiated one and return error if it doesn't match? |
@rw8896 |
After GET_VERSION, the requester need decide which version is final selected and always use it.
After GET_CAPABILITY, the responder will know this is the version selected by the requester and always stick it it.
Current implementation just check all supported versions, which is too relax.
The text was updated successfully, but these errors were encountered: