Game Developers Note Net Neutrality Concerns To FCC

eldavojohn writes "A list of notes from game developers (PDF) was sent in a letter to the FCC which represented a net neutrality discussion between the developers and FCC representatives. Game Politics sums it up nicely, but the surprise is that developers are concerned with latency, not bandwidth, unlike the members of many other net neutrality discussions. One concern is that each and every game developer will need to negotiate with each and every ISP to ensure their traffic achieves acceptable levels of latency for users. 'Mr. Dyl of Turbine stated that ISPs sometimes block traffic from online gaming providers, for reasons that are not clear, but they do not necessarily continue those blocks if they are contacted. He recalled Turbine having to call ISPs that had detected the high UDP traffic from Turbine, and had apparently decided to block the traffic and wait to see who complained.' It seems a lot of the net neutrality discussions have only worried about one part of the problem — Netflix, YouTube and P2P — while an equally important source of concern went unnoticed: latency in online games."

Comments

Not any surprise

[enriquevagu]

the surprise is that developers are concerned with latency, not bandwidth, unlike the members of many other net neutrality discussions

Actually, this is no surprise at all. Maybe most people only focus on the raw speed - i.e., throughput. However, for many applications, the latency - and the lack of sudden latency variations - is more important. These apps are called "inelastic", because they don't tolerate changes in the latency. For example: In a real-time VoIP application, sudden changes in latency make delayed packets useless and the voice gets cut. Yep, you can use a buffer, but that will add an anoying delay in your conversation, so in general the application is highly sensitive to latency changes.

The same happens with games. If you are playing against sb else, your latency can determine if you live or die. AND, the main problem is that the only solution comes from QoS mechanisms that tag, segregate and priorize different flows of traffic. What, I believe, is somehow against net neutrality.