Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
TCP/IP is a suite of cooperating protocols, not a single protocol. Applications use transport protocols such as TCP or UDP; IP gives the resulting data network addresses and moves it as datagrams across interconnected networks; routers forward those datagrams; and each local link carries a datagram to the next device. At the destination, the layers hand the data back to the correct application.
This division of labor lets a browser, phone app, game, or mail client communicate across many different networks without knowing the physical technology used on every hop. TCP can add reliable, in-order delivery, while UDP offers a simpler datagram service when the application needs lower overhead or control over timing.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
TCP/IP Illustrated: The Protocols, Volume 1 (Addison-Wesley Professional Computing Series) | $64.49 | Buy on Amazon |
TCP/IP is a family of protocols with separate jobs
The name TCP/IP combines two important protocols, but the Internet uses many protocols that cooperate at different layers. A useful way to understand the suite is to follow data downward from an application and then upward again at the destination.
Recommended Free Tools
- Application protocols define what an application means by its messages, such as a request for a web resource or a name lookup.
- Transport protocols move data between application processes. TCP exposes a reliable, ordered byte stream; UDP exposes datagrams without TCP’s built-in ordering and retransmission service.
- IP supplies network-layer addresses and carries datagrams between networks. IPv4 is specified in RFC 791 (September 1981), while RFC 8200 (July 2017) specifies IPv6 as the successor to IPv4.
- Link or network-access technologies carry an IP datagram across one particular local connection to the next device. The technology can differ from one link to the next.
These layers are related but not interchangeable. A local link can deliver a frame to a neighboring router, but it does not provide the Internet-wide addressing that IP provides. IP can forward a datagram toward a destination, but it does not promise that the datagram arrives. TCP, when selected by the application, supplies end-to-end recovery and ordering above IP.
#1 Best Overall
How data travels across the internet
Consider a browser requesting a page from a server. The exact exchange can use TCP or another transport, so this example illustrates the layered process rather than claiming that every web transaction uses TCP.
- The application creates data. The browser constructs an application message, such as a request for a resource, and gives it to the transport protocol selected by the application and service.
- The transport adds process information. TCP treats the application input as a byte stream and divides that stream into segments for transmission. UDP places an application message in a datagram. A transport header includes source and destination port information so the receiving system can deliver the data to the correct service.
- IP packages the transport unit. The TCP segment or UDP datagram becomes the payload of an IP datagram. IP adds source and destination network addresses and other fields needed for forwarding.
- The local link sends the datagram to a neighbor. A network-access technology puts the IP datagram into a link-specific frame and delivers it to the next device, often a router or a directly connected host.
- Routers make forwarding decisions. Each router receives the frame, processes the IP datagram, consults its current routing information, and sends the datagram over the next link. The next link can use a different technology and addressing format.
- The destination host removes the layers. The final link delivers the datagram to the destination system. IP passes its payload to the transport protocol identified in the IP header, and the transport port identifies the receiving application service.
- The transport completes delivery to the application. TCP uses sequence numbers, acknowledgments, checksums, and retransmission to reconstruct the ordered byte stream and recover missing data. UDP delivers its datagrams without providing TCP’s reliability and ordering guarantees; an application that needs those properties must implement them or choose another protocol.
The path is not a permanent physical track. IP datagrams are treated independently, and routing decisions can change as networks, links, and routing information change. Different datagrams from one exchange can therefore take different routes or encounter different delays.
What IP does—and what it deliberately does not do
Addressing and datagram delivery
IP’s central job is to move datagrams through interconnected networks. An IP header identifies where a datagram came from and where it is intended to go. Routers use the destination address to select a next hop, progressively moving the datagram toward the destination network.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11IPv4 and IPv6 perform this network-layer role with different address formats and protocol details. IPv6 is specified as the successor to IPv4 in RFC 8200. Using IPv6 does not turn IP into a reliable transport: it still provides best-effort datagram delivery, leaving end-to-end recovery and ordering to a higher layer when needed.
Best effort, not a delivery guarantee
RFC 791 explicitly distinguishes IP from a reliable end-to-end service. IP does not provide end-to-end reliability, flow control, or sequencing. A datagram can be delayed, discarded, duplicated, or delivered out of order, and IP itself does not repair those conditions. That design keeps the network layer broadly usable across many kinds of networks while allowing applications to choose the transport behavior they require.
TCP: a reliable, in-order byte stream
The current consolidated TCP specification, RFC 9293 (edited by Wesley Eddy and published in August 2022), states: “TCP provides a reliable, in-order, byte-stream service to applications.” Each part of that description matters.
Byte stream rather than message boundaries
An application writes bytes to a TCP connection; TCP may divide those bytes into segments of different sizes for transmission. At the receiving end, TCP presents the bytes in sequence as a stream. The application should not assume that one write corresponds to one read or that the receiver sees the sender’s original segmentation.
Sequence numbers and acknowledgments
TCP numbers the bytes in the stream. The receiver acknowledges data it has received, allowing the sender to determine which portion arrived. Checksums help detect corruption. If an acknowledgment does not arrive as expected, TCP can retransmit data. These mechanisms let the endpoints recover from loss without asking the application to track every missing piece.
Ports identify the service
IP addresses identify hosts or network interfaces; TCP ports identify application endpoints on those hosts. A connection is associated with the relevant source and destination addresses and ports, allowing one computer to run many network services at once. TCP is connection-oriented, so the endpoints establish transport state before exchanging the application stream and maintain that state while the connection is active.
What TCP does not hide
TCP cannot make an unavailable server respond, and it cannot eliminate delay caused by congestion or a broken link. Its retransmission and ordering behavior can increase waiting time when data is lost. Applications that value correctness and a complete ordered stream commonly accept that trade-off.
UDP: datagrams with fewer built-in guarantees
RFC 768 (August 1980) specifies UDP as a user datagram protocol used with IP. UDP sends discrete datagrams and includes port information for delivery to an application, but it does not provide TCP’s reliable, in-order byte-stream service.
Free tools Windows power users keep installed
One-click scans. No signup required.
A UDP datagram can be lost, duplicated, delayed, or received out of order. UDP itself does not retransmit missing data or turn several datagrams into a single ordered stream. That simpler service can be useful when an application needs minimal transport processing, wants each message to remain a distinct datagram, or has its own rules for recovery, ordering, deadlines, or congestion behavior.
Choosing UDP is not the same as choosing “unreliable software.” The application may add acknowledgments, sequence numbers, forward-error correction, or selective retransmission. The important distinction is where those decisions live: TCP supplies a standardized reliable stream, while a UDP-based application decides which features are worth implementing for its workload.
TCP and UDP compared
| Characteristic | TCP | UDP |
|---|---|---|
| Unit presented to the application | Ordered byte stream | Individual datagrams |
| Built-in ordering | Yes, using sequence numbers and reassembly | No |
| Built-in loss recovery | Yes, through acknowledgments and retransmission | No; the application may add its own |
| Connection model | Connection-oriented transport state | Connectionless datagram service |
| Application responsibility | Handle stream semantics and application errors; TCP handles transport recovery | Handle any required ordering, reliability, timing, or duplicate suppression |
| Underlying network | Operates over IP | Operates over IP |
Neither transport is universally “faster” or “better.” The right choice depends on whether the application needs a complete ordered stream or prefers control over individual messages and recovery policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Routers, links, and the layered handoff
A router participates in multiple networks. On receiving a link-layer frame, it extracts the IP datagram, examines the destination address, and transmits the datagram in a new frame appropriate for the next link. The IP datagram is therefore carried by a succession of local link technologies rather than by one end-to-end link.
This handoff explains why the Internet can join unlike networks. A local wireless connection, an Ethernet segment, and a provider’s long-distance link can all carry the same network-layer datagram even though their framing and physical transmission methods differ. Each hop handles local delivery; IP preserves the network-layer destination across the routed path.
The receiving router does not normally need to understand the application’s message. It forwards based on network-layer information. TCP or UDP processing occurs at the endpoints, where the transport ports and application data are meaningful.
A complete mental model for a web request
Use this compact model when diagnosing or explaining an Internet exchange:
- Application: “I need to send or receive this meaningfully structured data.”
- Transport: “Which process should receive it, and do we need a reliable stream or datagrams?”
- IP: “Which network address is the destination, and how can a datagram be forwarded there?”
- Link: “How do I carry this datagram to the next device on this particular network?”
- Destination stack: “Which transport and port should receive the payload, and how should it be presented to the application?”
Encapsulation describes the downward journey: application data becomes a transport segment or datagram, which becomes an IP datagram, which is carried in a link-specific frame. Decapsulation describes the upward journey at the destination. Routers generally remove and rebuild only the link framing at each hop while forwarding the IP datagram onward.
Common misconceptions and the correct interpretation
“TCP/IP is one protocol.”
It is a protocol suite. TCP and IP are distinct, and many other protocols fill application, transport, and link-layer roles.
“IP guarantees that every packet arrives.”
It does not. IP provides addressing and best-effort datagram delivery; reliability, sequencing, and flow control are not IP guarantees.
“Every Internet application uses TCP.”
Applications can use UDP or other transports when a stream is not the right abstraction. The transport choice is an application and protocol-design decision.
“One exchange follows one fixed route.”
Routing decisions can change, and IP datagrams are handled independently. The path and timing can vary during an exchange.
“A link-layer delivery is the same as Internet delivery.”
A link moves a frame to a neighboring device on one network. IP provides the addressing and forwarding model that spans many networks.
Where to study the specifications
For authoritative details, RFC 9293 is the current consolidated TCP specification, RFC 791 defines foundational IPv4 behavior, RFC 8200 specifies IPv6, and RFC 768 defines UDP. RFC 1180, published in January 1991, offers an accessible historical TCP/IP tutorial; use it for concepts rather than as a replacement for current protocol specifications.
Readers who want a detailed, packet-level treatment can consult TCP/IP Illustrated, Volume 1: The Protocols, 2nd edition, by Kevin R. Fall and W. Richard Stevens. Pearson lists a print edition with extensive TCP/IP protocol coverage. Availability and pricing can change, so the book is an optional next step, not a prerequisite for understanding the layered model.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors
