Ethernet and the IEEE Standards: 10 Mbps to 800 Gbps

Ethernet and the IEEE Standards: 10 Mbps to 800 Gbps

What you'll learn

• Explain why standards exist and which IEEE 802 families still matter (802.3, 802.11, 802.1)
• Decode any Ethernet name — 100BASE-TX, 1000BASE-LX, 10GBASE-SR — into rate, signaling and medium
• Compute throughput with Tp = Fs/Ts and dodge the megabyte/megabit trap
• Place CSMA/CD in history and CSMA/CA in today's Wi-Fi
• Read the Ethernet ladder from 10 Mbps to 800 Gbps, including multi-gig and PoE — copper's two modern superpowers

Why standards exist at all

This lesson builds on Chapter 7 of Dr. Tahseen Al-Doori's Network Essentials, with the Ethernet-versus-Token-Ring story from Chapter 3. A classic analogy from Dr. Al-Doori's course explains why any of it matters: picture yourself road-tripping across Europe in an imported American car when the brakes start grinding. The garage you limp into has shelves full of brake parts — none of which fit your car, because every part in the building follows metric specifications and your car follows different ones. Stocked shelves, willing mechanic, no help. That stranded feeling is life without shared standards, and it is exactly what early networking looked like: equipment that worked beautifully — with itself.

The fix is the IEEE (Institute of Electrical and Electronics Engineers), the body that creates and ratifies the standards behind nearly everything electrical in networking — not judging product quality, but defining the shared specifications that make one vendor's port accept another vendor's cable. Its LAN standards all live under the number 802, followed by a dot and a working-group number. Three families do almost all the work in 2026:

• 802.3 — Ethernet (current): every wired LAN port you will ever touch.
• 802.11 — Wi-Fi (current): wireless LANs, with Module 6 all to itself.
• 802.1 — bridging and network management (current): the glue standards switches implement, including VLANs (next lesson) and loop protection.

The book's 2007 edition also listed a second tier "worth knowing": 802.5 (Token Ring), 802.9 (integrated voice and data) and 802.10 (network security) — the latter two flagged as increasing in importance. Here 2026 must gently overrule the forecast: all three are withdrawn (obsolete). Token Ring lost the LAN war entirely; 802.9's voice-data integration happened, but via IP telephony instead; 802.10 was abandoned in favor of other security approaches. Keep this as more than trivia — it is a lesson in how technology forecasting fails, and why this course tags every technology with its current status instead of trusting any single snapshot in time.

Ethernet versus Token Ring: how the war was won

Since Token Ring just entered as a casualty, meet it properly — the comparison teaches why Ethernet rules the world.

Token Ring (802.5) connected machines in a logical ring around which a single permission slip — the token — circulated. Only the machine holding the token could transmit; everyone else waited. Orderly, deterministic, collision-free by construction. Think of a relay race: you run only while holding the baton, so runners never trample each other.

Ethernet (802.3) took the opposite bet: no token, no schedule — any machine may try to transmit whenever the wire sounds idle, accepting that transmissions will sometimes crash into each other. A marathon, not a relay: everyone on the course at once, occasionally jostling.

A classic analogy from the book's teaching tradition explains the deeper argument, using holiday light strings. Some strings are wired in series: one bulb fails and everything beyond it goes dark. Others give each bulb an independent circuit: one fails, the rest shine on. Token Ring had a series-string quality — the design centered on an unbroken ring — while star-wired Ethernet let any single machine die without dimming the network around it. Add that Ethernet gear was cheaper to buy and simpler to fix, and the outcome stops being surprising: resilience and economics beat elegance, a pattern you will see again and again in this field. Token Ring is history (obsolete); the reasoning that killed it is evergreen.

Sharing the wire: CSMA/CD then, CSMA/CA now

If Ethernet lets anyone transmit whenever the wire seems free, something must handle the inevitable pile-ups. The original answer was CSMA/CD — Carrier Sense Multiple Access with Collision Detection. Unpack the name: carrier sense — listen before transmitting, and hold off while someone else is talking; multiple access — many machines share the medium; collision detection — while transmitting, keep listening, and if your signal collides with another, stop, wait a random backoff interval, and retry. The book sets it in a lively classroom: students speak up when the room sounds quiet, without raising hands; occasionally two start at once, both stop, and after an awkward beat one nods the other ahead. Random politeness as a protocol.

