I've found it useful in the past to quote the introduction to RFC1323
(TCP Extensions for High Performance) whenever LEO constellation
proposers have confounded GEO delay with legacy stack implementations
(4K reference, say) for white papers that could easily be
misinterpreted.
RFC1323 is especially useful as it is more established than
prone-to-expiry internet drafts, is dated May 1992, predating public
knowledge of many constellations, refers to work in 1981 (aka 'before
the internet' as far as many are concerned), and even has Van
Jacobson's name on it; that makes it a garlic-scented wood-and-silver
crucifix with sharpened points in my book. Here's the relevant bit.
1. INTRODUCTION
The TCP protocol [Postel81] was designed to operate reliably over
almost any transmission medium regardless of transmission rate,
delay, corruption, duplication, or reordering of segments.
Production TCP implementations currently adapt to transfer rates in
the range of 100 bps to 10**7 bps and round-trip delays in the range
1 ms to 100 seconds. Recent work on TCP performance has shown that
TCP can work well over a variety of Internet paths, ranging from 800
Mbit/sec I/O channels to 300 bit/sec dial-up modems [Jacobson88a].
http://src.doc.ic.ac.uk/rfc/rfc1323.txt
etc. satellite netwroks are discussed further down.
L.
<[email protected]>PGP<http://www.sat-net.com/L.Wood/>+44-1483-300800x3641
On Tue, 16 Jun 1998, Vern Paxson wrote:
> Paul wrote:
>
> > I would suggest reading:
> >
> > Title : Ongoing TCP Research Related to Satellites
>
> As I think someone else pointed out, better is its companion I-D, which
> isn't about "research" but existing mechanisms:
>
> Title : Enhancing TCP Over Satellite Channels using
> Standard Mechanisms
> Author(s) : D. Glover, M. Allman
> Filename : draft-ietf-tcpsat-stand-mech-04.txt
> Pages : 15
> Date : 01-May-98
>
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-tcpsat-stand-mech-04.txt
>
> And, wearing my official IETF hat, let me state unambiguously: there's no
> IETF document that TCP/IP is limited to paths with link latencies under
> 125 msec; speaking plainly, that's absurd; and at a recent research meeting
> I was at, we debated whether TCP can work with RTTs of several minutes.
This archive was generated by hypermail 2b29 : Mon Feb 14 2000 - 16:14:43 EST