Error Correction vs Error Detection
- Networking Fundamentals & OSI Model
- TCP/IP Model
- Network Topologies
- IP Addressing & Subnetting
- Routing Algorithms & Protocols
- Switching Concepts
- Transport Layer Protocols (TCP & UDP)
- Application Layer Protocols
- Network Security & Firewalls
- Wireless Networking & Wi-Fi
- Network Address Translation (NAT)
- DNS Deep Dive
- Congestion Control & Flow Control
- Error Detection & Correction
- Network Devices
- VPN & Tunneling
- Load Balancing & CDN Networking
- Socket Programming
- Network Troubleshooting Tools
- Physical Layer & Transmission Media
- Data Link Layer & MAC Addressing
- Ethernet Protocol
- ARP (Address Resolution Protocol)
- ICMP Protocol
- Unicast, Multicast, Broadcast and Anycast
- Proxy Servers
- Port Numbers Reference
- Network Performance Metrics
- Quality of Service (QoS)
- Software-Defined Networking (SDN)
- HTTP/2 and HTTP/3 Overview
- 5G and Mobile Networks
- IoT Networking Basics
- VoIP Networking Basics
Two Different Goals
Error detection (covered by parity, checksums and CRC in this section) only tells a receiver that something went wrong. Error correction goes a step further - it can actually identify and fix the error, without needing to ask the sender to resend anything.
What Happens After Detection, Without Correction
Error detected -> data discarded -> receiver requests a retransmission -> sender resendsDetection-only schemes rely on this "detect and retransmit" pattern, which works well when retransmission is cheap and delay isn't critical - exactly the assumption TCP relies on.
How Error Correction Achieves More
Error-correcting codes add extra redundant information calculated in a way that not only flags an error, but pinpoints exactly which bit (or bits) is wrong, allowing the receiver to flip it back to the correct value itself - no retransmission required at all.
The Trade-off: More Overhead, for a Reason
| Detection only | Detection + Correction | |
|---|---|---|
| Extra data required | Less | More |
| Response to an error | Discard and request retransmission | Fix it immediately, no retransmission |
| Best suited for | Situations where retransmission is fast/cheap | Situations where retransmission is slow, expensive, or impossible |
When Paying That Extra Overhead Makes Sense
Error correction is especially valuable when retransmission is impractical - like a satellite link with several seconds of delay, or a live broadcast where "please resend that" simply isn't an option. In those cases, the extra overhead of correction is well worth avoiding a costly or impossible retransmission.