1. 1 F-RTO Update Pasi Sarolahti Markku Kojo Kazunori Yamamoto Max Hata IETF-72 / TCPM / Dublin, Ireland / July 28, 2008

2. 2 Last changes (from -01) The execution of the F-RTO algorithm is now not allowed if an earlier RTO recovery is underway, except in case the retransmission timer expires multiple times for the same segment Applies both basic and SACK-enhanced F-RTO algorithm Addresses the issue raised by Murari Sridharan This is for the same reason why F-RTO was not allowed in RFC 4138, if an earlier SACK-based fast recovery is underway In both cases several retransmitted segments may be in flight when the retransmission timer expires and ACKs for these retransmissions may lead the TCP sender to falsely declare the timeout spurious General editing Includes suggestions by Alfred Hönes

3. 3 Current Status The draft is currently in WGLC Will last until August 8, 2008