UDP is described in RFC 768 and is seen as a protocol which delivers data on best effort. This means that it cannot be regarded as reliable. Each delivery of data will not seek an acknowledgement from the destination device. It neither offers flow control. Features of UDP includes Unreliable Delivery – The reason it is called a protocol of best effort delivery is because UDP does not provide the mechanism for guarantee that destination device will receive the data from the source device. It is therefore referred to as unreliable. This however does not mean that the data delivered to the destination device will not be meaningful. Small segments of data may be lost or corrupt but since UDP is used mainly by applications such Voice over IP(VoIP), video streaming etc, this will only present itself as a little glitch or something of that sort. Connectionless – There is no need for the establishment of connection for UDP between hosts before data can be sent and received. No sequencing – There may be times when data is received in a different order than it was sent. UDP lacks provision for any mechanism to reassemble the data to its original sequence. Data is simply delivered to the application in the order of arrival. No Flow Control – Unlike TCP, there are no mechanisms within UDP for regulating the amount of data the source transmits to avoid a bottle neck at the destination device. When the source device sends the data and the resources on the destination host is overburdened, it is most likely that the destination device will simply drop the data and will continue to drop data until the bottle neck is cleared. ![]() No acknowledgements
Speed One of the most important requirements for delivering live video and voice over the network is speed. UDP is a fast protocol. Video and voice applications need a fast protocol, can tolerate little segments of missing or corrupt data but cannot tolerate being slow. Stateless UDP is a stateless protocol. It follows therefore that neither the client nor the server keeps track of the state of the communication session. Reference https://www.pluralsight.com/content/dam/pluralsight/resources/blog/2007/10/networking-basics-tcp-udp-tcpip-osi-models/wp/img/TCP7.jpg https://www.evl.uic.edu/cavern/RBUDP/Reliable%20Blast%20UDP_files/droppedImage.png |
CategoriesAuthor I have a passion for networking and use this medium for tutorials in Networking Archives
April 2017
Categories |