← Back to the chapter · Previous detail
Technical detail · CoAP Security: CON and NON Trade-Offs
What the save/restore sketches do not establish
The reference sketches concern a sleeping CoAP sensor whose first protected send depends on valid keys, sequence state and peer acceptance. Their placeholder code needs implementation evidence before it can establish safe wake behavior.
Retaining a live DTLS association differs from session resumption, which negotiates renewed use of earlier session information. The save/restore sketch on the reference page demonstrates neither a supported serialization format nor a resumed handshake. A fixed retained-memory buffer proves neither complete state retention nor peer acceptance.
The C++ fragments on that reference page have unspecified application programming interfaces (APIs). Their energy, handshake-size and battery-life comments are unverified. A fresh-establishment sketch must wait for successful establishment before sending; placeholder calls do not prove asynchronous completion. Measure the complete encoded exchange, including applicable acknowledgements and application response evidence, instead of relying on a fixed security byte allowance.