TCP Cubic - Yale University：TCP三次-耶鲁大学.ppt

Then based on TCP, when the sender detects that there is a packet loss, Fast retransmission would be triggered which allows it to directly send the lost segment to the receiver possibly preventing retransmission timeout. * TCP uses RTT estimate to update retransmission timeout (RTO), In this example, when the lost segment is retransmitted, RTT is 262ms and RTO is 290ms. However, TCP does not update RTO based on duplicate ACKs. Notice that the duplicate ACKs are generated by the reception of the data packets sent AFTER the lost segment. * However, given that the RTT is growing and by the time the ACK of the retransmitted segment is back, RTT has increased to 356ms, while RTO is not updated. Since RTT is larger than RTO now, there is unexpected retransmission timeout. It is called unexpected because the purpose of fast retransmission is to prevent such timeout to happen. After timeout, the congestion window would drop to 1 segment size, triggering slow start, which hurt TCP performance * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * The vertical gap between data and ACK curve indicates the bytes in flight And we clearly see that the bytes in flight is growing as the downloading proceeds. * We observe a packet loss at time 1 second * TCP Cubic cwnd = C( t – K)3 + Wmax Wmax = cwnd before last reduction βmultiplicative decrease factor C scaling factor t is the time elapsed since last window reduction TCP CUBIC Packet loss event Time Steady State Behavior Max Probing Wmax Around Wmax, window growth almost becomes zero Fast growth upon reduction Cubic starts probing for more Bandwidth TCP Cubic Advantages Good RTT fairness Growth dominated by t, competing flows have same t after synchronized packet loss Real-time dependent Similar to BIC but linear increases are time dependent Does not depend on ACK’s like TCP/ Reno Scalability Cubic increases window to Wmax (or its vicinity) quickly and keeps it there longer TCP Cubic Drawbacks Slow Converge