A link-layer technique that reduces the number of bits transmitted per packet by encoding, eliding or compacting protocol header fields (statefully or statelessly) so that per-packet protocol overhead on a specific link is lowered while preserving the information required for correct packet reconstruction at the far end.

Principle

Reducing header size decreases per-packet bandwidth and increases effective payload throughput on constrained links, but stateful methods require synchronized context and recovery mechanisms while stateless methods trade compression ratio for independence of per-flow state.

Demonstration

Illustrative scenario → A narrow wireless link carries frequent small update packets. A stateful compressor at the sender maintains a compact context for each flow and transmits a short compressed header; the decompressor restores full headers using its synchronized context. When a burst of packet loss desynchronizes contexts, an explicit refresh or full header is sent to reestablish correct reconstruction.

Misapplication

Assuming header compression always reduces latency and is safe on any link; this overlooks that compression adds processing delay and that stateful schemes can produce corrupted or dropped packets if compressor and decompressor lose synchronization.

Consequence

When applied appropriately, link throughput for payload increases and average per-packet overhead falls; when synchronization fails or when packets are encrypted end-to-end so headers are opaque, compression can introduce retransmissions, packet rejection, or extra control traffic to resynchronize.

Reversal

If headers are protected by end-to-end encryption (so header fields are not observable) or when CPU/latency constraints prohibit additional processing, header compression is infeasible and may worsen performance; in such cases payload compression or link provisioning must be considered instead.

Boundary

Clearly within: compacting network/transport header fields transmitted in clear on a specific link (e.g., link-layer compressor paired with a decompressor). Boundary case: compressing headers that are then encrypted on the same hop (requires careful ordering). Clearly outside: compression of payload data or application-layer content unrelated to protocol headers.

Semantic Tension

Bandwidth efficiency ↔ Operational complexity and state: higher compression ratios typically require maintained state and recovery logic, increasing implementation complexity and fragility on lossy links.

Synthesis

Header compression is a bandwidth-efficiency technique whose net benefit depends on the link's error characteristics, the availability of observable header fields, and the operational cost of maintaining and recovering compressor state.