Currently, the requester is strictly pull-based. SPDM 1.3 introduces an asynchronous notification model using Event Subscriptions. This allows a requester to register interest in specific telemetry alerts, component failures, or physical tamper events happening on the responder side.
Adding an event management mechanism will make this library capable of driving reactive security controls in embedded systems.
What to Add
- Event Negotiation: Add support for the
EVENT_CAP flag during capabilities exchange.
- Subscription Commands: Implement
GET_SUPPORTED_EVENT_TYPES and SUBSCRIBE_EVENT_TYPE serialization logic.
- Encapsulated Processing: Implement handling for incoming encapsulated
SEND_EVENT messages coming from the transport layer, exposing an event handler callback mechanism to the top-level application.
Currently, the requester is strictly pull-based. SPDM 1.3 introduces an asynchronous notification model using Event Subscriptions. This allows a requester to register interest in specific telemetry alerts, component failures, or physical tamper events happening on the responder side.
Adding an event management mechanism will make this library capable of driving reactive security controls in embedded systems.
What to Add
EVENT_CAPflag during capabilities exchange.GET_SUPPORTED_EVENT_TYPESandSUBSCRIBE_EVENT_TYPEserialization logic.SEND_EVENTmessages coming from the transport layer, exposing an event handler callback mechanism to the top-level application.