reply to justbits
Re: Well worth reading on why P2P causes problems
said by justbits:The QoS issue only applies to the first mile anyway, where the problem is. There is not bandwidth problem at the internet backbone level.
QOS/TOS flags are not a solution. Anybody can set those flags. Anybody can ignore those flags. QOS/TOS is only useful between you and your first hop onto the Internet, not between you and anybody else. Otherwise, everybody who is greedy would mark all of their packets as highest priority.
As well, QoS can easily be implemented in a way that prevents the "flags" issue you have mentioned.
The proposed change to TCP can result in fair-sharing of major Internet backbones as well as fair-sharing on your home Internet router. The big win with a fair-sharing TCP stack is that the major Internet backbones that carry GB/sec of traffic wont need to deploy excessive traffic shaping or deploy fake RST packets.Major backbone providers have not even thought about using traffic shaping or forged RST packets. There is not a bandwidth problem on the internet backbones, nor will there be for awhile as there is still a lot of available bandwidth and many options to alleviate any problems (turning up new wavelengths, etc.) This is a problem in last mile networks only.
And it seems to result in a huge increase in performance for lower-bandwidth single-connection users like VoIP and web surfing.There are VERY few single-session TCP applications left. VoIP is not one of them. And web surfing is not one either (any longer).
If you want to think of it another way, P2P protocols are NOT designed to be a "green" or environmentally friendly protocol.Then the problem is the P2P algorithm, NOT TCP. Fix the P2P algorithms, fix them problem. Mangle TCP, problem remains.