[pilc] interoperability issue with TCP PEP
"Lakshmi Priya" <lakshmips@future.futsoft.com> Wed, 28 July 2004 11:50 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 HAA23054 for <pilc-archive@lists.ietf.org>; Wed, 28 Jul 2004 07:50:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bpmut-0005vv-G4; Wed, 28 Jul 2004 07:48:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bpmqy-0005Dy-E3 for pilc@megatron.ietf.org; Wed, 28 Jul 2004 07:44:12 -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 HAA22773 for <pilc@ietf.org>; Wed, 28 Jul 2004 07:44:11 -0400 (EDT)
Received: from mail1.future.futsoft.com ([203.197.138.222]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bpmsk-0004YQ-UL for pilc@ietf.org; Wed, 28 Jul 2004 07:46:04 -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 <T6b1326397bcbc58ade594@mail1.future.futsoft.com> for <pilc@ietf.org>; Wed, 28 Jul 2004 17:12:52 +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 i6SBhTZ03716 for <pilc@ietf.org>; Wed, 28 Jul 2004 17:13:29 +0530
From: Lakshmi Priya <lakshmips@future.futsoft.com>
To: pilc@ietf.org
Date: Wed, 28 Jul 2004 17:12:02 +0530
Message-ID: <004801c47497$e72100c0$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)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
In-Reply-To: <001901c401a3$6b8fcde0$4703080a@future.futsoft.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Subject: [pilc] interoperability issue with TCP PEP
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, 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] 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