Which IPv4 issue is described as overhead related to checksum calculations?

Which IPv4 issue is described as overhead related to checksum calculations?

• A. Overhead related to Checksum calculations
• B. Fixed header size reduces overhead
• C. IPv6 header length
• D. 128-bit address exhaustion

Answer: (A)

In IPv4, every packet carries a 16-bit header checksum that validates the integrity of the header itself. As the packet moves through routers, fields in the header (such as the TTL) are modified, so the checksum must be recalculated for each hop. This per-hop recalculation adds processing overhead across the network, making checksum handling a notable source of overhead in IPv4 traffic. This is a key reason IPv6 removed the header checksum, shifting integrity checks to end-to-end transport-layer checksums instead. The other options don’t describe this overhead: one references a general idea of header size reducing overhead, another points to IPv6 header length, and another talks about address exhaustion, none of which capture the per-hop checksum processing burden in IPv4.

In IPv4, every packet carries a 16-bit header checksum that validates the integrity of the header itself. As the packet moves through routers, fields in the header (such as the TTL) are modified, so the checksum must be recalculated for each hop. This per-hop recalculation adds processing overhead across the network, making checksum handling a notable source of overhead in IPv4 traffic. This is a key reason IPv6 removed the header checksum, shifting integrity checks to end-to-end transport-layer checksums instead. The other options don’t describe this overhead: one references a general idea of header size reducing overhead, another points to IPv6 header length, and another talks about address exhaustion, none of which capture the per-hop checksum processing burden in IPv4.