Hi Kumar,
If Scaling is in effect on both ends with the stack having the option
enabled, then it will work as you explained. If one of the host doesn't
support supports window scaling, it will not be enabled in either direction.
The window scaling option issent only once during a connection by each
host, mostly in the SYN packet. The window size can be dynamically adjusted
but the scale factor remains static for the duration of the TCP connection.
If you are looking for a manual setting, the best way to calculate an ideal
window size is to do [BW in bps x RTT in secs] which gives the total bytes
that can be transmitted per sec Then you can find the window size and the
scale factor with a little math.
Best Regards,
Tharak Abraham Luke
On Mon, Jun 16, 2014 at 8:19 PM, kumar yes <2014ccie_at_gmail.com> wrote:
> Hello Experts,
>
>
> I read about tcp window scaling factor and how that influence overall tcp
> flow
> What I understood is,
>
> Let's say the client send a sync with window size of 64323 bytes and
> window scale factor 3 (multiple of 8 =2^3)
> So the server will send first 64323 bytes and start sending second
> 64323bytes without waiting for an ack, same thing for 3rd and so
> on ...until 8th. If the sender receive an ack in btw for 1st 64323 then the
> sender will shift the factor to the left and keep sending the traffic.
>
> Example: sender sent 2x64323 and left with 6 remaining but the sender
> receive an ack for first 64323 and sender now has 7 remaining.
>
> Please let me know if my understanding is correct. Thanks and appreciate
> your response.
>
> Regards,
> Kumar
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Fri Jun 20 2014 - 17:33:32 ART
This archive was generated by hypermail 2.2.0 : Tue Jul 01 2014 - 06:32:36 ART