TCP induced packet loss over UDP and bachelor thesis references

Question

I'm currently writing a bachelors thesis in computer science and engineering, we're creating a racing game in C++ using OpenGL. In the report, I'm comparing use of TCP and UDP and I found a source, that claimed that multiple TCP-connections can induce packet loss in a UDP-connection. I even got a good reference

The problem lies in the fact that it's 13 years old but I haven't been able to find any indication that either protocol has modified to fix this problem. I've also been unable to find any paper or article, that are more current, that do similar investigations

So, my questions are whether there has been any changes to the protocols that might be relevant and/or if I should just forget about using this old reference in the thesis report.

Answer 1

Read the significant points in the article:

1. First, we focused on the case in which only TCP connections use all of the bandwidth of the network.
2. With the increase in the number of TCP connections, a larger number of packets can simultaneously arrive at the node, thereby making the buffer severely congested and thus making packet loss occur more often.

So the WAN link under test is saturated and the testing is for fairness of the TCP and UDP protocols. The 29 West article linked in the comments also notes:

Myth--There is no loss in networks that are operating properly.

Reality--The normal operation of TCP congestion control may cause loss due to queue overflow. See this report for more information. Loss rates of several percent were common under heavy congestion.

None of this is particularly new or should be surprising to anyone. Consider a home Internet connection, DSL or Cable with minimal speed, e.g. 2mb/s and setup one computer with Bittorrent downloading several large files, now try to run a UDP game such as Valve's Team Fortress 2. It's not going to work well.

With VoIP many networking persons started looking at methods to improve this situation which brings QoS to the table. QoS however demands co-operation both ends of the WAN and so this is of no benefit to the majority of end users. The only real solution is bandwidth throttling. If you have a 2mb link you set the TCP traffic to say 1.5mb and leave the remainder for UDP traffic for gaming.

If you are developing a split protocol game you would define a upper bandwidth limit, say 25KB/s per client for the total traffic and then define separate limits for TCP and UDP traffic within that limit, e.g. 15KB/s for TCP and 10KB/s for UDP. Generally games tend to use HTTP (TCP) for downloading game content outside of the game and then switch to UDP inside the game to remove the issue completely.