RE: [pilc] interoperability issue with TCP PEP
"Lakshmi Priya" <lakshmips@future.futsoft.com> Mon, 02 August 2004 05:12 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00068 for <pilc-archive@lists.ietf.org>; Mon, 2 Aug 2004 01:12:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrV3l-000679-Cy; Mon, 02 Aug 2004 01:08:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrUww-0003FT-3q for pilc@megatron.ietf.org; Mon, 02 Aug 2004 01:01:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29658 for <pilc@ietf.org>; Mon, 2 Aug 2004 01:01:25 -0400 (EDT)
Received: from mail1.future.futsoft.com ([203.197.138.222]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrUzf-0007Nu-PA for pilc@ietf.org; Mon, 02 Aug 2004 01:04:19 -0400
Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by mail1.future.futsoft.com (Content Technologies SMTPRS 4.3.12) with ESMTP id <T6b2b752b46cbc58ade3bc@mail1.future.futsoft.com>; Mon, 2 Aug 2004 10:29:59 +0530
Received: from lakshmips (lakshmips.future.futsoft.com [10.8.3.71]) by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id i7250cZ23836; Mon , 2 Aug 2004 10:30:39 +0530
From: Lakshmi Priya <lakshmips@future.futsoft.com>
To: "'Keith L. Scott'" <kscott@mitre.org>, pilc@ietf.org
Subject: RE: [pilc] interoperability issue with TCP PEP
Date: Mon, 02 Aug 2004 10:29:23 +0530
Message-ID: <001e01c4784d$7ac40c60$4703080a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To: <0I1K00FKJJPZTK@mailsrv2a.mitre.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Content-Transfer-Encoding: 7bit
Cc: sis-scps-interest@mailman.ccsds.org
X-BeenThere: pilc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: lakshmips@future.futsoft.com
List-Id: Performance Implications of Link Characteristics IETF Working Group <pilc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pilc>, <mailto:pilc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pilc@ietf.org>
List-Help: <mailto:pilc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pilc>, <mailto:pilc-request@ietf.org?subject=subscribe>
Sender: pilc-bounces@ietf.org
Errors-To: pilc-bounces@ietf.org
Content-Transfer-Encoding: 7bit
Keith and John thanks for the response. The SCPS-TP as mentioned would surely help in having a interoperable transport protocol over satellite. But yet it does not suggest any ways to interoperate PEP i.e. the means of informing the other PEP node (in a split connection)of the end host session information which has been spoofed. Hope the DVB-RCS standard would help clarify on these aspects. regards, Lakshmi Priya -----Original Message----- From: pilc-bounces@ietf.org [mailto:pilc-bounces@ietf.org]On Behalf Of Keith L. Scott Sent: Wednesday, 28 July 2004 9:14 PM To: lakshmips@future.futsoft.com; pilc@ietf.org Cc: sis-scps-interest@mailman.ccsds.org Subject: RE: [pilc] interoperability issue with TCP PEP Lakshmi, It is entirely possible for PEPs made by different vendors to interoperate, provided the vendors implement a common standard; and yes, there _is_ a standard for how the information is carried across the satellite link. The Space Communications Protocol Standards: Transport Protocol (SCPS-TP, also sometimes referred to as TCP tranquility) defines a set of TCP options that can improve TCP performance in stressed environments, including satellite communications. PEP products that implement these options are available from a number of vendors, and should interoperate if they all conform to the specification. There is also a freely available reference implementation of the SCPS protocols that includes a PEP application that is available by sending mail to the point of contact listed at http://www.scps.org. Tranquility is completely backward-compatible with other TCP implementations; all of the Tranquility-specific functionality is negotiated during the SYN exchange. By using different settings for the terrestrial and satcom sides of the PEPs, they can dramatically improve performance over the satcom link. There is currently no implementation that I know of that does private, out-of-band signaling between the PEPs, though I can envision uses for such signaling. I'd be happy to answer any other questions you have or to point you at some vendors. The SCPS-TP protocol spec is available from http://www.ccsds.org/CCSDS/documents/714x0b1.pdf Best regards, --keith >-----Original Message----- >From: pilc-bounces@ietf.org [mailto:pilc-bounces@ietf.org] On >Behalf Of Lakshmi Priya >Sent: Wednesday, July 28, 2004 7:42 AM >To: pilc@ietf.org >Subject: [pilc] interoperability issue with TCP PEP > > >hi, > > Would it be possible to implement PEP such that it is >interoperable >with other PEP implementations? >That is, in a split connection, is it possible to have 2 >different vendor >implementations running on either end of satellite link PEP >nodes? Are there >any such implementations? > > Since there are no standards to the way in which the end host >information is carried over the satlink after spoofing, I >guess this would >not be possible. There could also exist many other proprietary control >packets. Any inputs in this regard is welcome. > >thanks and regards, >Lakshmi Priya > > > >*************************************************************** >************ >This message is proprietary to Future Software Limited (FSL) >and is intended solely for the use of the individual to whom it >is addressed. It may contain privileged or confidential information >and should not be circulated or used for any purpose other than for >what it is intended. > >If you have received this message in error, please notify the >originator immediately. If you are not the intended recipient, >you are notified that you are strictly prohibited from using, >copying, altering, or disclosing the contents of this message. >FSL accepts no responsibility for loss or damage arising from >the use of the information transmitted by this email including >damage from virus. >*************************************************************** >************ > > >_______________________________________________ >pilc mailing list >pilc@ietf.org >https://www1.ietf.org/mailman/listinfo/pilc >http://www.ietf.org/html.charters/pilc-charter.html >http://pilc.grc.nasa.gov/ > _______________________________________________ pilc mailing list pilc@ietf.org https://www1.ietf.org/mailman/listinfo/pilc http://www.ietf.org/html.charters/pilc-charter.html http://pilc.grc.nasa.gov/ *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. *************************************************************************** _______________________________________________ pilc mailing list pilc@ietf.org https://www1.ietf.org/mailman/listinfo/pilc http://www.ietf.org/html.charters/pilc-charter.html http://pilc.grc.nasa.gov/
- [pilc] tcppep Lakshmi Priya
- Re: [pilc] tcppep John Border
- RE: [pilc] tcppep Lakshmi Priya
- Re: [pilc] tcppep Joe Touch
- [pilc] interoperability issue with TCP PEP Lakshmi Priya
- RE: [pilc] interoperability issue with TCP PEP Keith L. Scott
- Re: [pilc] interoperability issue with TCP PEP John Border
- RE: [pilc] interoperability issue with TCP PEP Lakshmi Priya
- Re: [pilc] interoperability issue with TCP PEP Gorry Fairhurst