User Datagram Protocol (UDP)

The User Datagram Protocol (UDP) is one of the core members of the core members of the Internet protocol suite. The protocol was designed by David P.Reed in 1980 and formally defined in RFC 768.

Introduction -
The User Datagram Protocol (UDP) according to RFC-768 is defined to make available a data-gram mode of packet-switched computer communication in the environment of an interconnected set of computer network. This protocol assumes that the Internet Protocol (IP) is used as the underlying protocol.
UDP provides a procedure for application programs to send messages to other programs with a minimum of protocol mechanism. The protocol is transaction oriented, and delivery and duplicated protection are not guaranteed. Application requiring ordered reliable delivery of streams of data should use the Transmission Control Protocol (TCP).

RFC768.pdf is down here, read it to learn more about UDP -
UDP Fields -
  • Source port
  • Destination port
  • Length
  • Checksum
  • Pseudo Header
Features of UDP -
  • It is Transaction Oriented, suitable for query response protocol, such as Domain Name system.
  • It provides Data-grams, suitable for modelling other protocols such as in IPTunneling, Network file system.
  • It is Simple, suitable for bootstrapping or other process such as DHCP.
  • It is Stateless, suitable  for very large number of clients such as in streaming media.
  • The lack of retransmission delays make it suitable for real time application asuch as voice over IP, online games.
  • It works well in Unidirectional Communication, suitable for broadcast information such as service discovery and shared information.
What UDP does ?

UDP's real task is-
  • to take data from higher-layer protocols.
  • place it in UDP messages.
  • then pass down to the internet protocol for transmissions.
The basic steps for transmission using USP are-
  • Higher-layer data transfer.
  • UDP messages encapsulation.
  • Transfer messages to IP.
What UDP does not ?

UDP does not -
  • Establish connections before sending data.
  • Provide acknowledgement to show that data was received.
  • Provide any guarantees that its messages will arrive.
  • Detect lost messages and retransmit them.
  • Ensure that data is received in the same order that they were sent.
  • Provide any mechanism to manage the flow of data between devices, or handle congestion.


Reference - Wikipedia and RFC768

****ATCAPH.com****

Comments

Popular posts from this blog

Artificial Intelligence

Smart Card

Biometrics