diff options
| author | Bhasker Hariharan <bhaskerh@google.com> | 2019-01-29 18:12:31 -0800 |
|---|---|---|
| committer | Shentubot <shentubot@google.com> | 2019-01-29 18:13:48 -0800 |
| commit | f03c7e48e71009a64c30b57648fd234710fd578a (patch) | |
| tree | 908bce875e9dd050d122c7c1eda9900ec359690b /tools/go_stateify | |
| parent | 53afa68988f84ac8df62b2df6463457c39c1e803 (diff) | |
Fix IsLost check to match the description in RFC6675.
quoting what "rscheff@gmx.at" pointed out over email.
"IsLost in RFC3517 is defined as >= (DupThresh * SMSS) while
RFC6675 improves upon this, and defines IsLost as >
((DupThresh - 1) * SMSS + 1).
The latter addresses situations where partial segments (size < MSS)
are sent (eg. last segment of a http protocol message sent with PSH
being less than MSS is common)."
PiperOrigin-RevId: 231512331
Change-Id: I1addd4a92e3e7baeb0bdda46463ebfae435da958
Diffstat (limited to 'tools/go_stateify')
0 files changed, 0 insertions, 0 deletions