TCP/IP
In plain English
Plain definition
TCP/IP is the layered protocol suite that provides addressing, routing and reliable end-to-end delivery for communication between networked devices, including the public internet.
Technical Definition
Formally, TCP/IP designates the Transmission Control Protocol (TCP) and the Internet Protocol (IP), together with the wider suite of protocols documented through the RFC process administered by the RFC Editor. The suite is commonly described using a four-layer conceptual model: the link layer (physical and local delivery), the internet layer (logical addressing and routing, principally IP), the transport layer (end-to-end delivery, principally TCP and UDP), and the application layer (protocols such as HTTP, DNS and SMTP that consume transport services). IP provides best-effort, connectionless packet delivery identified by IP addresses; TCP adds connection state, sequencing, acknowledgement and retransmission to provide a reliable, ordered byte stream on top of IP’s unreliable delivery.
| Layer | Representative protocols | Primary responsibility |
|---|---|---|
| Link | Ethernet, Wi-Fi, ARP | Delivery within a local physical or logical segment |
| Internet | IP, ICMP | Logical addressing and routing across networks |
| Transport | TCP, UDP | End-to-end delivery, with reliability where required |
| Application | HTTP, DNS, SMTP | Protocol behaviour consumed directly by software |
Operational Relevance
Practitioners rely on TCP/IP concepts daily when diagnosing connectivity failures, configuring routing and firewall policy, sizing timeouts and retransmission behaviour, and reasoning about where a fault sits in the stack, whether that is a link failure, a routing failure, or an application-level rejection. Because addressing and routing decisions sit at the internet layer while access control commonly depends on transport-layer port information, effective diagnosis depends on separating these layers rather than treating ‘the network’ as a single undifferentiated boundary.
Architecture Relationship
TCP/IP is often compared with the seven-layer OSI reference model, but the two are not equivalent: TCP/IP’s four practical layers map loosely onto OSI’s more granular layers, and production systems are built and troubleshot against the TCP/IP model in practice. Application protocols such as HTTP, DNS and TLS-protected traffic sit above TCP/IP and depend on it for delivery; routing infrastructure, firewalls, NAT devices and VPN tunnels operate primarily within the internet and transport layers, shaping which packets are permitted to traverse a boundary and how they are addressed once they do.
Example
A bounded, low-risk way to validate a TCP/IP path is to work in an isolated or non-production segment and use only read-only diagnostic checks: confirm local interface configuration, confirm reachability to a known-good address, and confirm that the expected transport-layer port is open and answering. Each check should have a defined pass condition, for example, that a specific host responds within an expected time window, and a stop condition, for example, that no response after several attempts indicates a routing or firewall issue and diagnosis should move up the stack rather than repeating the same test. No state-changing network configuration should be applied during this kind of verification; any configuration change belongs in a separate, deliberately scoped change with its own rollback plan.
Misunderstanding
A common misunderstanding is that ‘TCP/IP’ refers only to the Transmission Control Protocol. In practice the name denotes the whole suite, including protocols that do not use TCP at all, such as UDP and ICMP, and applications frequently choose UDP deliberately when TCP’s ordering and retransmission guarantees are not needed. A second common misunderstanding is treating TCP/IP and the OSI model as interchangeable descriptions of the same layers; they are related but distinct reference models with different layer counts and different levels of granularity.
Related Terms
- OSI Model
- User Datagram Protocol (UDP)
- IP addressing and subnetting
- Routing
- Domain Name System (DNS)
- Firewall and access control lists
Further Reading
The RFC Editor maintains the RFC Series, the authoritative publication channel for the Internet technical specifications underlying TCP/IP. This entry was reviewed against that source on 2026-07-31, with a freshness date of 2026-08-08. Specific protocol behaviour can vary by vendor and software version, so version-specific detail should be confirmed against current vendor documentation before being relied upon.
Before relying on this definition to justify a specific change, verify connectivity and behaviour in a non-production environment first, confirm the pass and stop conditions described above, and escalate to a network owner if any read-only check produces an unexpected result rather than proceeding directly to a state-changing action.