-
Notifications
You must be signed in to change notification settings - Fork 44
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
Questions about SPDM message read/write between requester and responder #244
Comments
SPDM-EMU implements a mechanism to send message via socket, not MCTP. MCTP or DOE is just treated as payload in the TCP socket message. |
(Please correct me if I am wrong :)) If I want to encode the SPDM messages into complete MCTP packets, do I need to construct it by myself? |
yes, you are right. In current implementation, we just add MCTP message header. There is no MCTP transport header. The purpose of the SPDM-EMU is to test SPDM, not MCTP. Feel free to proposal a patch to add MCTP transport header, if you see there is such need. |
Hi Yao, |
No. I don't know. |
I am trying to understand how requester send SPDM message over MCTP to responder through using wireshark to capture the tcp packets between requester and responder.
And I found that the captured packets seem mismatched from the SPDM message format and MCTP message format.
Is
SOCKET_SPDM_COMMAND_NORMAL
necessary for SPDM request/respond?Why the write function would split the request into four packets?
Why the mctp header information is not included in the packet payload?
spdm-emu/spdm_emu/spdm_emu_common/command.c
Lines 258 to 315 in c8ac4ca
The text was updated successfully, but these errors were encountered: