Re: Re[2]: I-D ACTION:draft-ietf-tcpsat-res-issues-02.txt

From: Joe Touch (touch@ISI.EDU)
Date: Thu Mar 26 1998 - 13:37:19 EST


> From: gnnakanishi@CCGATE.HAC.COM
> Date: Thu, 26 Mar 98 10:00:20 PST8
> To: mallman@lerc.nasa.gov, halsem@intelsat.int
> Cc: tcp-over-satellite@achtung.sp.trw.com, travis@clark.net,
> jejustiss@CCGATE.HAC.COM, jhmurakawa@CCGATE.HAC.COM,
> kfmatsunaga@CCGATE.HAC.COM, jkigawa@CCGATE.HAC.COM,
> rjbenhabib@CCGATE.HAC.COM
> Subject: Re[2]: I-D ACTION:draft-ietf-tcpsat-res-issues-02.txt
>
> I've been following the multitude of postings on spoofing. Here are some of my
> personal opinions.
>
> 1) In my opinion, the charter of the group should look at any issues related to
> the performance of TCP over satellite. This includes things like spoofing
> which, although is not a TCP mechanism, has an effect on TCP performance.

Rather than asking whether this is "TCP", is this "satellite"?

There might be 'general TCP performance issues' that should be
listed, but it also might be useful to tag them as 'non-satellite specific',
so others will take them into consideration as well.

I.e., to label issues as:

SAT-SPECIFIC - arises uniquely in satellite

SAT-AMPLIFIED - arises many places, and affects satellite particularly badly

GENERAL - arises many places, not satellite any more than any others,
                but is also to be considered

(?)

Joe



This archive was generated by hypermail 2b29 : Mon Feb 14 2000 - 16:14:37 EST