public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 0/3] TCP timestamp hardening (update)
@ 2007-07-25 10:44 shemminger
  2007-07-25 10:44 ` [PATCH 1/3] TCP: congestion control API pass RTT in microseconds shemminger
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: shemminger @ 2007-07-25 10:44 UTC (permalink / raw)
  To: David Miller; +Cc: netdev

These patches deal with issues brought up by Gavin McCullagh
about reactions of Cubic and HTCP to hostile receivers that return
bogus timestamp options. If the receiver crafts a timestamp that is
larger than the original, then some of the congestion control algorithms
maybe come unfair.

The solution in these patches is to only use local values to measure
RTT for congestion control.  The timestamp is still used as described
in RFC's to measure RTT used for retransmit timer.

Thank you to Sangtae Ha for testing, these, see:
  http://netsrv.csc.ncsu.edu/net-2.6.22/stephen_lowres/
He also found some pre-existing problems with TCP-LP that might
be related to NAPI on the receiver.

This should go into 2.6.23. But not into the stable kernel
since the risk of causing regression is greater than the possible
risk exposure.

-- 


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-07-25 11:01 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-07-25 10:44 [PATCH 0/3] TCP timestamp hardening (update) shemminger
2007-07-25 10:44 ` [PATCH 1/3] TCP: congestion control API pass RTT in microseconds shemminger
2007-07-25 10:44 ` [PATCH 2/3] TCP: cubic - eliminate use of receive time stamp shemminger
2007-07-25 10:44 ` [PATCH 3/3] TCP: htcp - use measured rtt shemminger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox