Generally speaking TCP is an endpoint protocol that runs over IP. Switches don't need to know anything about TCP to rout TCP traffic. Anyway, I was not talking about TCP, I was referring to the simplest way for a high bandwidth ISP to deal with oversubscribing their network without pissing people off. They don't need to know anything about the IP packets your sending be the UDP, TCP or whatever.
His suggestion is that people who use less bandwidth on average should have better bandwidth when things get congested, but your network is only effected by the last few seconds of traffic so letting people have all the bandwidth for new connections seems like a bad idea. (Comcast was doing something like this and it ended up messing with a lot of low bandwidth apps.)
PS: Networking equipment has internal buffers so they can buffer 20 and only 20 packets from each user / network and then round robbin transmission of those packets down the line. The advantage to this is if your sending a small stream of data your going to have low latency and if your trying to flood the pipe you and only you will get a high number of packets dropped.
His suggestion is that people who use less bandwidth on average should have better bandwidth when things get congested, but your network is only effected by the last few seconds of traffic so letting people have all the bandwidth for new connections seems like a bad idea. (Comcast was doing something like this and it ended up messing with a lot of low bandwidth apps.)
PS: Networking equipment has internal buffers so they can buffer 20 and only 20 packets from each user / network and then round robbin transmission of those packets down the line. The advantage to this is if your sending a small stream of data your going to have low latency and if your trying to flood the pipe you and only you will get a high number of packets dropped.