Bug 798
Summary: | last timestamp value received (ts_recent) not updated properly; includes solution | ||
---|---|---|---|
Product: | Networking | Reporter: | Martin Duke (mduke26) |
Component: | IPV4 | Assignee: | Bugme Janitors Team (bugme-janitors) |
Status: | REJECTED INVALID | ||
Severity: | low | ||
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | from 2.4.18 through 2.5.70 | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Martin Duke
2003-06-10 16:47:16 UTC
Said draft is buggy and our behavior is correct. The TCP implementation community considers our behavior acceptable. There was a discussion about exactly this on the tcp-impl list some time ago, sorry I don't have a reference handy. In particular, said draft opens up a hole where anyone can break the connection on us. |