Now the 2026 correction — one of this course's clearest then-versus-now beats. On modern wired networks, CSMA/CD is history (legacy — still worth knowing). You saw why in the previous lesson: switches gave every device a private micro-segment, and full duplex gave it separate transmit and receive lanes. No shared wire, no possible collision, nothing to detect. The algorithm still ships in standards documents for backward compatibility, but on a switched full-duplex network it simply never engages — and the newest Ethernet speeds do not even define a half-duplex mode to need it. When an exam or interview asks, the professional answer is: CSMA/CD belongs to the hub era; switching retired it.

Its cousin lives on. CSMA/CA — Collision Avoidance — governs Wi-Fi (802.11), because radio cannot detect collisions: a transmitting radio drowns out its own receiver, so crashes must be prevented rather than noticed. Wireless devices therefore coordinate before sending — the hand-raised classroom instead of the free-for-all — including an optional request/clear exchange with the access point that solves radio's "hidden node" problem, where two devices both in range of the access point are out of range of each other. Details belong to Module 6; the placement belongs here: CD is wired history; CA is wireless present. (One correction to file: some older materials, including a line in the book's Chapter 7, group Token Ring under CSMA/CA. Strictly, token passing is its own access method — the baton race — while CSMA/CA is the listen-and-avoid family that Wi-Fi uses. Keep the three methods distinct and the distinction will never cost you a mark.)

Bandwidth versus throughput: the pipe and the water

Lesson 1 promised this pair a proper treatment. A classic analogy from Dr. Al-Doori's course delivers it through plumbing: compare the water main feeding a whole neighborhood — fat as a dinner plate — with the narrow pipe entering one house. Water moves at similar speed through both; what differs is how much arrives per second, set by the pipe's width. Bandwidth is the width of the pipe: capacity, not velocity. In signaling terms it is how much signal a medium carries per second — and remember from lesson 1 that electrons don't move faster in better cable; better cable simply carries more.

Throughput is what actually comes out of the tap: the amount of data really delivered from source to destination per second, after every real-world loss — congestion, errors, protocol overhead, and above all the narrowest pipe along the path. Throughput almost never equals bandwidth, and the gap between them is where network administrators go hunting for bottlenecks.

Throughput has a formula, and the book's version is the one this course drills:

Tp = Fs / Ts — throughput equals file size divided by transfer time in seconds.

