The growth of the internet has put a strain on the bandwidth and speed of networks. There are now more users than ever and the need for a more efficient form of data transfer is needed.
The absolute minimum number of packets required in a transaction is two, one request followed by one response. UDP [16] is the one protocol in the TCP/IP protocol stack that allows this, the problem here being the unreliability of the transmission. A protocol that has the efficiency of UDP but the reliability of TCP is needed.
T/TCP solves these problems to a large degree. It still has the reliability of TCP, and comes very close to realising the 2 packet exchange (three in fact). T/TCP uses the TCP state model for its timing and retransmission of data, but introduces a new concept to allow the reduction in packets.
Even though three packets are sent using T/TCP, the data is carried on the first two, thus allowing the applications to see the data with the same speed as UDP. The third packet is the acknowledgement to the server by the client that it has received the data, this is how the TCP reliability is incorporated.