1 / 7

TCP and SCTP RTO Restart draft-ietf-tcpm-rtorestart-01 TCPM WG IETF-88

TCP and SCTP RTO Restart draft-ietf-tcpm-rtorestart-01 TCPM WG IETF-88. P. Hurtig, A. Brunstrom, A. Petlund , M. Welzl. RTO Restart. As the RTO timer is restarted on an incoming ACK (RFC 6298, RFC 4960), the effective RTO often becomes RTO = RTO + t Where t ≈ RTT [+ delACK ]

benito
Download Presentation

TCP and SCTP RTO Restart draft-ietf-tcpm-rtorestart-01 TCPM WG IETF-88

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TCP and SCTP RTO Restartdraft-ietf-tcpm-rtorestart-01TCPM WGIETF-88 P. Hurtig, A. Brunstrom, A. Petlund, M. Welzl

  2. RTO Restart • As the RTO timer is restarted on an incoming ACK (RFC 6298, RFC 4960), the effective RTO often becomesRTO = RTO + t • Where t ≈ RTT [+delACK] • RTO restart adjusts the RTO so that retransmissions are performed after exactly RTO seconds • The modified restart is only used when • the number of outstanding segments < 4; • and there is no unsent data ready for transmission. • Thus, only flows incapable of FR can use modified RTO restart

  3. Updatesto draft (1) • New section that discusses the applicability of and problems related to the RTO restart mechanism • Reduces the loss detection time and thereby increases the risk of spurious timeouts in some situations • Impact of spurious RTO is negligible for short flows and thin streams • Spurious RTO can be a problem for flows with multiple bursts, as cwndis reduced • Further experience related to spurious RTOs required to move specification from experimental to proposed standard

  4. Updatesto draft (2) • Removed the possibility for a connection limited by the receiver's advertised window to use RTO restart • Gain for this scenario unclear • Decreasing the risk of spurious timeouts

  5. Updatesto draft (3) • Improved wording throughout the document • Updates to the text that describe RTO restart's relation to TLP • Acknowledgments added

  6. Implementation • Updated for the 3.12 Linux kernel • http://riteproject.eu/projects/wp1-end-systems-and-applications/rto-restart/

  7. ?

More Related