Your cookie choices
Essential cookies keep your basket and sign-in working. Optional cookies help us understand visits and measure ads. Privacy details.
Essential cookies keep your basket and sign-in working. Optional cookies help us understand visits and measure ads. Privacy details.
Fundamental communication protocol suite that powers the internet.
AI-assisted explanation. It may contain errors; use a textbook or original source to check important details.
TCP/IP isn’t a single equation—it’s a pair of cooperating ideas (really, a whole suite of rules) that together explain how the internet moves information reliably across messy, unpredictable networks. Think of sending a long message as mailing a book to a friend across a world of postal systems you don’t control. - IP (Internet Protocol) is the addressing-and-routing part: it’s like writing the destination address on every envelope and trusting the postal system to move each envelope step-by-step through sorting centers (routers). IP’s job is to get small pieces of data called packets from one machine to another, but it makes no promises: packets can be delayed, duplicated, arrive out of order, or vanish. - TCP (Transmission Control Protocol) is the reliability-and-ordering part: it’s like a careful librarian who numbers all the pages, checks which ones arrived, requests missing pages again, and reassembles the book in the right order. TCP adds features like: - Sequencing (so pieces can be put back in order) - Acknowledgments (the receiver confirms what arrived) - Retransmission (missing data gets resent) - Flow control (don’t overwhelm a slow receiver) - Congestion control (don’t flood the network when it’s busy) Together, TCP/IP is the quiet choreography that makes “send a message,” “load a webpage,” or “stream a file” feel instantaneous and dependable—despite the underlying network being a constantly changing web of routes and traffic.
TCP/IP was developed in the 1970s as part of the effort to build a robust, interoperable network of networks—what we now call the internet. At the time, ARPANET (an early packet-switched network funded by the U.S. Department of Defense’s ARPA) existed, but the bigger dream was to connect different kinds of networks (satellite links, radio networks, wired networks) into one seamless system. The key challenge: how do you design communication rules that still work when the path is unreliable, the network is heterogeneous, and pieces may fail? The breakthrough was the concept of an internetworking protocol (IP) that treats each underlying network as a “black box,” plus an end-to-end reliability layer (TCP) that lives at the communicating computers rather than the network core. This philosophy—often summarized as the end-to-end principle—helped the internet scale and evolve. TCP and IP were originally conceived together; later the design was split into separate layers, producing the modern TCP/IP architecture. A major milestone was the “flag day” transition on January 1, 1983, when ARPANET switched from its older protocol (NCP) to TCP/IP, cementing TCP/IP as the foundation of the growing internet.
Pioneered by: Primarily Vinton G. Cerf and Robert E. Kahn (often called the “fathers of the Internet”) developed the core ideas and early specifications of TCP/IP in the 1970s, building on packet-switching work by researchers such as Paul Baran, Donald Davies, and Leonard Kleinrock. Many others contributed to refinements, implementations, and standardization through the IETF and related communities.