← Back to the chapter · Previous detail · Next detail →
Technical detail · CoAP Security: Protection and Application Fit
Assumptions and omissions in protection cost models
Illustrative CoAP protection cost models estimate transmission work from selected byte counts rather than measurements of a complete device.
18.8 Putting Numbers to It
For a transmit-charge arithmetic exercise, 53-byte and 20-byte transmitted units at 250 kbps take 1.696 ms and 0.640 ms. At 20 mA, their transmit charges are 0.00942 µAh and 0.00356 µAh. The ratio is 2.65 under those assumptions. This is not a measured Datagram Transport Layer Security (DTLS) penalty or a device lifetime estimate.
A handshake explorer, which estimates the initial exchanges that establish transport protection, uses assumed byte counts and fixed round trips. Loss, retransmissions, certificate size, receive current, processing, and DTLS version can change the result. Its display labelled energy covers client transmit charge only; charge and energy are different quantities.
Three other illustrative models have explicit limitations: the battery estimator mislabels a conversion from joules and volts, the protocol comparison omits fields and transport costs, and the block-size model omits parts of the full packet. Measure protected record sizes and device charge, account for usable cell capacity, and verify packet fit before making deployment decisions.