TCP WS option.

I am trying to understand TCP WS option and i have the following
question:

1. How can a receiver advertise less the 2^14 bits window when TCP WS
option is used.
Assume a HOST A advertises WS factor of 14 in its syn packet and hand
shake is complete. During the process of receiving data sent from the
peer, HOST A now has window less than 2^14 bits. While sending ACK,
before putting the window value in the TCP header, HOST A will do the
right shift window value by 14 bits and the resulting value will be
assigened to header field. By right shifting 14bits effective window
value will be zero, since window itself is less than 2^14 bits.

Is my understing correct ? if yes, will cause any problem?

Thanks,

<maheshmylar@gmail.com> wrote in message
news:31e24826-c1a1-4c61-acaf-aaea5911348d@d4g2000prg.googlegroups.com...[color=blue]
>I am trying to understand TCP WS option and i have the following
> question:
>
> 1. How can a receiver advertise less the 2^14 bits window when TCP WS
> option is used.
> Assume a HOST A advertises WS factor of 14 in its syn packet and hand
> shake is complete. During the process of receiving data sent from the
> peer, HOST A now has window less than 2^14 bits. While sending ACK,
> before putting the window value in the TCP header, HOST A will do the
> right shift window value by 14 bits and the resulting value will be
> assigened to header field. By right shifting 14bits effective window
> value will be zero, since window itself is less than 2^14 bits.
>
> Is my understing correct ? if yes, will cause any problem?
>
> Thanks,[/color]

This might help :
[url]http://hyperthink.net/blog/PermaLink,guid,8519a1bf-e1b7-4b9b-b10c-fce8d359b83e.aspx[/url]

[color=blue][color=green]
>> 1. How can a receiver advertise less the 2^14 bits window when TCP WS
>> option is used.
>> Assume a HOST A advertises WS factor of 14 in its syn packet and hand
>> shake is complete. During the process of receiving data sent from the
>> peer, HOST A now has window less than 2^14 bits. While sending ACK,
>> before putting the window value in the TCP header, HOST A will do the
>> right shift window value by 14 bits and the resulting value will be
>> assigened to header field. By right shifting 14bits effective window
>> value will be zero, since window itself is less than 2^14 bits.[/color][/color]

If the advertized window is 1000, and the WS factor is 14,
then the advertizing window is 1000*2^14 or 16384000000

You "lose" the ability to precisely specify small windows. Or rather
the system rounds up to the nearest 2^14 value:
Advertized window Real Window
0 0
1 16384
2 32768
1000 16384000000
etc.


--
Posted via a free Usenet account from [url]http://www.teranews.com[/url]

"eager" <eager@beaver.it> wrote in message
news:mtrfj.2425$EA5.1952@pd7urf2no...[color=blue]
>
>
> This might help :
>[/color]
[url]http://hyperthink.net/blog/PermaLink,guid,8519a1bf-e1b7-4b9b-b10c-fce8d359b83e.aspx[/url][color=blue]
>
>[/color]

Maybe a bit too "eager"? Your link seems unrelated to the question of
window scaling.

"Michael K. O'Neill" <mikeathon2000@nospam.hotmail.com> wrote in message
news:jcCfj.82345$Um6.879@newssvr12.news.prodigy.net...[color=blue]
>
> "eager" <eager@beaver.it> wrote in message
> news:mtrfj.2425$EA5.1952@pd7urf2no...[color=green]
>>
>>
>> This might help :
>>[/color]
> [url]http://hyperthink.net/blog/PermaLink,guid,8519a1bf-e1b7-4b9b-b10c-fce8d359b83e.aspx[/url][color=green]
>>
>>[/color]
>
> Maybe a bit too "eager"? Your link seems unrelated to the question of
> window scaling.
>
>[/color]

WS is widely known as web services...

"eager" <eager@beaver.it> writes:
[color=blue]
> WS is widely known as web services...[/color]

But when the OP first said

"I am trying to understand TCP WS option"

And then talks about windows, then "web services" makes no sense in
this content.

--
Posted via a free Usenet account from [url]http://www.teranews.com[/url]

"Bruce Barnett" <spamhater133+U080106200308@grymoire.com> wrote in message
news:yek3atafnuo.fsf@mail.grymoire.com...[color=blue]
> "eager" <eager@beaver.it> writes:
>[color=green]
>> WS is widely known as web services...[/color]
>
> But when the OP first said
>
> "I am trying to understand TCP WS option"
>
> And then talks about windows, then "web services" makes no sense in
> this content.
>
> --
> Posted via a free Usenet account from [url]http://www.teranews.com[/url]
>[/color]

agreed

Bruce Barnett <spamhater133+U080104145611@grymoire.com> writes:
[color=blue]
> If the advertized window is 1000, and the WS factor is 14,
> then the advertizing window is 1000*2^14 or 16384000000[/color]

Oops. I meant 1000*2^14 or 16384000

In further discussion with Manesh, we discussed the case when the
window scale was set to 14, and the application's buffer was set to
8K.

Now this could be a configuration error, or it might happen if the
system default is WS=14, but an application, unaware of RFC1323,
specifically sets the buffer to 8K - which is common in old programs.

It is therefore theoretically possible that the application can never
advertise available memory, because the smallest amount it can
advertise is 16K. It would be "stalled."

It seems to me that the OS should check for this condition, and only
set a window scale factor that matches the buffer allocated. In other
words, only use the window scale feature if the buffer is > 64K.

If the buffer is 1GB, then set the window scale to 14.
512MB, then WS=13,
128K, WS=2, etc.

This makes sense. But I'm not sure what real world implementations do.
Does anyone know if this is the typical approach?

--
Posted via a free Usenet account from [url]http://www.teranews.com[/url]

In article <yekk5mkwbxu.fsf@mail.grymoire.com>,
Bruce Barnett <spamhater133+U080108103230@grymoire.com> wrote:
[color=blue]
> It seems to me that the OS should check for this condition, and only
> set a window scale factor that matches the buffer allocated. In other
> words, only use the window scale feature if the buffer is > 64K.
>
> If the buffer is 1GB, then set the window scale to 14.
> 512MB, then WS=13,
> 128K, WS=2, etc.
>
> This makes sense. But I'm not sure what real world implementations do.
> Does anyone know if this is the typical approach?[/color]

I think it is. Basically, WS is generally only used to the extent it's
needed.

The other thing I think some systems do is round up the actual buffer
space allocated from what the application requests. I.e. if the
application asks for an 8KB buffer, it's actually saying "I need AT
LEAST 8KB". If the OS/stack designer feels they can afford it, they can
make the buffer bigger, and then use an appropriate WS factor.

--
Barry Margolin, [email]barmar@alum.mit.edu[/email]
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***