RFC 793

RFC 793
Title	Transmission Control Protocol
Number	793
Author	Jon Postel
Organization	Internet Engineering Task Force
Published	September 1981
Status	Standard

RFC 793

RFC 793 is the seminal specification that formalized the Transmission Control Protocol (TCP) as the transport-layer connection-oriented protocol used across the early and modern Internet. It was published in 1981 by the same community that produced the foundational ARPANET and influenced subsequent work by the Internet Engineering Task Force and the Internet Architecture Board. The document codified connection establishment, reliable byte-stream delivery, flow control, and connection teardown mechanisms that underpin implementations in operating systems like BSD Unix, SunOS, and later Linux kernel networking stacks.

Background and Publication

RFC 793 emerged from research and operational experience within institutions such as the Defense Advanced Research Projects Agency, University of California, Los Angeles, and the Stanford University research groups that participated in early packet network experimentation. The specification consolidated designs that had evolved from RFCs authored by figures including Vint Cerf, Bob Kahn, and Jon Postel, reflecting discussion at venues like the Internet Engineering Task Force workshops and technical reports from BBN Technologies. Publication coincided with contemporaneous standards work by the International Organization for Standardization and the European Computer Manufacturers Association, situating TCP within both academic networks and commercial data communications environments overseen by organizations such as Bell Labs and Xerox PARC.

Technical Summary

RFC 793 defines a connection-oriented, reliable, ordered byte-stream service implemented atop the Internet Protocol specified in related RFCs produced by contributors at UCLA and SRI International. Core mechanisms include the three-way handshake for connection establishment, cumulative acknowledgments, retransmission on timeout, and sliding-window flow control. The header fields described—Sequence Number, Acknowledgment Number, Data Offset, Flags (SYN, ACK, FIN, RST), Window, Checksum, Urgent Pointer—were designed to interoperate with IP fragmentation models implemented by Cisco Systems routers and network interfaces used in DEC and Intel hardware. The specification also prescribes connection states, timer behavior for retransmission and keepalive, and options negotiation for Maximum Segment Size, reflecting operational requirements observed in deployments at MIT and RAND Corporation networks.

Protocol Architecture and State Machine

RFC 793 codifies a finite state machine for endpoints with states such as LISTEN, SYN-SENT, SYN-RECEIVED, ESTABLISHED, FIN-WAIT-1, FIN-WAIT-2, CLOSE-WAIT, CLOSING, LAST-ACK, and TIME-WAIT. This stateful model informed implementations in stacks distributed with 4.2BSD, SunOS, and commercial systems from vendors like Hewlett-Packard and IBM. The handshake and teardown sequences align with design principles advocated by early networking researchers at Carnegie Mellon University and standards committees within IEEE. Interaction with IP routing and addressing managed by entities such as IANA and protocols like ICMP are implicit in the state transitions and error processing described.

Implementation and Interoperability

Following RFC 793, numerous operating systems and network products adopted the TCP specification, producing interoperable implementations used in software from Microsoft and Apple Computer to embedded stacks in devices designed by Siemens and Ericsson. The document’s precise header layout and checksum algorithm simplified interoperability testing in multi-vendor environments managed by labs at National Institute of Standards and Technology and trade organizations like IETF working groups. Interoperability challenges prompted clarifications and revisions in later experimental RFCs and influenced test suites produced by the Internet Society and collaborative projects within DARPA research programs.

Security Considerations and Vulnerabilities

Although RFC 793 focused on correctness and reliability, its mechanisms were later shown to be susceptible to exploitation in hostile environments. The three-way handshake and sequence number predictability were analyzed in seminal security research at MIT and CMU, leading to the discovery of sequence-number attacks and spoofing techniques exploited in early distributed denial-of-service incidents investigated by CERT Coordination Center. The protocol’s reliance on blind reset and weak authentication assumptions prompted adaptations such as TCP sequence number randomization, SYN cookies, and extensions standardized through collaborative efforts by IETF working groups and security teams at CERT and US-CERT. The interaction of TCP with middleboxes produced by vendors like Juniper Networks and Fortinet further illustrated practical security and ossification issues.

Legacy and Impact on Networking standards

RFC 793’s formalization of a reliable transport service became foundational for application protocols such as File Transfer Protocol, Simple Mail Transfer Protocol, Hypertext Transfer Protocol, and remote access systems like Telnet. Its architectural choices influenced subsequent standards including TCP extensions (Selective Acknowledgment, Window Scaling) and successor transport protocols developed in research at ICSI and standardization efforts within the IETF such as RFC 1122 and RFC 1323. The specification’s influence persists in modern developments including protocol designs like QUIC and congestion-control research at institutions like Stanford and ETH Zurich. RFC 793 remains a touchstone in networking curricula at universities including UC Berkeley and Princeton, and its legacy is evident across commercial and research deployments coordinated by bodies such as IANA and the Internet Society.

Category:Internet standards