UDP/IP

UDP/IP
Name	UDP/IP
Type	Network protocol suite
Developer	Vint Cerf; Robert Kahn; Defense Advanced Research Projects Agency
First standard	RFC 768; RFC 791
Initial release	1980s
Os support	Unix; Windows NT; macOS; Linux
Ports	0–65535
Transport layer	User Datagram Protocol
Internet layer	Internet Protocol

UDP/IP

UDP/IP is a concise description of the combination of the User Datagram Protocol and the Internet Protocol as used in packet-switched networks. It provides a lightweight, connectionless transport over Internet Protocol, enabling low-latency datagram exchange between hosts defined in early work by Vint Cerf and Robert Kahn under the auspices of the Defense Advanced Research Projects Agency. The design contrasts with connection-oriented suites such as Transmission Control Protocol implementations standardized in RFC 793.

Overview

UDP/IP pairs a minimal transport protocol with the addressing and routing schemes of Internet Protocol. The layering follows the model articulated in DARPA-funded research and later mapped to the OSI model and standards bodies like the Internet Engineering Task Force. The protocol combination emphasizes simplicity and speed, which made it suitable for early packet networks such as the ARPANET and later commercial networks implemented by vendors like Cisco Systems and Juniper Networks.

Protocol Architecture

The architecture separates responsibilities: the internet-layer addressing and routing provided by Internet Protocol and the transport-layer datagram service provided by the User Datagram Protocol. Packet structures are defined in standards originating from the Request for Comments series, with header fields that interact with router implementations from companies such as Cisco Systems and research projects at institutions like MIT and Stanford University. Allocation of logical endpoints via port numbers follows assignments maintained by Internet Assigned Numbers Authority and operationalized by software stacks in FreeBSD and Windows NT.

Operation and Features

Operation relies on stateless datagram exchanges: a sender encapsulates application payloads in UDP headers that carry source and destination ports and a length field; those datagrams are then encapsulated in IP packets with source and destination addresses. Routers and switches from vendors like Cisco Systems forward IP packets based on Border Gateway Protocol and Open Shortest Path First information. Features include minimal overhead suited for real-time systems developed at labs like Bell Labs and applied in protocols standardized by the IETF such as the Session Initiation Protocol favored by projects from Nokia and Ericsson.

Use Cases and Applications

UDP/IP underpins many latency-sensitive applications: streaming media deployed by companies like Netflix and YouTube, voice over IP services offered by providers such as Vonage and Skype, and online gaming platforms from studios like Electronic Arts. It is foundational for DNS queries handled by entities like Cloudflare and Verisign, and for multicast delivery used in standards from International Telecommunication Union. Research deployments in distributed systems at Carnegie Mellon University and University of California, Berkeley used UDP/IP for experimental transport protocols and high-performance datagram services.

Implementation and Interoperability

Implementations exist across operating systems including Linux, Windows NT, macOS, and embedded stacks from companies such as ARM Holdings and Microchip Technology. Interoperability is assured by conformance to IETF RFCs implemented in network libraries like lwIP and libpcap tools used by projects at University of Illinois Urbana–Champaign. Network appliances from Juniper Networks and Cisco Systems must correctly process UDP-in-IP to interoperate with application servers hosted by cloud providers such as Amazon Web Services and Google Cloud Platform.

Security and Limitations

The lack of connection management and flow control exposes UDP/IP to spoofing and amplification attacks exploited in incidents investigated by organizations such as CERT Coordination Center and monitored by agencies like National Institute of Standards and Technology. Because it omits retransmission and congestion control present in Transmission Control Protocol, applications rely on libraries and protocols such as QUIC and DTLS from the IETF to provide security and reliability when needed. Network operators using middleboxes from vendors like F5 Networks must account for UDP behavior when designing mitigation strategies referenced in advisories from US-CERT.

Category:Internet protocols