Slashdot Mirror
UK ISP To Prioritize Gaming Traffic
nk497 writes "A UK ISP is now offering a broadband package just for gamers, which will prioritize their traffic to give them an edge over rival players. Demon Internet has also set up direct networks with gaming companies to boost speeds, and is promising lower latency and a higher usage cap than standard packages. 'Looking at the usage of gamers, it's actually more akin to a small business,' the company said. While paying to get specific content streamed more quickly may worry net neutrality campaigners, Demon says it has enough capacity for its own customers and that's who it's looking out for."
LOL wut? Net neutrality would prevent this, yes, but it would also prevent ISPs from holding you hostage for not paying up. I get that you're a Libertarian and it's all ZOMG gubment doin' stuff, but give me a break. The suggestion that what we have now works is as laughable as it is wrong. At bare minimum there needs to be rules to ensure that things are conducted in an above the board fashion.
Additionally, this is in a sense a method of cheating, you're putting down extra money to have an in game advantage, It doesn't take a genius to see that it puts pressure on other players to pony up for it as well, whether it would otherwise be necessary or not.
Prolly more like "Not intentionally slowing down"
Wherever You Go, There You Are
Let's create preferred lanes for Mercedes, Lexus and BMW drivers. After all, these people paid a lot more than Al Bundy for his Dodge and they pay more taxes as well. So it's entirely fair they get preferred treatment and lower driving latency (get to their destination faster). They're businessmen and women, so their needs are different from the normal people. We still have enough other roads for all the other drivers, don't worry.
If they had enough capacity on their network to avoid congestion, they wouldn't *need* to prioritise anything. This appears to be running a poor network, then charging more to compensate for it.
Shame, Demon used to be a decent ISP in the 90s.
Um, despite the "worry over net neutrality" cited in the article, the actual service just looks like they're repackaging a higher speed/business connection as a "gamer" package. Nothing there actually says that your connection will be slower by packet category.
Paying £3 to get something extra doesn't sound too bad. What worries me is that ISPs may quietly start crippling their default packages so they can sell "extras". For example, this ISP could artificially raise the latency of normal users' connections, and when anyone complains they might say "it's because we give priority to the more expensive packages -- if you want better latency you must also pay more". You might say "meh, that'll never happen"... But, this is exactly the sort of thing our ISPs are infamous for doing here in the UK.
Prioritizing based on source or destination would be a problem under Net Neutrality but prioritizing based on protocol etc isn't necessarily unless it's to try to degrade a competitors products(like a phone company which is also an ISP intentionally degrading VOIP).
NN doesn't stop you pushing VOIP packets through faster than FTP or UDP faster than TCP.
How do you figure that? You're assuming that the consequences of banning this would be harmful. There are two cases to consider here - one where the ISP is operating at 100% bandwidth, and another where they are operating below that.
If the ISP is operating at 100% bandwidth, then this becomes a zero-sum game. The gamer's packets being prioritized come at the price of other paying customers' packets being de-prioritized. In essence, the other customers are not getting the bandwidth they paid for. The ISP transmits the same number of packets, they collect the same amount of money from regular customers, and they collect more money from the gamers. In other words, the ISP does the exact same amount of work as before, but collects more money.
If the ISP is operating below 100% bandwidth, then the gamer gains nothing. His packets travel out with the same latency as regular customers' packets, so he gains nothing by paying extra. Again, the ISP does the exact same amount of work as before, but collects more money.
So in both cases, the harm comes from offering to prioritize gaming traffic for an extra fee. At its heart, that's what Net Neutrality aims to prevent - ISP using their monopoly position over your network data to extract more money from you while they do the exact same amount of work. Net neutrality encourages ISPs to solve bandwidth problems the correct way - by adding more bandwidth. Except for illegal traffic (spam, copyrighted downloading), prioritization encourages ISPs to solve bandwidth problems the wrong way - by not adding more bandwidth when they obviously need it, and taking bandwidth some customers have legitimately paid for and should get, and giving it to someone else who paid more.
Now, if ISPs wanted to lower prices for people willing to have their bandwidth degraded, while raising prices for people wanting to have their bandwidth prioritized, thus keeping their revenue the same, then there's no problem. But no ISP is going to do that because it involves them doing a whole lot of work implementing all this for no net revenue gain. The whole reason prioritization (of legal traffic) makes economic sense to ISPs is because it's essentially robbing from Peter to pay Paul, without Peter knowing that he's being robbed, and Paul is willing to pay extra for the service.
Prioritizing based on source or destination would be a problem under Net Neutrality but prioritizing based on protocol etc isn't necessarily
Since most games run their own protocol, it's effectively the same. So the WoW protocol gets prioritized and the Age of Conan protocol does not, it works out to exactly the same as a src/dst filter.
Live today, because you never know what tomorrow brings
It's not as simple as whether the ISP is running at 100% or not (i.e. your packet will get through, or not). Some apps are very sensitive to latency (voice, gaming, etc) while most are not.
The switches have buffering which gets emptier, fuller, emptier, fuller. When it runs out of buffering, i.e. your 100% situation, packets get dropped, and TCP "backs off" to try to avoid that happening again in the immediate future. In fact, Random Early Discard (RED) protocols will drop the odd random packet, with increasing probability as the buffer fills, to let TCP know to backoff.... before LOTS of packets start getting dropped. If you do get to 100%, it shouldn't last long.
However when your time sensitive packets are in the same queue as it gets emptier, fuller, emptier, fuller, then even if the buffers never fill, you still suffer from increased latency... and also latency variation (jitter), which can be even more problematic (when do you decide the packets never coming and you need to fill in the gap?). Furthermore, you'd like to avoid dropping these time-sensitive packets with RED (which of course would be another "non neutral behavior"). That's because these kinds of apps generally send a steady stream, they will sorely miss the data in that dropped packet, and anyway they won't backoff in the face of drops, defeating the whole purpose of RED.
Enterprises who use IP Telephony will usually put that traffic at a higher priority (and, for that priority, disable RED). Not because their gigabit LANs are at 100%... they do it because it makes the telephone calls almost as robust and low-latency as "fixed lines".
The whole Net Neutrality debate would perhaps get somewhere if people agreed on what they were talking about. There's too many very different ideas bundled into the same name. The version that makes it illegal to willfully delay/block/etc will get 90% support. The version where it's illegal to prioritize ANYTHING is much more debatable. Those who have actually rolled out services over shared medium (IP telephony, video conferencing, etc) will have a lot of information to share on the latter.
Simply throwing bandwidth at the problem is not (yet) a viable solution, since folks are still figuring out ways to use all the bandwidth they can get. It's like saying "I don't need background threads and foreground threads, just treat them all the same and make the CPUs faster". Sounds nice, in theory.
Think of a service like Skype. Assume we want that kind of innovative service to prosper. This absolutely requires that service providers don't block/delay Skype packets. Meanwhile, to hit the quality and reliability of "fixed lines", some way to mark that small number of packets as "important" would help A LOT.
-netchipguy
It's an issue anywhere there is congestion. Which happens anywhere people don't like wasting money.
Buffering versus line utilization is an interesting relationship. You NEED buffering if you want to keep the line highly utilized because data comes in randomly from various places -- if you have small buffers, then the various TCPs will often collide, drop, and backoff even though the line isn't highly utilized. The "right" amount of buffering is a function of how much you want to pay, the utilization you want to achieve, the latency you are willing tolerate, and, assuming an adaptive protocol like TCP, the round trip time of from one endstation to the other (not just on your segment).
In the core, the lines are fast, but also very expensive. Providers want those things well utilized -- a 10Gb pipe which is only running at 20% isn't earning enough money. So the core tends to have deep buffering, lots of simultaneous flows, and hence runs at high utilization. It's not uncommon to have buffers on the order of several megabytes per port (providers often will measure it "milliseconds").
In a LAN, gigabit lines run everywhere, and the wires are short and cheap. They tend to be cheap switches, with shallow buffers. No one cares too much if packets are dropped, there is plenty of bandwidth to resend things. It's not uncommon to have 2-4 megabytes shared for the whole switch (24 ports or whatever).
In the first case, prioritizing helps avoid large latencies, since the core has deep buffers, and enough users to keep the buffers busy.
In the second case, prioritizing helps avoid packet drops, since the LAN has shallow buffers.
-netchipguy