From mailman-bounces@ietf.org  Sun Aug  1 06:52:24 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11291
	for <pilc-archive@lists.ietf.org>; Sun, 1 Aug 2004 06:52:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrCVB-0007uf-TW
	for pilc-archive@lists.ietf.org; Sun, 01 Aug 2004 05:19:33 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: pilc-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.16077.1091351086.10663.mailman@lists.ietf.org>
Date: Sun, 01 Aug 2004 05:04:46 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for pilc-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
pilc@ietf.org                            HsCZ      
https://www1.ietf.org/mailman/options/pilc/pilc-archive%40lists.ietf.org


From pilc-bounces@ietf.org  Sun Aug  1 23:43:24 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26047
	for <pilc-archive@lists.ietf.org>; Sun, 1 Aug 2004 23:43:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrTda-0006Fw-1y; Sun, 01 Aug 2004 23:37:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrTYu-0003ou-3j
	for pilc@megatron.ietf.org; Sun, 01 Aug 2004 23:32:34 -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 XAA25511
	for <pilc@ietf.org>; Sun, 1 Aug 2004 23:32:29 -0400 (EDT)
Received: from hnse2.hns.com ([208.236.67.201])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrTbd-00066O-Ap
	for pilc@ietf.org; Sun, 01 Aug 2004 23:35:24 -0400
Received: from excore8.hns.com (excore8.hns.com [139.85.52.126])
	by hnse2.hns.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id
	i723VV3C028436
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 1 Aug 2004 23:31:31 -0400 (EDT)
Received: from hns.com (rasnvpn53.hns.com [139.85.221.136])
	by excore8.hns.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id
	i723VGQg004345; Sun, 1 Aug 2004 23:31:19 -0400 (EDT)
Message-ID: <410DB583.9090004@hns.com>
Date: Sun, 01 Aug 2004 23:31:15 -0400
From: John Border <border@hns.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: lakshmips@future.futsoft.com
Subject: Re: [pilc] interoperability issue with TCP PEP
References: <0I1K00FKJJPZTK@mailsrv2a.mitre.org>
In-Reply-To: <0I1K00FKJJPZTK@mailsrv2a.mitre.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Filtered: Sendmail Attachment Filter v2.6.0 hnse2.hns.com i723VV3C028436
X-AntiVirus: Sendmail Anti-Virus Filter hnse2.hns.com 4.3.20 4382
	i723VV3C028436
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Content-Transfer-Encoding: 7bit
Cc: sis-scps-interest@mailman.ccsds.org, ip-dvb@erg.abdn.ac.uk, pilc@ietf.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


DVB-RCS, via SatLabs, is currently looking into standardizing a minimum 
interoperable PEP.  Not sure of the current status of the effort...

Keith L. Scott wrote:

>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 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/


From pilc-bounces@ietf.org  Mon Aug  2 01:12:49 2004
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, 2 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/


From pilc-bounces@ietf.org  Tue Aug  3 02:02:44 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06768
	for <pilc-archive@lists.ietf.org>; Tue, 3 Aug 2004 02:02:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrsFn-0006H1-0V; Tue, 03 Aug 2004 01:54:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrsAQ-0003aN-UB
	for pilc@megatron.ietf.org; Tue, 03 Aug 2004 01:48:57 -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 BAA03802
	for <pilc@ietf.org>; Tue, 3 Aug 2004 01:48:51 -0400 (EDT)
Received: from mail1.future.futsoft.com ([203.197.138.222])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrsDN-0003xE-Gl
	for pilc@ietf.org; Tue, 03 Aug 2004 01:51:59 -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 <T6b30c702fccbc58ade204@mail1.future.futsoft.com>; Tue, 3 Aug 2004 
	11:17:29 +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 i735m7Z25089;
	Tue , 3 Aug 2004 11:18:08 +0530
From: "Lakshmi Priya" <lakshmips@future.futsoft.com>
To: "'Eric Travis'" <travis@globalprotocols.com>,
        <sis-scps-interest@mailman.ccsds.org>, <pilc@ietf.org>
