[pilc] tcppep

"Lakshmi Priya" <lakshmips@future.futsoft.com> Wed, 03 March 2004 04:45 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29497 for <pilc-archive@lists.ietf.org>; Tue, 2 Mar 2004 23:45:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AyOFj-00007a-LY; Tue, 02 Mar 2004 23:45:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AyOFH-0008Ui-73 for pilc@optimus.ietf.org; Tue, 02 Mar 2004 23:44:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29369 for <pilc@ietf.org>; Tue, 2 Mar 2004 23:44:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AyOFF-0005rF-00 for pilc@ietf.org; Tue, 02 Mar 2004 23:44:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AyOEa-0005fy-00 for pilc@ietf.org; Tue, 02 Mar 2004 23:43:53 -0500
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com) by ietf-mx with esmtp (Exim 4.12) id 1AyODQ-0005NS-00 for pilc@ietf.org; Tue, 02 Mar 2004 23:42:40 -0500
Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id <T681c9bb3aacbc58c23394@fsnt.future.futsoft.com> for <pilc@ietf.org>; Wed , 3 Mar 2004 10:09:24 +0530
Received: from lakshmips (lakshmips.future.futsoft.com [10.8.3.71]) by kailash.future.futsoft.com (8.11.0/8.11.0) with ESMTP id i234WRb30464 for <pilc@ietf.org>; Wed, 3 Mar 2004 10:02:27 +0530
Reply-To: lakshmips@future.futsoft.com
From: Lakshmi Priya <lakshmips@future.futsoft.com>
To: pilc@ietf.org
Date: Wed, 03 Mar 2004 10:01:12 +0530
Message-ID: <001001c400d8$5cb1ab20$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.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=EXCUSE_16 autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [pilc] tcppep
Sender: pilc-admin@ietf.org
Errors-To: pilc-admin@ietf.org
X-BeenThere: pilc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pilc>, <mailto:pilc-request@ietf.org?subject=unsubscribe>
List-Id: Performance Implications of Link Characteristics IETF Working Group <pilc.ietf.org>
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>
Content-Transfer-Encoding: 7bit

hi,

RFC3135 for PEP states that "In a split connection we can encapsulate
the tcp packets over satlink. These tcp packets are decapsulated at
the other end of the satlink and transmitted to the end host."

Will it be necessary to encapsulate the entire packet along with the TCP and
IP headers to maintain end to end semantics?
In such a case wouldnt it be an overhead to manupulate the send buffers on
the satellite tcp as segments(since we retain the headers) rather than
bytes.
Any documents suggesting techniques for pep encapsulation?

thanks,
lp



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