Difference between revisions of "User Datagram Protocol"
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) |
||
| Line 21: | Line 21: | ||
* [https://en.wikipedia.org/wiki/Client%E2%80%93server_model Client-server model]] | * [https://en.wikipedia.org/wiki/Client%E2%80%93server_model Client-server model]] | ||
| + | [[Category:Computer networks]] | ||
[[Category:Computing]] | [[Category:Computing]] | ||
| − | |||
[[Category:Internet]] | [[Category:Internet]] | ||
| + | [[Category:Telecommunications]] | ||
Latest revision as of 19:22, 30 June 2017
In electronic communication, the User Datagram Protocol (UDP) is one of the core members of the Internet protocol suite.
With UDP, computer applications can send messages, in this case referred to as datagrams, to other hosts on an Internet Protocol (IP) network. Prior communications are not required in order to set up transmission channels or data paths.
UDP uses a simple connectionless transmission model with a minimum of protocol mechanism. UDP provides checksums for data integrity, and port numbers for addressing different functions at the source and destination of the datagram. It has no handshaking dialogues, and thus exposes the user's program to any unreliability of the underlying network: there is no guarantee of delivery, ordering, or duplicate protection.
If error-correction facilities are needed at the network interface level, an application may use the Transmission Control Protocol (TCP) or Stream Control Transmission Protocol (SCTP) which are designed for this purpose.
UDP is suitable for purposes where error checking and correction are either not necessary or are performed in the application; UDP avoids the overhead of such processing at the level of the network interface. Time-sensitive applications often use UDP because dropping packets is preferable to waiting for delayed packets, which may not be an option in a real-time system.
The UDP protocol was designed by David P. Reed in 1980 and formally defined in RFC 768.