One trap accounts for nearly every wrong answer: file sizes come in bytes (B); network rates come in bits (b) — and one byte is eight bits. Convert before dividing. Worked example, our numbers: a 250 MB file transfers in 40 seconds. Convert: 250 MB × 8 = 2,000 megabits. Divide: 2,000 Mb ÷ 40 s = 50 Mbps throughput. If that transfer crossed a gigabit port, the pipe was twenty times wider than the flow — time to ask what narrowed it: the far server? a congested uplink? the disk? (Sometimes the bottleneck isn't the network at all — a truth that will save you hours someday.) Capital B, little b: the marketing department's favorite ambiguity, now permanently yours to see through.

Reading the label: Ethernet's naming code

Chapter 7 teaches a decoding skill that transfers perfectly to 2026, because Ethernet still names its standards the same way. Every name — on a switch datasheet, a NIC box, an interface listing — has three parts:

[rate] BASE [medium code]

• Rate: the bandwidth, in Mbps unless suffixed G (10 = 10 Mbps; 100 = Fast Ethernet; 1000 or 1G = Gigabit; 10G, 40G, 400G and up).
• BASE: baseband signaling — lesson 1's one-signal-at-a-time transmission. Essentially every LAN standard is baseband, so you will read this word thousands of times.
• Medium code: the letters that tell you what the standard runs on. T means twisted pair. Fiber letters sketch the wavelength and reach class rather than the fiber type: S short-wavelength (multimode), L long-wavelength (single-mode, and sometimes multimode with a mode-conditioning cord), E extended reach. Check the optic's datasheet for the fiber it actually supports. An X or R marks encoding details you can safely wave at for now. The book is refreshingly honest here: beyond T and the fiber letters, the letter codes stop following any tidy system, and a little memorization beats searching for logic that isn't there.

So 100BASE-TX reads: 100 Mbps, baseband, twisted pair (Cat5-era). 1000BASE-LX: gigabit, baseband, long-wavelength (1310 nm) laser over fiber — 5 km on single-mode, or 550 m on multimode with a mode-conditioning patch cord; the classic campus link. 10GBASE-SR: 10 gigabits, short-reach multimode — inside a datacenter. Three glances, full identification. That is the skill; the worksheet below drills it on eight real labels, and Download: Ethernet and Cable Labels Reference (the whole decoder ring on one page) is built for your pocket.

The ladder to 800 gigabits — and power in the bargain

Now for this lesson's biggest modernization. The book's speed ladder topped out at 10 Gbps, state of the art for 2007. The ladder since kept climbing — and, more interestingly, grew middle rungs:

The 2.5/5 Gbps rungs deserve a pause, because they answer a question the pure ladder can't: why would engineers standardize slower speeds after faster ones existed? Because of lesson 1's installed base: the world's walls are full of Cat5e that cannot carry 10GBASE-T, and rewiring buildings costs fortunes. Multi-gig Ethernet was designed to push 2.5 or 5 Gbps through that existing copper — which is exactly what modern Wi-Fi access points need from their uplink cable. An engineering compromise shaped by economics: the whole Ethernet story in one standard. Beyond the table, the climb continues — 1.6 terabit work is in progress (as of the Ethernet Alliance's current roadmap), and the industry that was supposed to be replaced by something newer many times over keeps simply out-evolving its replacements.

The ladder's companion superpower travels the same copper: Power over Ethernet, teased in lesson 1 and delivered here. Three amendments mark the generations, and each quotes two numbers — what the switch sources and what the device is guaranteed to receive, the gap being cable loss over 100 m: 802.3af (15.4 W sourced, 12.95 W at the device), 802.3at (30 W sourced, 25.5 W at the device), and 802.3bt (up to 90 W sourced, 71.3 W at the device). Always size equipment against the second number. Real deployments hang whole categories of equipment on that wattage: VoIP phones and cameras at the low end, Wi-Fi access points in the middle, and point-of-sale terminals, displays, even building lighting at the top. One cable, data plus power, no electrician — a large share of the reason twisted pair still owns the network edge in 2026.

From the textbook to 2026

Chapter 7's method — decode the name, respect the difference between bandwidth and throughput, know your access methods — survives fully intact; this course changed the inventory, not the teaching. The ladder gained rungs to 400G and 800G with 1.6T climbing; multi-gig filled the middle so old copper could keep up; PoE turned the cable into a power cord. CSMA/CD moved from operations to history as switching made collisions impossible, while CSMA/CA thrives wherever radios share air. And the book's second-tier standards list became an epitaph: Token Ring, 802.9 and 802.10 all withdrawn — the strongest argument this module offers for learning how to read standards rather than memorizing any year's roster.

Worksheet: Throughput and label decoding

Part A — throughput drills. Use Tp = Fs/Ts. Convert bytes to bits first (×8). Answers follow — work all five before peeking.

1. A 400 MB video file downloads in 64 seconds. What is the throughput?
2. A 4.5 GB game update arrives in 6 minutes. Throughput? (Watch both conversions: GB→Mb and minutes→seconds.)
3. A nightly backup moves 90 GB and must finish inside a 2-hour window. What minimum sustained throughput does the job require, and is a 100 Mbps link enough?
4. Your ISP sells a "1 Gbps" plan. A speed-test download peaks at 118 MB/s and a friend calls it false advertising. Compute what 1 Gbps promises in MB/s and rule on the complaint.
5. Two PCs on the same gigabit switch copy a folder at a measured 60 MB/s. Is the network the bottleneck? Compute, then name one non-network suspect and how you would test it.

Part A — answers.

