3 ms·
For TLS, which runs on top of TCP, this is a non-issue, as TCP enforces complete, in-order delivery of the data. However: This document describes the Heart
by twic 13y ago
For TLS, which runs on top of TCP, this is a non-issue, as TCP enforces complete, in-order delivery of the data.
However:
This document describes the Heartbeat Extension for the Transport
Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
protocols [...] DTLS is designed to secure traffic running on top
of unreliable transport protocols.
The payload is necessary because this extension can be used with DTLS, which runs on top of UDP, which does not enforce complete or in-order delivery.
I wonder if the payload should have been specified only for use with DTLS, not TLS.
- tptacek 13y agoThe whole extension was originally specified only for DTLS. Then the working group started suggesting reasons that an app-layer liveness check would be useful in TLS. At some point, it became easier simply to add the feature in both places than to hash out the argument. That's how standards processes work: it's easier to say "yes" to a new feature than "no".