When interfacing with low-power microcontrollers, secure enclaves, or hardware roots-of-trust, such as slow hardware TPMs, the responder may not be capable of rendering complex cryptographic structures within a standard timeout window. In these scenarios, the responder drops a ResponseNotReady error frame.
The requester needs an explicit, non-blocking asynchronous state machinery to handle back-off periods and subsequent RESPOND_IF_READY polls without blocking execution.
What to Add
- Error State Mapping: Intercept
ERROR responses checking for the ResponseNotReady error code.
- Timing Engine Interface: Parse the
RtnExponent and RtnRequestToPrepare parameters provided by the responder to compute required waiting intervals.
- Stateful Poll Generation: Provide an asynchronous status check loop allowing the application to fire
RESPOND_IF_READY frames only after the specified timeout boundary has elapsed.
When interfacing with low-power microcontrollers, secure enclaves, or hardware roots-of-trust, such as slow hardware TPMs, the responder may not be capable of rendering complex cryptographic structures within a standard timeout window. In these scenarios, the responder drops a
ResponseNotReadyerror frame.The requester needs an explicit, non-blocking asynchronous state machinery to handle back-off periods and subsequent
RESPOND_IF_READYpolls without blocking execution.What to Add
ERRORresponses checking for theResponseNotReadyerror code.RtnExponentandRtnRequestToPrepareparameters provided by the responder to compute required waiting intervals.RESPOND_IF_READYframes only after the specified timeout boundary has elapsed.