The Transport Service

Computer Network & Network Security System — Transport Layer, NEC licence examination syllabus (Nepal Engineering Council).

The Transport Service: the last layer that still cares about your data's journey

Above this layer, nobody cares HOW the data got there anymore — only that it did.

The network layer's job ends at "deliver this packet somewhere on that machine." The transport layer's job is to deliver it to the exact right APPLICATION on that machine, and decide how carefully to babysit the delivery along the way.

📮 Process-to-Process Delivery

Network layerHost-to-host delivery — gets data to the right MACHINE.

Transport layerProcess-to-process delivery — gets data to the right APPLICATION running on that machine (your browser, not your email client).

Reliable service (like TCP) guarantees delivery, order, and integrity — at the cost of some speed and overhead. Unreliable service (like UDP) makes no such guarantees, but is faster and lower-overhead — a deliberate tradeoff, not a flaw.

💡 One-liner: "Why would anyone WANT unreliable service?" → For real-time applications (voice/video calls), a late retransmitted packet is more useless than a dropped one — speed matters more than perfection.

Why an unreliable service is offered at all

If TCP delivers everything in order and UDP does not, UDP looks strictly worse. It is not, and the reason is a specific cost of the reliability guarantee.

TCP delivers bytes in order. So if one segment is lost, every segment that arrives after it must wait in a buffer until the missing one is retransmitted and received — even though those later segments are sitting in memory, complete and correct. This is head-of-line blocking: one loss stalls everything behind it for at least a full round trip.

🎙️ When waiting is worse than losing

Live audio or videoA packet arriving 200 ms late is useless — that moment has already passed. Better to play through a tiny gap than to freeze while it is recovered.

Online gamingA position update from half a second ago is worse than no update, because a newer one has already superseded it.

DNSOne small request, one small reply. Setting up a connection would cost more round trips than simply asking again if nothing comes back.

💡 So the exam answer to "why use UDP when TCP is reliable?" is not merely that UDP is lighter. It is that retransmission takes time, and for real-time data a late packet has no value — so the recovery is worse than the loss. Reliability is a cost as well as a benefit.

What the transport layer adds to the network layer

📶 Four things IP does not do

Process addressingIP reaches a machine; ports reach a program on it.

ReliabilityIP may drop, duplicate or reorder. TCP detects and repairs all three; UDP declines to.

Flow controlPreventing a fast sender from swamping a slow receiver — meaningless at the network layer, which has no idea who is reading.

Congestion controlBacking off when the network is overloaded, which requires end-to-end knowledge routers do not have.

The design principle underneath is the end-to-end argument: a function that can only be implemented correctly at the endpoints should live there, not in the network. Only the endpoints know whether a byte was actually delivered to the application, so that is where reliability belongs — which is why IP deliberately makes no such promise.

Syllabus points

Process-to-process delivery
Reliable vs unreliable service

Create a free account to tick topics off, take notes as you read, watch the video lessons and get a day-by-day study plan built around your exam date.