TCP Flow Control for Fast Startup Schemes
draft-scharf-tcpm-flow-control-quick-start-00

Document Type Expired Internet-Draft (individual)
Last updated 2008-07-07
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-scharf-tcpm-flow-control-quick-start-00.txt

Abstract

This document describes extensions for the flow control of the Transmission Control Protocol (TCP) that avoid interactions with fast startup congestion control mechanisms, in particular the Quick-Start TCP extension. Quick-Start is an optional TCP extension that allows to start data transfers with a large congestion window, using feedback of the routers along the path. This can avoid the time consuming Slow-Start, provided that the TCP flow control is not a limiting factor. There are two potential interactions between the TCP flow control and congestion control schemes without the standard Slow-Start: First, receivers might not allocate a sufficiently large buffer space after connection setup, or they may advertise a receive window implicitly assuming the Slow-Start behavior on the sender side. This document therefore provides guidelines for buffer allocation in hosts supporting the Quick-Start extension. Second, the TCP receive window scaling mechanism can prevent fast startups immediately after the initial three-way handshake connection setup. This document describes a simple solution to overcome this problem.

Authors

Michael Scharf (michael.scharf@ikr.uni-stuttgart.de)
Sally Floyd (floyd@icir.org)
Pasi Sarolahti (pasi.sarolahti@iki.fi)

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