RFC 768

RFC 768
Title	RFC 768
Subject	User Datagram Protocol
Author	Jon Postel
Published	1980
Status	Standard
Series	RFC

RFC 768

RFC 768 defines the User Datagram Protocol (UDP), a core protocol for packet-switched internetworking that provides a minimal, connectionless transport service. The memo specifies packet structure, port semantics, checksum behavior, and intended use cases for low-overhead datagram delivery. It influenced subsequent Internet architecture, protocol design, and implementations across operating systems and network equipment.

Introduction

RFC 768 was authored during the period of rapid development of the Internet Protocol Suite and is associated with influential figures and institutions such as Jon Postel, DARPA, University of Southern California, Information Sciences Institute, and IETF precursor activities. It complements contemporaneous specifications like RFC 791 and relates to projects and organizations including ARPANET, Stanford University, MIT, Berkeley Software Distribution, and Xerox PARC. The document addresses transport-layer needs in environments ranging from early packet radio research exemplified by DARPA Packet Radio Project to campus networks maintained by Carnegie Mellon University and University of California, Los Angeles. RFC 768's minimalism reflects design philosophies seen in work by Vint Cerf, Bob Kahn, and other early Internet pioneers.

Protocol Specification

The protocol described provides a connectionless, unreliable datagram service operating atop Internet Protocol as specified in RFC 791 implementations found in stacks for BSD Unix, Microsoft Windows NT, Solaris (operating system), and FreeBSD. It uses port numbers influenced by assignment practices later managed by IANA and interoperates with applications and services such as Domain Name System, Simple Network Management Protocol, Bootstrap Protocol, and multimedia tools developed at institutions like Bell Labs and MPEG. The specification contrasts with virtual-circuit and stream-oriented services exemplified by Transmission Control Protocol and influenced the design of lightweight transports used in projects at CERN and X Window System deployments.

Header Format and Checksums

The RFC defines a small header containing source and destination port fields, a length field, and a checksum. Implementations across stacks from IBM mainframes to embedded systems produced by Cisco Systems and Juniper Networks honored the header layout when integrating with Ethernet (IEEE 802.3), PPP, and wireless links from Qualcomm and IEEE 802.11. Checksum semantics relate to works on error detection such as the Internet checksum and research by figures associated with MIT Lincoln Laboratory and Bell Labs. The header size and alignment considerations affected protocol handlers in Linux kernel networking subsystems and influenced packet capture tools like tcpdump and Wireshark.

Implementation and Usage

Adoption of the specified protocol occurred across academic, commercial, and governmental networks including NSFNET, Cisco, Sun Microsystems, AT&T, and research at SRI International. Use cases span real-time media and control channels exemplified by applications like RTP, VoIP initiatives, multiplayer gaming engines by companies such as id Software, and lightweight name resolution utilities in BIND deployments. Library and API exposure occurred through interfaces in Berkeley sockets, language runtimes such as Java (programming language), Python (programming language), and middleware stacks used in CORBA experiments. Device vendors in the Internet of Things era integrated the protocol into firmware developed by firms like ARM Holdings and STMicroelectronics.

Security and Limitations

The memo's minimal guarantees highlighted security and reliability trade-offs examined in studies by CERT Coordination Center, NSA, and academic groups at Stanford University and University of California, Berkeley. Limitations—absence of congestion control, sequence integrity, and authentication—led to misuse patterns exploited in incidents investigated by SANS Institute and mitigations proposed in protocols such as IPsec and Transport Layer Security. The protocol's behavior contributed to reflection attacks and amplification vectors analyzed in reports by FBI cyber units and security research from Google Project Zero and ACM SIGCOMM papers. Responses included deployment of rate-limiting in Cisco IOS and filtering guidance from NIST.

Historical Context and Impact

RFC 768 is situated among foundational documents like RFC 791 and later standards produced under the aegis of IETF working groups including IETF Transport Area efforts. Its influence extends to protocol engineering practices at Google LLC, Facebook (Meta Platforms), and content-delivery research from Akamai Technologies. The document shaped curriculum in courses at Massachusetts Institute of Technology, Stanford University, and Carnegie Mellon University and appears in canonical texts authored by figures such as Andrew S. Tanenbaum and W. Richard Stevens. Its legacy persists in modern networking research at institutions such as ETH Zurich and University College London and in commercial deployments by Amazon Web Services and Microsoft Azure.

Category:Internet protocols