← Back to the chapter · Next detail →
Technical detail · Network Traffic Analysis: Evidence Paths
Protocol receipt and application meaning
The under-the-hood skill is separating transport evidence from application meaning. Under MQTT Version 5.0, QoS 1 is at-least-once delivery and duplicates are possible. The sender does not retry PUBLISH on an established connection solely because PUBACK is missing; after reconnecting with a continuing session, it must retransmit unacknowledged QoS messages. PUBACK timing shows protocol acknowledgement along the broker path, but does not prove a human saw an alert. A CoAP ACK can prove message exchange at the protocol layer, but it does not prove a sensor value was physically correct. LoRaWAN frame counters and RSSI/SNR can show link behavior, but payload meaning still needs device, network-server, or application context. BLE supervision timeouts, Thread parent changes, Wi-Fi roaming, and cellular reconnects each leave different evidence trails, so the capture point must match the mechanism under review.