Also: internet protocol suite, TCP, UDP, IP protocol, transport layer
TCP/IP is the family of protocols on which the internet runs: IP moves packets between addresses without guarantees, and TCP or UDP ride on top to deliver either a reliable ordered stream or fast unordered messages.
Our take. Every networking course teaches the model and almost none teaches the one fact that explains most outages: IP promises nothing. Packets are dropped, duplicated and reordered as a matter of design, and everything that feels reliable about the internet is TCP doing repair work above a layer that never claimed to be reliable. Learn what the repair costs and you understand latency; learn when to skip it and you understand UDP.
The design splits the job. IP gets a packet from one address to another across any number of networks, by whatever route the routers along the way choose, and makes no promise that it arrives, arrives once, or arrives in order. That is not a weakness; it is what lets the internet survive a failed link by sending the next packet another way. TCP, running on the two end machines, turns that into what applications want: it numbers the bytes, acknowledges what arrived, retransmits what did not, slows down when the network is congested, and presents the receiver with an ordered stream that looks like a pipe. UDP skips all of it and hands the application raw packets, which is exactly right when a late packet is worth less than a fast one.
Property
TCP
UDP
Connection
Set up with a three-step handshake, torn down explicitly
Web pages, email, file transfer, anything that must be complete
Voice and video calls, games, DNS lookups, anything where late is worse than lost
Port numbers are how one machine offers many services: the address gets the packet to the host, the port gets it to the process, and the well-known ports are conventions rather than rules, which is why a web server can listen on any port it likes and why firewalls that filter by port alone are fooled by anything that borrows a common one. The exams live here. The vendor-neutral networking paper asks which protocol a described application should use and why; the entry security paper asks which ports a service uses and what an attacker learns from an open one; the Cisco associate exam asks you to read a capture and say what the handshake reveals about a failed connection.
In practice
A page loads slowly on a lossy connection: TCP is retransmitting and backing off. The link is not slow; it is losing packets, and every loss costs a round trip.
A video call breaks up but keeps going: UDP is dropping late packets on purpose. Retransmitting them would arrive after the moment they described.
A connection hangs for a minute and then fails: the handshake never completed, usually because a firewall silently dropped the first packet instead of refusing it. A refusal would have failed in milliseconds; a drop waits for every retry.
Two applications on one server both work on the same address: ports. The address found the machine; the port found the process.
The OSI model is a seven-layer teaching framework; TCP/IP is the four-layer protocol family that actually runs. Courses map one onto the other and the mapping is loose, which is why the same protocol lands on different layers in different textbooks.
Addressing is how IP names hosts; TCP/IP is the whole suite that carries traffic between them. You can understand addressing without transport and not the reverse.
HTTP is an application protocol that runs over TCP. When a page loads slowly, the question of whether the delay is in HTTP or in the TCP beneath it is the first diagnostic split.
Key takeaways
→IP promises nothing; that is what makes it survive failures.
→TCP repairs the stream at the cost of latency; UDP skips the repair when late beats lost.
→Ports route to processes; well-known numbers are conventions, not rules.
Certifications that test this
Vendor exams whose syllabus covers this concept — facts, cost and a preparation path on each page.
A rotating selection from the course directory, drawn from the subcategories where this concept is taught rather than picked for it. Details, price and the provider link are on the course page.
>>> Start Sending Data Over Long Distance using Arduino via Wired and Wireless Connection and extend Arduino Capabiliti…
Udemy
FAQ
Why does the internet use an unreliable protocol at its core?
Because reliability at the core would be reliability nobody could tune. Putting it at the ends lets each application decide how much it wants: a file transfer wants all of it, a voice call wants almost none, and both run over the same routers.
Is UDP less secure than TCP?
Neither is secure; both carry whatever the application sends, and encryption happens above them. UDP is easier to spoof because there is no handshake to prove the sender is who the packet claims, which matters for some attacks and for why some services rate-limit it.
What is the three-way handshake actually for?
Agreeing starting sequence numbers so both sides can number bytes, and proving each side can reach the other before data flows. A connection attempt that times out rather than failing fast usually means a firewall dropped the first step; the handshake is the first place to look.
Sources
The primary text this definition rests on. Read it before you trust ours.
