Computer Network & Network Security System — Data Link Layer, NEC licence examination syllabus (Nepal Engineering Council).
Wide Area Protocols: X.25, Frame Relay, ATM
Before the modern internet's IP-everywhere approach, WANs had their own dedicated protocol families.
🌍 The Three Legacy WAN Technologies
X.25An early packet-switching WAN standard with heavy error-checking at every hop — reliable, but slow due to that overhead.
Frame RelaySimplified successor to X.25 — drops most hop-by-hop error checking (trusting the endpoints to handle errors instead), making it much faster.
ATMAsynchronous Transfer Mode — transmits data in small, fixed-size 53-byte "cells," designed to carry voice, video, and data equally well with predictable timing.
💡 One-liner: "Why does ATM use small, FIXED-size cells instead of variable-size packets?" → Fixed size makes switching delay predictable — crucial for real-time traffic like voice and video, where variable delays cause noticeable glitches.
Three technologies, one trend
These are far easier to remember as a sequence than as a list, because each was a response to the same changing fact: physical links kept getting more reliable.
X.25 (1970s) links are noisy
→ check for errors at EVERY hop
→ reliable, but heavy and slow
Frame Relay links are much better now
(1990s) → check at the endpoints only, discard bad frames
→ far faster, endpoints retransmit if needed
ATM links are excellent
→ fixed 53-byte cells for predictable switching
→ designed to carry voice, video and data together
Every step moves work out of the network and toward the endpoints. X.25 assumed the network must guarantee delivery because the links could not be trusted; by Frame Relay's era, checking at every hop was paying for a problem that had largely gone away. IP took the same argument to its conclusion — the network makes no delivery guarantee at all, and TCP at the endpoints handles what goes wrong.
💡 That is the answer to "why did IP displace these?" — not that IP was technically superior in isolation, but that it made the fewest assumptions about the network, so it ran over anything. The trend these three follow is the same one that made IP the winner.
Why ATM used tiny fixed cells
A 53-byte cell — 48 bytes of payload and a 5-byte header — looks arbitrary and wasteful. It follows from a single design goal: carrying voice and data on one network.
📦 What fixed size buys
Predictable delayA short cell cannot be stuck behind a long one. Voice tolerates loss but not jitter, so bounded delay was essential.
Simple switchingEvery cell is the same size, so switching can be done in hardware at speed with no buffering decisions about variable lengths.
The cost5 bytes of header on 53 is 9.4% overhead, far worse than Ethernet's on a large frame — the price paid for that predictability.
💡 The 48-byte payload was a committee compromise: one camp wanted 32 bytes to keep voice delay low without echo cancellation, another wanted 64 for data efficiency. Neither won, and the average was adopted — a genuinely useful fact, since the number otherwise looks unmotivated.
💡 Exam framing: X.25 is reliable but slow, Frame Relay faster by trusting the endpoints, ATM fixed cells for predictable, mixed-traffic switching. Then say what unites them — error handling migrating from the network to the edge.
Syllabus points
X.25, Frame Relay, ATM (overview)
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.