1. 400 MB × 8 = 3,200 Mb; 3,200 ÷ 64 = 50 Mbps.
2. 4.5 GB = 4,500 MB × 8 = 36,000 Mb; 6 min = 360 s; 36,000 ÷ 360 = 100 Mbps.
3. 90 GB = 720,000 Mb; 2 h = 7,200 s; 720,000 ÷ 7,200 = 100 Mbps minimum. A 100 Mbps link is exactly enough only in a perfect world with zero overhead — reality never is, so the window will be missed; specify gigabit.
4. 1 Gbps = 1,000 Mbps ÷ 8 = 125 MB/s theoretical ceiling. Measuring 118 MB/s is about 94% of the ceiling — excellent, once protocol overhead is counted. Complaint dismissed; the friend confused bytes with bits.
5. 60 MB/s × 8 = 480 Mbps — under half the gigabit pipe, so the network is not saturated. Prime suspect: disk read/write speed on either PC (or the file-sharing protocol's own overhead). Test: repeat the copy between faster drives (or run a memory-to-memory network benchmark) and see whether the number moves.

Part B — decode these eight labels. For each: rate, signaling, medium — plus its 2026 status. Answers below.

1. 10BASE2 · 2. 10BASE-T · 3. 100BASE-TX · 4. 100BASE-FX · 5. 1000BASE-T · 6. 1000BASE-LX · 7. 2.5GBASE-T · 8. 10GBASE-SR

Part B — answers.

1. 10BASE2 — 10 Mbps, baseband, thin coax (the "2" hinted at ~200 m reach; really 185 m). The old bus-topology LAN cable. (Obsolete.)
2. 10BASE-T — 10 Mbps, baseband, twisted pair; the standard that moved Ethernet onto phone-style wiring and star topologies. (Obsolete, historically pivotal.)
3. 100BASE-TX — 100 Mbps "Fast Ethernet," baseband, twisted pair (Cat5-era; the X marks its encoding scheme). (Legacy — still found in walls and cheap gear.)
4. 100BASE-FX — 100 Mbps, baseband, fiber (two-strand multimode); the campus-link workhorse of its day. (Legacy.)
5. 1000BASE-T — Gigabit, baseband, twisted pair (Cat5e or better, all four pairs). (Current baseline everywhere.)
6. 1000BASE-LX — Gigabit, baseband, long-wavelength fiber: 5 km on single-mode, or 550 m on multimode with a mode-conditioning patch cord. (Current for modest campus links.)
7. 2.5GBASE-T — 2.5 Gbps, baseband, twisted pair — the multi-gig rung built to run on the installed Cat5e base; the Wi-Fi access point's favorite uplink. (Current.)
8. 10GBASE-SR — 10 Gbps, baseband, short-reach multimode fiber: rack-to-rack inside datacenters. (Current.)

Check yourself

1. An interviewer asks: "Is CSMA/CD running on your office network right now?" Give the two-sentence professional answer.
2. A colleague reads "1000BASE-LX" on a datasheet and asks what it means and roughly where you'd deploy it. Decode all three parts and answer.
3. A 1.2 GB file transfers in 4 minutes. Compute the throughput — mind both unit conversions.
4. Which IEEE family would you consult for: (a) a VLAN tagging question, (b) a Wi-Fi channel question, (c) a question about 800 Gbps optics?
5. A PoE security camera needs 22 W delivered at the device. Will an 802.3af port do? Name the amendment you'd specify and why.
6. A vendor pitches a retro "deterministic token network — zero collisions, guaranteed access." Grant the premise, then explain in two sentences why history still picked Ethernet.

Answers

1. No — on switched full-duplex networks every device has a private micro-segment with separate send/receive lanes, so collisions cannot occur and CSMA/CD never engages. It belongs to the shared-medium hub era; its cousin CSMA/CA is alive in Wi-Fi, where radios must avoid collisions they cannot detect.
2. 1000 = gigabit rate; BASE = baseband signaling; LX = long-wavelength laser over fiber, i.e., single-mode reach in kilometers. Deployment: a building-to-building or campus backbone link.
3. 1.2 GB = 1,200 MB × 8 = 9,600 Mb; 4 min = 240 s; 9,600 ÷ 240 = 40 Mbps.
4. (a) 802.1 (specifically its VLAN standard — next lesson names it); (b) 802.11; (c) 802.3.
5. No — 802.3af guarantees only 12.95 W at the device (15.4 W leaves the switch; the rest is lost in the cable). Specify 802.3at (about 25 W usable) at minimum; 802.3bt if the camera adds heaters or pan-tilt motors that push the budget higher.
6. Determinism was real, but Ethernet was cheaper to buy, simpler to repair, and star-wired so one dead machine didn't threaten the ring's continuity. Economics plus resilience beat elegant scheduling — and switching later eliminated collisions anyway, removing Token Ring's core selling point.

Key terms

• IEEE 802 — the family of LAN standards; 802.3 (Ethernet), 802.11 (Wi-Fi) and 802.1 (bridging/VLANs) are the living core.
• Token Ring (802.5) — the withdrawn ring LAN where a circulating token granted permission to transmit.
• Token passing — Token Ring's access method: transmit only while holding the token.
• CSMA/CD — Ethernet's classic listen-transmit-detect-backoff access method; historical on switched full-duplex networks.
• CSMA/CA — collision avoidance: coordinate before transmitting; alive in Wi-Fi, where collisions can't be detected.
• Bandwidth — capacity of the pipe, in bits per second; not velocity.
• Throughput (Tp = Fs/Ts) — data actually delivered per second: file size (in bits!) over transfer seconds.
• B vs b — bytes versus bits; one byte = eight bits; the unit trap in every rate calculation.
• [rate]BASE[medium] — Ethernet's naming code: bandwidth, baseband signaling, medium letters (T twisted pair; S/L/E fiber reach).
• Multi-gig (2.5G/5GBASE-T) — the middle rungs added so existing Cat5e/Cat6 could exceed a gigabit without rewiring.
• PoE (802.3af/at/bt) — Power over Ethernet: roughly 13/25/71 W guaranteed at the device (15.4/30/90 W sourced by the switch); data and power on one cable.
• 802.3df-2024 / 800G — the current top of the standardized Ethernet ladder, with 1.6T in progress.

Summary

• Standards exist so parts fit: the stranded-traveler lesson, institutionalized as the IEEE 802 family.
• Three families carry 2026: 802.3 wired, 802.11 wireless, 802.1 gluing switches together; the book's "up-and-coming" 802.5/.9/.10 all died — forecast humbly.
• Ethernet beat Token Ring on cost, simplicity and star-wired resilience, not elegance.
• CSMA/CD is history on switched full-duplex networks; CSMA/CA lives wherever radios share air.
• Bandwidth is the pipe; throughput (Tp = Fs/Ts, bits not bytes) is the water you actually get — the gap is where bottlenecks hide.
• Decode any Ethernet name as rate-BASE-medium; T is twisted pair, S/L/E sketch fiber reach.
• The ladder now runs to 400/800 Gbps with 1.6T climbing — and multi-gig rungs prove economics steers engineering.
• PoE pushes up to ~71 usable watts through the data cable: copper's second modern superpower.

Next lesson

You have the standards; now step inside the switch that implements them. The module closes with MAC learning in detail, VLANs — networks drawn in software rather than copper — and the loop-protection protocol whose amber lights you have already met in Packet Tracer. One more build, and Module 3 is yours.

Sources and further study

• Al-Doori, T., Network Essentials, Chapter 7 (Ethernet Network Standards) and Chapter 3 (the Ethernet/Token Ring comparison) — the academic backbone of this lesson.
• IEEE 802.3 Ethernet Working Group — https://www.ieee802.org/3/ — the living registry of every standard decoded here.
• Ethernet Alliance, Ethernet Roadmap — https://ethernetalliance.org/technology/ethernet-roadmap/ — the ladder's current state and the climb to 1.6T.
• IEEE 802.3bt Power over Ethernet — https://www.ieee802.org/3/bt/ — the amendment behind 90 W PoE.
• Download: Ethernet and Cable Labels Reference (the one-page decoder ring for names, categories and PoE classes).