Re: transparent tcp improvements

Joseph Ishac <jishac@grc.nasa.gov> Mon, 15 April 2002 13:49 UTC

Date: Mon, 15 Apr 2002 09:49:25 -0400
From: Joseph Ishac <jishac@grc.nasa.gov>
To: karl.jonas@ieee.org
Cc: tcpsat@grc.nasa.gov
Subject: Re: transparent tcp improvements
Message-ID: <20020415094925.A12936@sunfire.grc.nasa.gov>
Reply-To: Joseph Ishac <jishac@grc.nasa.gov>
References: <OHEFJNMPOIMBPIIHGBDCCEMMCFAA.karl.jonas@fokus.fhg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OHEFJNMPOIMBPIIHGBDCCEMMCFAA.karl.jonas@fokus.fhg.de>; from karl.jonas@fokus.fhg.de on Mon, Apr 15, 2002 at 10:10:35AM +0200
Sender: owner-tcpsat@grc.nasa.gov
Precedence: bulk
Status: RO
Content-Length: 711
Lines: 16

> The idea is that tcp's slow start / congestion avoidance mechanism
> will handle the situation in the terrestrial nw correctly, and
> transmission will not suffer from the long delay link.
> 
> The 'tcp box' must monitor tcp sesssions, generate acks towards the
> sender (possibly drop acks from the mobile?), and of course buffer
> tcp data that it has ack'ed to the sender, but which has not been
> ack'ed by the mobile yet.

This is "TCP Spoofing" as described in RFC 3135 on PEP's.  Also, a Milcom paper
on the subject http://roland.grc.nasa.gov/~jishac/papers/2001/TCP_Spoofing.pdf
(please excuse the shameless self plug :)

I strongly suggest reading RFC 3135 if you have not done so already.

- Joseph

transparent tcp improvements Karl Jonas
Re: transparent tcp improvements Mike Jagdis
Re: transparent tcp improvements David Carek
Re: transparent tcp improvements Joseph Ishac