For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Tuning the TCP Profile: Part Three

Since February I've walked you through most of the TCP profile configuration page. This month I'll finish this tour. As I said previously, when I refer to "performance" below, I'm referring to the sp...
Published Mar 25, 2016
Version 1.0
application delivery
LTM
security
series-the-tcp-profile
tcp
Martin_Duke's avatar
Ret. Employee
I work in the Office of the CTO on both F5's standards engagement process in general, and specifically on the application of transport-layer innovation to F5's product line. F5 sponsors my service as Transport Area Director at the Internet Engineering Task Force (IETF), where I help to administer standards development worldwide.
View Profile
Martin_Duke's avatar
Ret. Employee
I work in the Office of the CTO on both F5's standards engagement process in general, and specifically on the application of transport-layer innovation to F5's product line. F5 sponsors my service as Transport Area Director at the Internet Engineering Task Force (IETF), where I help to administer standards development worldwide.
View Profile
riraccuia's avatar
riraccuia
Icon for Cirrus rankCirrus
Nov 08, 2016

Hi Martin,

 

this kb article states that "The Woodside algorithm relies on timestamps to determine transmission. If timestamps are not available in your network, avoid using Woodside.". In this article though, you mentioned that Woodside does not rely on timestamps for rtt estimation.

 

I am not sure what "determine transmission" really means in that sentence but is it really necessary for the server/client to actively set this option in the TCP packet so that Woodside can do its job correctly?