Vista's TCP/IP Promises and Perils

boyko.at.netqos tips us to a new writeup on Vista's TCP/IP stack, which is called Compound TCP/IP (CTCP). From the article: "...security policy will come from a centralized source. When you get your DHCP lease, your computer will report to the stack what OS you're using, what version level, what patches, what anti-virus software that's active — all that kind of stuff. It will have the ability to restrict your network access if you have a down-level machine... We could see a lot of our customers with much higher WAN network utilization because of this new TCP/IP stack... CTCP can be enabled/disabled from the command prompt but there has been no mention of tuning parameters which leads us to ask the question: How are you supposed to configure this setting in Vista?... What worries us... is that Microsoft is basing this on packet round trip time. The round-trip time from the client-side will have the server processing time in it; but the clients aren't likely going to be the running the CTCP at first. If you have a server-to-server backup running, for example, CTCP may think its part of the round-trip time and it'll throw the delay window through the roof..."

Comments

Re:What the load of misinformation

[LoudMusic]

I haven't read TFA, but based on blurb it will be horrible. You say that as if you expected something different from Slashdot.

Re:Why build it into the stack?

[coredog64]

The point is to avoid the hassles of 802.1n (i.e. tying MACs to ports based on a facilities diagram) and still reap some of the benefits of same.
Joe Contractor brings his Vista laptop in -- no A/V, no access. Jane Vendor brings her laptop in -- not up-to-date on patches, no access. All without
requiring those laptops to have some third party service installed/configured.