Issues in TCP Slow-Start Restart After Idle
draft-ietf-tcpimpl-restart-00

Document Type Expired Internet-Draft (tcpimpl WG)
Last updated 1998-04-10
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-tcpimpl-restart-00.txt

Abstract

This draft discusses variations in the TCP 'slow-start restart' (SSR) algorithm, and the unintended failure of some variations to properly restart in some environments. SSR is intended to avoid line-rate bursts after idle periods, where TCP accumulates permission to send in the form of ACKs, but does not consume that permission immediately. SSR's original 'restart after send is idle' is commonly implemented as 'restart after receive is idle'. The latter unintentionally fails to restart for bidirectional connections where the sender's burst is triggered by a reverse-path data packet, such as in persistent HTTP. Both the former and latter are shown to permit bursts in other circumstances. Three solutions are discussed, and their implementations evaluated. This document is a product of the LSAM project at ISI. Comments are solicited and should be addressed to the authors.

Authors

Joseph Touch (touch@isi.edu)
John Heidemann (johnh@isi.edu kemp@isi.edu)
Amy Hughes (ahughes@isi.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)