Subject: RE: [pilc] interoperability issue with TCP PEP
Date: Tue, 3 Aug 2004 11:16:53 +0530
Message-ID: <001b01c4791d$490b3420$4703080a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
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)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
In-Reply-To: <410E6DBB.4060807@globalprotocols.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: 7bit
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

hi,
   Thanks, Eric.

Guess I was not very clear with my question.
Consider the scenario below:

H1-P1 -> terrestial link
P1--P2 -> satellite link
H2-P2 -> terrestial link

End host	PEP node	PEP node	End host

H1 ----------P1------------P2----------H2

In a split PEP connection there would be 3 TCP connections (between the
nodes).
If PEP is transparent to end user the session properties (atleast the 4
tuples H1,H2,srcport1,dstport1)
should be the same for the TCP sessions between H1-P1 and P2-H2.Both these
sessions would ideally be spoofed with session tuples -
H1,H2,srcport1,dstport1 as expected by end users H1 and H2. This can be done
in many ways, since there is no specification. The information of the
session just needs to be passed from P1 to P2.

Eric, as per your reply
>> It seems that an ideally constructed transport proxy would leave all the
relevant information (obviously port numbers, but also bidirectional
sequence
space, urgent pointers, I suppose the Push flag and any IP header service
markings) undisturbed.

      It means the P1-P2 session should also retain the same properties as
the end host sessions. This is one of the methods of passing the
information. But this is not standardised. One could use a totally new set
of properties over P1-P2, may be even a different protocol, and yet pass on
the session information from P1 to P2 for the terrestial sessions using any
other control packet.

In this aspect, if P1 and P2 are 2 different implementations, I foresee an
interoperability issue.
Please correct me if I am wrong.

regards,
Lakshmi



-----Original Message-----
From: Eric Travis [mailto:travis@globalprotocols.com]
Sent: Monday, 2 August 2004 10:07 PM
To: lakshmips@future.futsoft.com
Cc: sis-scps-interest@mailman.ccsds.org
Subject: RE: [pilc] interoperability issue with TCP PEP


Lakshmi,

This is interesting:

>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.
>
>
What sort of information do you have in mind, and in what manner would
the other node make use of this information?

It seems that an ideally constructed transport proxy would leave all the
relevant information (obviously port numbers, but also bidirectional
sequence
space, urgent pointers, I suppose the Push flag and any IP header service
markings) undisturbed.

While an intermediate proxy may very well [need to] resegment the data
in the
flow,  this would be transparent to the ultimate end-system anyway it
isn't clear
if this activity needs to be conveyed to the peer-proxy.

Is there some other information that you had in mind?

Eric



***************************************************************************
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/


From pilc-bounces@ietf.org  Tue Aug  3 02:57:58 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20615
	for <pilc-archive@lists.ietf.org>; Tue, 3 Aug 2004 02:57:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Brt8v-0001Ti-4F; Tue, 03 Aug 2004 02:51:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Brt6W-0000W5-Si
	for pilc@megatron.ietf.org; Tue, 03 Aug 2004 02:48:57 -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 CAA20348
	for <pilc@ietf.org>; Tue, 3 Aug 2004 02:48:54 -0400 (EDT)
Received: from h-68-167-218-35.nycmny83.covad.net ([68.167.218.35]
	helo=mail.hotlens.com) by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1Brt9T-0004jo-QC
	for pilc@ietf.org; Tue, 03 Aug 2004 02:52:03 -0400
Message-ID: <001e01c4784d$7ac40c60$4703080a@future.futsoft.com>
Date: Mon, 2 Aug 2004 10:29:23 +0530
From: "Lakshmi Priya" <lakshmips@future.futsoft.com>
To: "'Keith L. Scott'" <kscott@mitre.org>, <pilc@ietf.org>
Subject: [Sis-SCPS-INTEREST] RE: [pilc] interoperability issue with TCP PEP
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-SpamKiller-Forwarded: Y
X-GCMulti: 1
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
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.
***************************************************************************


_______________________________________________
Sis-SCPS-INTEREST mailing list
Sis-SCPS-INTEREST@mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-scps-interest

_______________________________________________
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/


