ACK Spacing for High Delay-Bandwidth Paths with Insufficient Buffering
draft-rfced-info-partridge-01

Document Type Expired Internet-Draft (individual)
Author Craig Partridge 
Last updated 1998-10-09
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text 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-rfced-info-partridge-01.txt

Abstract

Suppose you want TCP implementations to be able to fill a 155 Mb/s path. Further suppose that the path includes a satellite in a geosynchronous orbit, so the round trip delay through the path is at least 500 ms, and the delay-bandwidth product is 9.7 megabytes or more. If we further assume the TCP implementations support TCP Large Windows and PAWS (many do), so they can manage 9.7 MB TCP window, then we can be sure the TCP will eventually start sending at full path rate (unless the satellite channel is very lossy). But it may take a long time to get the TCP up to full speed.

Authors

Craig Partridge (craig@aland.bbn.com)

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