RE: interoperability issue with TCP PEP

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: [email protected] [mailto:[email protected]]On Behalf Of
Keith L. Scott
Sent: Wednesday, 28 July 2004 9:14 PM
To: [email protected]; [email protected]
Cc: [email protected]
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: [email protected] [mailto:[email protected]] On
>Behalf Of Lakshmi Priya
>Sent: Wednesday, July 28, 2004 7:42 AM
>To: [email protected]
>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
>[email protected]
>https://www1.ietf.org/mailman/listinfo/pilc
>http://www.ietf.org/html.charters/pilc-charter.html
>http://pilc.grc.nasa.gov/
>


_______________________________________________
pilc mailing list
[email protected]
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
[email protected]
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/