From mailman-bounces@ietf.org  Thu Jul  1 07:08:19 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 HAA14696
	for <pilc-archive@lists.ietf.org>; Thu, 1 Jul 2004 07:08:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BfxhD-0002so-Sp
	for pilc-archive@lists.ietf.org; Thu, 01 Jul 2004 05:17:31 -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.14242.1088672648.3306.mailman@lists.ietf.org>
Date: Thu, 01 Jul 2004 05:04:08 -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  Wed Jul 14 00:01:22 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 AAA09635
	for <pilc-archive@lists.ietf.org>; Wed, 14 Jul 2004 00:01:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkaFn-00027Q-CB; Tue, 13 Jul 2004 23:16:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bcq9K-0000iP-SK
	for pilc@megatron.ietf.org; Tue, 22 Jun 2004 14:37:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14754
	for <pilc@ietf.org>; Tue, 22 Jun 2004 14:37:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bcq9J-00033a-HC
	for pilc@ietf.org; Tue, 22 Jun 2004 14:37:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcplL-0006cf-00
	for pilc@ietf.org; Tue, 22 Jun 2004 14:12:53 -0400
Received: from dcs-server2.cs.uiuc.edu ([128.174.252.3])
	by ietf-mx with esmtp (Exim 4.12) id 1Bcp0q-00068l-00
	for pilc@ietf.org; Tue, 22 Jun 2004 13:24:48 -0400
Received: from brooklyn (brooklyn.cs.uiuc.edu [128.174.244.80])
	(authenticated bits=0)
	by dcs-server2.cs.uiuc.edu (8.12.10/8.12.10) with ESMTP id
	i5MHOmLK013725
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <pilc@ietf.org>; Tue, 22 Jun 2004 12:24:48 -0500 (CDT)
From: "Robin Kravets" <rhk@cs.uiuc.edu>
To: <pilc@ietf.org>
Date: Tue, 22 Jun 2004 12:24:45 -0500
Message-ID: <B7D63DF79E7D1847946668F312592F90F3B90E@dcs-staff1.cs.uiuc.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,LINES_OF_YELLING 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 13 Jul 2004 23:16:15 -0400
Subject: [pilc] ACM MobiCom 2004 - Call For Participation
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


We apologize in advance if you receive multiple copies of this CFP.

----------------------------------------------------------------------
                C A L L  for  P A R T I C I P A T I O N

                      ***  ACM MobiCom 2004  ***

               The Tenth ACM International Conference on
                   Mobile Computing and Networking

                   September 26 - October 1, 2004

                     Loews Philadelphia Hotel
                  Philadelphia, Pennsylvania, USA

                    Sponsored by ACM SIGMOBILE

----------------------------------------------------------------------

MobiCom has grown in prestige since its inception in 1995 to become 
the leading technical meeting allowing the attendees to explore the 
latest and most exciting developments in mobile networking and 
computing. It is a highly competitive, single-track conference. This 
year's technical program includes 26 outstanding technical papers, a 
challenging panel session, a student poster session, 4 informative 
tutorials, and 6 full-day workshops that reflect important new 
research directions, including new workshops on vehicular ad hoc 
networks and on education in mobile communications.

As the global interest in mobile and wireless research and development 
surges, come join the debate on the future of mobile and wireless
communication networks.

Please find below information concerning registration, hotel 
accommodation, and a summary of the MobiCom 2004 technical program.

We look forward to hosting you in Philadelphia!

Zygmunt J. Haas
MobiCom 2004 General Chair

----------------------------------------------------------------------
                        CONFERENCE HIGHLIGHTS

FULL TECHNICAL PROGRAM: 
	http://sigmobile.org/mobicom/2004/

SECURE ONLINE REGISTRATION:
Note: early registration deadline is **September 10, 2004**
	http://sigmobile.org/mobicom/2004/registration.html

CONFERENCE HOTEL/VENUE:
Note: hotel registration cut-off date is **August 28, 2004**
	http://sigmobile.org/mobicom/2004/travel.html

