Standardisation of TCP/IP and the Birth of the Internet

Moment 10 of 12

IETF publishes RFC 1122 and RFC 1123 standardizing Internet host requirements

November 1, 1989

By the late 1980s, the Internet had expanded well beyond its initial military and academic research roots, connecting thousands of heterogeneous host computers running diverse operating systems. As vendor implementations of TCP/IP proliferated, subtle incompatibilities and non-standard behaviors began causing network instability and interoperability failures across the growing global network.

In November 1989, the Internet Engineering Task Force (IETF) addressed these discrepancies by issuing RFC 1122 and RFC 1123, titled "Requirements for Internet Hosts." Edited by Robert Braden of the Information Sciences Institute (ISI), these twin Request for Comments documents codified official standards for implementing internet protocols across all four TCP/IP layers. RFC 1122 specified lower-level communication requirements including IP, ICMP, TCP, and UDP, while RFC 1123 detailed application-layer protocols such as DNS, SMTP, FTP, and Telnet.

By categorizing protocol implementation features as mandatory ("MUST"), recommended ("SHOULD"), or optional ("MAY"), Braden and the Host Requirements Working Group established clear compliance criteria for software developers. The publication of these landmark standards eliminated widespread interoperability bugs, solidified the core architecture of the Internet, and ensured that software from competing commercial vendors could seamlessly exchange data across the expanding global infrastructure.

Why it matters

RFC 1122 and RFC 1123 served as the definitive architectural bible for software engineers building TCP/IP stack implementations during the commercial expansion of the Internet. Prior to these documents, subtle differences in vendor software frequently caused network crashes or dropped connections. By establishing clear, standardized rules for protocol compliance, the IETF laid the rigorous software foundation necessary for the Internet to scale into a universal commercial utility during the 1990s.

Interesting fact

Bob Braden spent over two years synthesizing feedback from dozens of working group meetings, earning RFC 1122 and 1123 the nickname "The Host Requirements Guide" and establishing the strict normative vocabulary ("MUST", "SHOULD", "MAY") later formalized in RFC 2119.

People

  • Robert BradenEditor of RFC 1122 and RFC 1123, Chair of Host Requirements Working Group
  • Jon PostelRFC Series Editor at the USC Information Sciences Institute
  • Vint CerfCo-designer of TCP/IP and Internet pioneer

Quotes

"A host MUST support the Transmission Control Protocol (TCP) and the Internet Protocol (IP)."
RFC 1122, Section 1.1

Location

USC Information Sciences Institute · Marina del Rey · United States

Open in Google Maps

Watch

References