Skip to content

TCP/IP Protocol Suite Specified

May 1974 to September 1981.Networking.Standard published.Date precision, month.Evidence grade, primary.5 primary sources

Drivers:

Interoperability needScalability demandStandardisation

The need to connect ARPANET with other networks (satellite, packet radio) drove the development of a universal internetworking protocol. The existing NCP could not span network boundaries.

TCP/IP is like the language computers use to talk to each other across the internet. IP handles addressing (like putting an address on an envelope), while TCP makes sure the message arrives complete and in order (like registered post that confirms delivery).

TCP/IP Protocol Suite Specified event plate

Structured atlas record showing date, domain, evidence grade, source count, and predecessor and successor links.

Event plate: TCP/IP Protocol Suite Specified Convergence-divergence layout. The central hero card carries the event year, type, title, evidence grade, domain and era band. 0 predecessor cards on the left feed in with red arrows labelled "absorbs". 0 successor cards on the right derive with red arrows labelled "spawns". Key terms below the hero pin the vocabulary the event introduced. EVENT PLATE Source: https://ieeexplore.ieee.org/document/1092259 1974 - STANDARD PUBLISHED TCP/IP Protocol SuiteSpecified primary evidence Domain: AI and machine learning Era band: E6 AI-scale systems KEY TERMS - VOCABULARY THE EVENT INTRODUCED TCP IP internetworking protocol suite Convergence-divergence: predecessors absorbed, successors spawned Hero card carries year, evidence and domain. 0 predecessors flow in from the left; 0 successors flow out to the right. Key termsbelow pin the vocabulary the event introduced.

Forecasts and counterfactuals stay labelled as opinion in the event data. Source: Computer History Museum.

Before

ARPANET used the Network Control Protocol (NCP), which worked only within a single network. There was no way to interconnect different networks (e.g., ARPANET, satellite networks, radio networks) into a unified internetwork.

What changed

The Transmission Control Protocol (TCP) and Internet Protocol (IP) provided a universal protocol suite that could interconnect heterogeneous networks. IP handled routing between networks; TCP handled reliable end-to-end communication.

How it happened

Vinton Cerf and Robert Kahn published 'A Protocol for Packet Network Intercommunication' in May 1974, describing the initial TCP design. RFC 675 (December 1974) provided the first TCP specification. The protocol was later split into TCP (transport) and IP (network), formalised in RFC 791 (IP) and RFC 793 (TCP) in September 1981.

Outcomes

  • Created the protocol foundation of the modern internet
  • Enabled interconnection of diverse network technologies
  • Established the principle of network independence (IP hides network differences)
  • Introduced concepts still central to networking (IP addresses, three-way handshake)

Limitations

  • Original design had no built-in security (addressed later with IPsec, TLS)
  • IPv4 address space (32-bit) proved insufficient, requiring IPv6
  • Header overhead reduces efficiency for small packets
  • TCP optimised for reliability over latency

Lessons learnt

  • Layered architecture enables independent evolution
  • Simple, universal protocols scale better than complex, specialised ones
  • Security should be considered in initial design
  • Address space requirements are difficult to predict

Stakeholders and artefacts

Organisations

  • DARPAgovernmentFunded development
  • Stanford UniversityacademiaCerf's research base
  • BBNvendorKahn's research base, implementation

Individuals

  • Vinton CerfCo-designer, Stanford UniversityCo-designed TCP/IP, often called 'Father of the Internet'
  • Robert KahnCo-designer, DARPA/BBNCo-designed TCP/IP, initiated internetworking programme
  • Jon PostelEditor/Contributor, USC ISIEdited RFCs 791 and 793, managed protocol development

Artefacts

  • IP (Internet Protocol)protocolNetwork layer protocol handling addressing and routing
  • TCP (Transmission Control Protocol)protocolTransport layer protocol providing reliable, ordered delivery
  • IP Addressspecification32-bit (IPv4) or 128-bit (IPv6) numerical identifier for network hosts

Key terms

TCPIPinternetworkingprotocol suiteRFC

Causality

Preceded by: First ARPANET Message Transmitted.

Made possible: OSI Reference Model Published.

On this course

Read in the path How the Internet Works.

Sources

1Vinton G. Cerf, Robert E. Kahn. "A Protocol for Packet Network Intercommunication". IEEE, 1974-05.peer reviewedieeexplore.ieee.org/document/1092259
2Vinton Cerf, Yogen Dalal, Carl Sunshine. "RFC 675: Specification of Internet Transmission Control Program". Network Working Group, 1974-12.authoritativewww.rfc-editor.org/rfc/rfc675
3Jon Postel. "RFC 791: Internet Protocol". DARPA, 1981-09.authoritativewww.rfc-editor.org/rfc/rfc791
4Jon Postel. "RFC 793: Transmission Control Protocol". DARPA, 1981-09.authoritativewww.rfc-editor.org/rfc/rfc793
5Barry M. Leiner, Vinton G. Cerf, David D. Clark, Robert E. Kahn, Leonard Kleinrock, Daniel C. Lynch, Jon Postel, Larry G. Roberts, Stephen Wolff. "A Brief History of the Internet". Internet Society, 1997.authoritativewww.internetsociety.org/internet/history-internet/brief-history-internet/