From pilc-bounces@ietf.org  Wed Aug  4 19:11:13 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18060
	for <pilc-archive@lists.ietf.org>; Wed, 4 Aug 2004 19:11:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsUrC-0005ln-Bu; Wed, 04 Aug 2004 19:07:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsUjS-0004bE-Tr
	for pilc@megatron.ietf.org; Wed, 04 Aug 2004 18:59:41 -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 SAA17500
	for <pilc@ietf.org>; Wed, 4 Aug 2004 18:59:35 -0400 (EDT)
Received: from mavis.erg.abdn.ac.uk ([139.133.204.77] helo=erg.abdn.ac.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsUmp-00027r-QE
	for pilc@ietf.org; Wed, 04 Aug 2004 19:03:08 -0400
Received: from [130.129.129.23] (opene-130-129-129-23.ietf60.ietf.org
	[130.129.129.23]) (authenticated bits=0)
	by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i74Mgl1G019688
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT);
	Wed, 4 Aug 2004 23:42:52 +0100 (BST)
User-Agent: Microsoft-Entourage/11.0.0.040405
Date: Wed, 04 Aug 2004 15:42:43 -0700
Subject: Re: [pilc] interoperability issue with TCP PEP
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
To: <ipdvb@erg.abdn.ac.uk>, <lakshmips@future.futsoft.com>
Message-ID: <BD36B473.D47%gorry@erg.abdn.ac.uk>
In-Reply-To: <410DB583.9090004@hns.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
X-ERG-MailScanner-To: ip-dvb@erg.abdn.ac.uk, ipdvb@erg.abdn.ac.uk,
	lakshmips@future.futsoft.com, pilc@ietf.org,
	sis-scps-interest@mailman.ccsds.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: c0aa019322dfce838bd8604f5a841b57
Content-Transfer-Encoding: 7bit
Cc: sis-scps-interest@mailman.ccsds.org, ip-dvb@erg.abdn.ac.uk, pilc@ietf.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


My take on this was the general story is that there have been a series of
meetings organised to understand the issues in producing inter-operable
PEPs, and the related issues of where NAT, IPSEC, etc are used and their
relation to DVB-RCS network scenarios.
 
SatLabs are considering a phased approach, looking for a short-term solution
providing basic PEP functions appropriate to some scenarios for DVB-RCS
(focussed on web browsing). They may also consider a more complete and
powerful long-term solution. Initial effort will probably be focussed on the
short term, looking at:

 - TCP with a split to a modified TCP transport layer (SCPS?)
 - a very light session layer if required to configure the two end points
 - optional web pre-fetching mechanisms in the application layer
 
I believe the result of their last meeting was that this work is to progress
in the months ahead.

Perhaps a member of Satlabs can give a more authorative status report?

Gorry
(speaking on behalf of no-one in particular)

-----------
On 1/8/04 8:31 pm, "John Border" <border@hns.com> wrote:

> 
> DVB-RCS, via SatLabs, is currently looking into standardizing a minimum
> interoperable PEP.  Not sure of the current status of the effort...
> 
> Keith L. Scott wrote:
> 
>> 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/
>>  
>> 
> 
Looks good to me.  I would add an "optional"  before the "web
prefetching".  I am not sure how much to say on timing or
actual outcome.

Cheers,
Joerg

Gorry Fairhurst wrote:

> See if you like this - or not, and I'll post it.
> 
> Gorry
> 
> ------
> 
> My take on this was the general story is that there have been a series of
> meetings organised to understand the issues in producing inter-operable
> PEPs, and the related issues of where NAT, IPSEC, etc are used and their
> relation to DVB-RCS network scenarios.
> 
> SatLabs are considering a phased approach, looking for a short-term solution
> providing basic PEP functions appropriate to some scenarios for DVB-RCS
> (focussed on web browsing). They may also consider a more complete and
> powerful long-term solution. Initial effort will probably be focussed on the
> short term, looking at:
> 
> - TCP with a split to a modified TCP transport layer (SCPS?)
> - a very light session layer if required to configure the two end points
> - web pre-fetching mechanisms in the application layer
> 
> I believe the result of their last meeting was that this work is to progress
> in the months ahead.
> 
> Perhaps a member of Satlabs can give a more authorative status report?
> 
> Gorry
> (speaking on behalf of no-one in particular)
> 
> On 1/8/04 8:31 pm, "John Border" <border@hns.com> wrote:
> 
> 
>>DVB-RCS, via SatLabs, is currently looking into standardizing a minimum
>>interoperable PEP.  Not sure of the current status of the effort...
>>
>>Keith L. Scott wrote:
>>
>>
>>>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 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/


