Both TCP (transmission control protocol) and UDP (user datagram protocol) are a part of the IP (Internet Protocol) suite of protocols. Both these protocols convert data into segments to enable exchange across networked computers. However, the two are very dissimilar in their details of operation; and hence have very different application.
In this exercise, you will learn more about TCP and UDP that work on top of Internet protocol and how they are used for different application layer protocols.
This exercise contains supporting materials for Cisco.
TCP and UDP
Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) are protocols that work on Layer 4 of the OSI reference model. There are different application layer protocols like HTTP, SMTP, FTP, etc. But how do they work , and what is the difference?
HTTP, SMTP, DNS, and similar application layer protocols use different Layer 4 protocols and different port numbers to communicate.
For example:
HTTP uses TCP - port 80
SMTP uses TCP - port 25
DNS uses UDP - port 53
TCP is a connection-oriented protocol. UDP is a connection-less protocol.
In TCP, before end hosts can send data to each other, a TCP connection needs to be established between them. This makes TCP a reliable protocol because every packet sent needs to be acknowledged. TCP guarantees packet delivery. Packets sent over a TCP connection are checked for errors before they are transmitted over the network.
UDP is a connection-less protocol. Hence it doesn’t acknowledge packets and does not guarantee packet delivery. Packets are not checked for errors before transmitting them over the network.
Applications that require high reliability, speed, and quick delivery of packets use TCP. Hence TCP is used for HTTP, SSH, FTP, Email, and many others.
UDP is used for applications that require a faster delivery and does not need to be checked for any errors. For example, voice, streaming video, DNS, and many others.
There are no screenshot items for this exercise.