A network engineer is troubleshooting latency spikes in a real-time financial market data feed. Packet analysis reveals that when minor packet loss occurs on the WAN link, the receiving application experiences head-of-line blocking, holding back newly arrived live data while waiting for lost segments to be retransmitted. The application developers require a transport solution that delivers incoming data segments immediately to the application layer upon arrival, accepting unacknowledged data loss in exchange for minimal overhead and zero retransmission delay. Which transport layer design recommendation satisfies these requirements?
- Migrate the streaming protocol to UDP and handle any required packet ordering at the application layer, reducing header overhead from 20 bytes to 8 bytes and eliminating TCP retransmission buffer delays.Cevap
- BRetain TCP as the transport protocol but configure Selective Acknowledgment (SACK) to force the receiving host to pass out-of-order segments to the application before missing segments arrive.
- CRetain TCP but set the TCP receive window size to 0 bytes to bypass transport-layer buffering and process incoming segments immediately.
- DMigrate the application to UDP while retaining the standard 20-byte transport header structure to maintain built-in segment sequence numbers without acknowledgment overhead.
Cevap
Migrating the streaming protocol to UDP and handling any required packet ordering at the application layer satisfies the requirements by reducing header overhead from 20 bytes to 8 bytes and eliminating head-of-line blocking.
Migrating to UDP removes transport-layer retransmissions and stream sequencing delays. UDP operates connectionlessly with a fixed 8-byte header overhead (compared to TCP's minimum 20-byte header), allowing out-of-order packets to be delivered to the application immediately upon arrival without head-of-line blocking.
Adım Adım Çözüm
Anahtar Kavram
TCP vs UDP Transport Characteristics and Header Overhead