From pilc-bounces@ietf.org  Fri Aug  6 14:00:41 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14325
	for <pilc-archive@lists.ietf.org>; Fri, 6 Aug 2004 14:00:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bt8yB-0006Nx-IK; Fri, 06 Aug 2004 13:57:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bt8tG-0005El-2b
	for pilc@megatron.ietf.org; Fri, 06 Aug 2004 13:52: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 NAA13922
	for <pilc@ietf.org>; Fri, 6 Aug 2004 13:52:23 -0400 (EDT)
Received: from h-68-167-218-35.nycmny83.covad.net ([68.167.218.35]
	helo=mail.hotlens.com) by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1Bt8wu-0001vU-US
	for pilc@ietf.org; Fri, 06 Aug 2004 13:56:17 -0400
Message-ID: <001b01c4791d$490b3420$4703080a@future.futsoft.com>
Date: Tue, 3 Aug 2004 11:16:53 +0530
From: "Lakshmi Priya" <lakshmips@future.futsoft.com>
To: "'Eric Travis'" <travis@globalprotocols.com>,
        <sis-scps-interest@mailman.ccsds.org>, <pilc@ietf.org>
Subject: [Sis-SCPS-INTEREST] RE: [pilc] interoperability issue with TCP PEP
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-SpamKiller-Forwarded: Y
X-GCMulti: 1
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: 7bit
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

hi,
   Thanks, Eric.

Guess I was not very clear with my question.
Consider the scenario below:

H1-P1 -> terrestial link
P1--P2 -> satellite link
H2-P2 -> terrestial link

End host	PEP node	PEP node	End host

H1 ----------P1------------P2----------H2

In a split PEP connection there would be 3 TCP connections (between the
nodes).
If PEP is transparent to end user the session properties (atleast the 4
tuples H1,H2,srcport1,dstport1)
should be the same for the TCP sessions between H1-P1 and P2-H2.Both these
sessions would ideally be spoofed with session tuples -
H1,H2,srcport1,dstport1 as expected by end users H1 and H2. This can be done
in many ways, since there is no specification. The information of the
session just needs to be passed from P1 to P2.

Eric, as per your reply
>> It seems that an ideally constructed transport proxy would leave all the
relevant information (obviously port numbers, but also bidirectional
sequence
space, urgent pointers, I suppose the Push flag and any IP header service
markings) undisturbed.

      It means the P1-P2 session should also retain the same properties as
the end host sessions. This is one of the methods of passing the
information. But this is not standardised. One could use a totally new set
of properties over P1-P2, may be even a different protocol, and yet pass on
the session information from P1 to P2 for the terrestial sessions using any
other control packet.

In this aspect, if P1 and P2 are 2 different implementations, I foresee an
interoperability issue.
Please correct me if I am wrong.

regards,
Lakshmi



-----Original Message-----
From: Eric Travis [mailto:travis@globalprotocols.com]
Sent: Monday, 2 August 2004 10:07 PM
To: lakshmips@future.futsoft.com
Cc: sis-scps-interest@mailman.ccsds.org
Subject: RE: [pilc] interoperability issue with TCP PEP


Lakshmi,

This is interesting:

>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.
>
>
What sort of information do you have in mind, and in what manner would
the other node make use of this information?

It seems that an ideally constructed transport proxy would leave all the
relevant information (obviously port numbers, but also bidirectional
sequence
space, urgent pointers, I suppose the Push flag and any IP header service
markings) undisturbed.

While an intermediate proxy may very well [need to] resegment the data
in the
flow,  this would be transparent to the ultimate end-system anyway it
isn't clear
if this activity needs to be conveyed to the peer-proxy.

Is there some other information that you had in mind?

Eric



***************************************************************************
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.
***************************************************************************


_______________________________________________
Sis-SCPS-INTEREST mailing list
Sis-SCPS-INTEREST@mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-scps-interest

_______________________________________________
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/


