designs/mctp/mctp-kernel.md

9 providing a sockets-based API for MCTP communication within an OpenBMC-based
38   mapping of the sockets API to MCTP usage
88 ## Sockets API
99 MCTP sockets are created with the `socket()` syscall, specifying `AF_MCTP` as
109 MCTP Sockets opened with a protocol value of 0 will communicate directly at the
159 existing sockets APIs.
163 Sockets that receive incoming request packets will bind to a local address,
208 Sockets may specify a socket's remote address with the `connect()` syscall:
318 Sockets will only receive responses to requests they have sent (with TO=1) and
356 Like the send calls, sockets will only receive responses to requests they have
371 The following socket options are defined for MCTP sockets:
410 non-connected sockets when transferring messages to multiple different
412 messages, and the `smctp_addr` destination for those sockets may vary across
437 not used in `SOCK_DGRAM`-type sockets:
873 model of the message type; sockets are bound to an incoming message type,
874 similar to the IP protocol's model of binding UDP sockets to a local port
909 - needlessly consumes a tag on non-tag-owning sockets (ie, those which send with
912 - limits us to 8 sockets per network.
916 An alternative would be to completely dissociate tag allocation from sockets;
928 - forward all incoming messages of a specific message-type to all sockets