CONFERENCE PROGRAM SUMMARY:
	* 4 Tutorials, September 26-27, 2004:
		* Evolution of IEEE 802.11 Wireless LANs: 
		  QoS, Security, Mobility, and Emerging Standard 
		  Perspectives (Full Day) by Sunghyun Choi, 
		  Seoul National University and Anand Balachandran, 
		  Intel Research

		* Theoretical Foundations of Wireless Networking 
	    	  (Half Day) by P. R. Kumar, University of Illinois,
		  Urbana-Champaign

		* Power-Efficient Protocols for Wireless Ad hoc 
	   	  Networks (Full Day) by Marwan M. Krunz, University 
		  of Arizona and Sung-Lee Lee, Hewlett Packard 
		  Laboratories

		* Sensor Networks: Hardware, Software, and Applications
		  (Half Day) by Kristofer S.J.Pisteri, Dust Networks, 
		  Berkeley, CA


	* 26 Technical papers (technical sessions September 28-30, 2004)
	  including the best student paper, covering topics of:
		security, media access control, transport layer issues, 
		WLANs, sensor networks, energy efficient systems, wireless 
		QOS, mesh networks, and systems issues

	* Conference Panel on:
		"Wireless Community Mesh Networks - Hype or the Next Big 
		 Thing" organized by Victor Bahl, Microsoft Research

	* Student poster session:
		The call for student posters is still open; we solicits 
		recent and on-going research by students on mobile
computing and mobile and wireless networking topics. 
See the conference web site for submission details. 
The deadline is July 12, 2004.

	* Demo session of mobile and wireless research:
		The call for proposals for research demos is still open. 
		See the conference web site for submission details. The 
		deadline is July 12, 2004. We are also planning an Expo 
		featuring exhibits of the latest mobile computing products 
		and services.

	* 6 one-day ACM workshops on October 1, 2004:
		* Joint Workshop on Foundations of Mobile Computing 
		  (DIALM-POMC 2004)
		* Workshop on Education in Mobile Communications 
		  (MobiEd 2004)
		* Workshop on Vehicular Ad Hoc Networks (VANET 2004)
		* Workshop on Wireless Security (WiSe 2004)
		* Workshop on Wireless Mobile Applications and Services on 
		  WLAN Hotspots (WMash 2004)
		* Workshop on Mobility Management and Wireless Access 
		  Protocols (WobiWac 2004)

----------------------------------------------------------------------


_______________________________________________
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 Jul 14 00:46: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 AAA09634
	for <pilc-archive@lists.ietf.org>; Wed, 14 Jul 2004 00:01:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkaFo-000280-CI; Tue, 13 Jul 2004 23:16:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkUMI-0001aF-JE
	for pilc@megatron.ietf.org; Tue, 13 Jul 2004 16:58:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17044
	for <pilc@ietf.org>; Tue, 13 Jul 2004 16:58:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkUMH-0005GF-87
	for pilc@ietf.org; Tue, 13 Jul 2004 16:58:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkUGE-0003hi-00
	for pilc@ietf.org; Tue, 13 Jul 2004 16:52:23 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BkUAM-00024Z-00; Tue, 13 Jul 2004 16:46:18 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i6DKjQJ22113;
	Tue, 13 Jul 2004 13:45:26 -0700 (PDT)
Message-Id: <200407132045.i6DKjQJ22113@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 13 Jul 2004 13:45:26 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-8.9 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
X-Mailman-Approved-At: Tue, 13 Jul 2004 23:16:14 -0400
Cc: pilc@ietf.org, rfc-editor@rfc-editor.org
Subject: [pilc] BCP 89, RFC 3819 on Advice for Internet Subnetwork Designers
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


--NextPart


A new Request for Comments is now available in online RFC libraries.


        BCP 89
        RFC 3819

        Title:      Advice for Internet Subnetwork Designers
        Author(s):  P. Karn, Ed., C. Bormann, G. Fairhurst,
                    D. Grossman, R. Ludwig, J. Mahdavi, G. Montenegro,
                    J. Touch, L. Wood
        Status:     Best Current Practice
        Date:       July 2004
        Mailbox:    karn@qualcomm.com, cabo@tzi.org,
                    gorry@erg.abdn.ac.uk, Dan.Grossman@motorola.com,
                    Reiner.Ludwig@ericsson.com,
                    jmahdavi@earthlink.net, gab@sun.com,
                    touch@isi.edu, lwood@cisco.com
        Pages:      60
        Characters: 152174
        SeeAlso:    BCP 89

        I-D Tag:    draft-ietf-pilc-link-design-15.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3819.txt


This document provides advice to the designers of digital
communication equipment, link-layer protocols, and packet-switched
local networks (collectively referred to as subnetworks), who wish to
support the Internet protocols but may be unfamiliar with the
Internet architecture and the implications of their design choices on
the performance and efficiency of the Internet.

This document is a product of the Performance Implications of Link
Characteristics Working Group of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <040713134345.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3819

--OtherAccess
Content-Type: Message/External-body; name="rfc3819.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <040713134345.RFC@RFC-EDITOR.ORG>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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



From pilc-bounces@ietf.org  Wed Jul 28 07:50:14 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 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/


From pilc-bounces@ietf.org  Wed Jul 28 12:01:09 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 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/


