RE: [pilc] interoperability issue with TCP PEP
"Keith L. Scott" <kscott@mitre.org> Wed, 28 July 2004 16:01 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 MAA09731 for <pilc-archive@lists.ietf.org>; Wed, 28 Jul 2004 12:01:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpqlA-0007iG-CV; Wed, 28 Jul 2004 11:54:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpqbX-00068Q-Lz for pilc@megatron.ietf.org; Wed, 28 Jul 2004 11:44:32 -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 LAA08378 for <pilc@ietf.org>; Wed, 28 Jul 2004 11:44:29 -0400 (EDT)
Received: from smtpproxy2.mitre.org ([192.80.55.71] helo=smtp-mclean.mitre.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpqdN-0000ay-TC for pilc@ietf.org; Wed, 28 Jul 2004 11:46:26 -0400
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i6SFiPe14806 for <pilc@ietf.org>; Wed, 28 Jul 2004 11:44:25 -0400
Received: from mailsrv2a (mailsrv2a.mitre.org [129.83.221.56]) by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i6SFiN314718; Wed, 28 Jul 2004 11:44:24 -0400
Received: from mm106846pc (mm106846-pc.mitre.org [128.29.3.80]) by mailsrv2a.mitre.org (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTPA id <0I1K00FKIJPZTK@mailsrv2a.mitre.org>; Wed, 28 Jul 2004 11:44:23 -0400 (EDT)
Date: Wed, 28 Jul 2004 11:44:22 -0400
From: "Keith L. Scott" <kscott@mitre.org>
Subject: RE: [pilc] interoperability issue with TCP PEP
In-reply-to: <004801c47497$e72100c0$4703080a@future.futsoft.com>
To: lakshmips@future.futsoft.com, pilc@ietf.org
Message-id: <0I1K00FKJJPZTK@mailsrv2a.mitre.org>
Organization: The MITRE Corporation
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Thread-index: AcR0mapZmCMcobslQay2PwBSBDwSlAAGNaKw
X-Spam-Score: 0.2 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: 7bit
Cc: sis-scps-interest@mailman.ccsds.org
X-BeenThere: pilc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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
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/
- [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