> From a networking perspective most Internet providers are generally not very happy with BitTorrent users. > These users place a heavy load on the network and can reduce the performance experienced by other subscribers. In addition, the huge amount of data transferred outside the ISPs’ own networks is also very costly. This could be re-stated with "BitTorrent" replaced with "video" and would still have the same mean…
I believe the issue is with the distribution of bandwidth between many TCP connections. The problem is that each TCP connection is treated with equal priority, meaning that a web page loading through a single TCP connection competes on equal footing with each of your 100 BitTorrent TCP connections, all running at a relatively low speed per connection. If this activity saturates your Internet connection, and you then…
My ISP for example seems to classify traffic and prioritise based that (HTTP(s) ports get more bandwidth than others up to the first couple of MB, BitTorrent goes in a low-priority group, etc). Yet I can still eat up all the bandwidth I want by just using multiple connections.
I would think it would be even easier to do this on the customer-IP level? Average over some time span, and customers who haven't used their fair allotment of the bandwidth for that time period get priority over others, and the guy with 2000 bittorrent connections has the same claim to the bandwidth as grandma loading her online banking in the browser through one TCP stream.
Are there some issues I'm missing that make this harder than it seems?