ARPANET transitions to TCP/IP

ARPANET initially used the Network Control Protocol. Other research networks developed different transmission arrangements, creating a need for communication across unlike systems. Cerf, Kahn, and numerous collaborators designed methods that separated internetwork addressing from parts of transport control. Gateways forwarded packets while endpoints handled selected reliability functions. Participating networks could retain internal technologies. Experiments tested the approach, but moving existing hosts also required coordinated changes across institutions already using operational communication services.

References: [1]

A transition plan published in 1981 scheduled ARPANET’s move to TCP and IP for 1 January 1983. Hosts needed updated operating and communication software. Preparations, testing, and deadlines coordinated adoption. IP provided addressing and packet delivery, while TCP supplied connection management, ordering, and retransmission for suitable applications. Other transport protocols could also use IP. The layered structure supported different services and a common interface between networks, allowing connections to expand further.

References: [1]

Universities, research institutions, and later commercial networks adopted the protocol family. Domain naming, routing, and applications continued developing across an expanding Internet. Email and eventually the World Wide Web used this infrastructure. Published standards and negotiation helped manufacturers and operators maintain compatibility. The migration involved code changes, organizational coordination, and ongoing maintenance. Growth depended on shared rules alongside the separate networks that supplied equipment, connectivity, and everyday operational work.

References: [1]