Licenciado En Logistica

Conclusion

T/TCP was originally designed to address the need for a more efficient protocol for transaction style applications. The original protocols defined in the TCP/IP reference model wereeither too verbose or not reliable enough.

T/TCP works by building on the TCP protocol and introducing a number of new options that allow the 3-Way Handshake to be bypassed in certain situations. Whenthis occurs, the transaction can almost realise the minimum number of segments that are required for a data transfer. T/TCP can reduce the average number of segments involved in a transaction from 9(TCP) to 3 using the TAO test. This has potential benefits to overloaded networks where there is a need to introduce a more efficient protocol.

Analysis of T/TCP shows that it benefits smalltransaction-oriented transfers more than large scale information transfer. Aspects of transactions can be seen in such cases as the World Wide Web, Remote Procedure Calls and DNS. These applications canbenefit from the use of T/TCP in efficiency and speed. T/TCP reduces on average both the number of segments involved in a transaction and the time taken.

As T/TCP is still an experimental protocol,there are problems that need to be addressed. Security problems encountered include the vulnerability to SYN flood attacks and rlogin authentication bypassing. Operational problems include thepossibility of duplicate transactions occurring. Problems that occur less frequently would be the wrapping of the CC values on high speed connections and thus opening up a destination host to acceptingsegments on the wrong connection.

Many people recognise the need for a protocol that favours transaction style processing and are willing to accept T/TCP as the answer. The security considerations lead tothe conclusion that T/TCP would be more useful in a controlled environment, one where there is little danger from a would-be attacker who can exploit the weaknesses of the standard. Examples of...