From mailman-bounces@ietf.org Wed Dec 1 07:11:15 2004 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 HAA20098 for ; Wed, 1 Dec 2004 07:11:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZTPb-0006tF-57 for pppext-web-archive@ietf.org; Wed, 01 Dec 2004 07:16:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZSFj-0005Oa-9x for pppext-web-archive@ietf.org; Wed, 01 Dec 2004 06:02:31 -0500 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: pppext-web-archive@ietf.org X-No-Archive: yes Message-ID: Date: Wed, 01 Dec 2004 05:35:39 -0500 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 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 pppext-web-archive@ietf.org: List Password // URL ---- -------- pppext@ietf.org kiowes https://www1.ietf.org/mailman/options/pppext/pppext-web-archive%40ietf.org From pppext-bounces@ietf.org Wed Dec 1 12:29:50 2004 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 MAA00362 for ; Wed, 1 Dec 2004 12:29:50 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZYNw-0005h1-UZ for pppext-web-archive@ietf.org; Wed, 01 Dec 2004 12:35:25 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZXQI-0004Uk-TT; Wed, 01 Dec 2004 11:33:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZVeD-0006tZ-08 for pppext@megatron.ietf.org; Wed, 01 Dec 2004 09:40:01 -0500 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 JAA03867 for ; Wed, 1 Dec 2004 09:39:59 -0500 (EST) Received: from mail1.future.futsoft.com ([203.197.138.222]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZVjX-0001OR-6M for pppext@ietf.org; Wed, 01 Dec 2004 09:45:32 -0500 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 for ; Wed, 1 Dec 2004 20:09:48 +0530 Received: from mania (mania.future.futsoft.com [10.4.9.30]) by kailash.future.futsoft.com (8.12.8/8.12.8) with SMTP id iB1EcxQf014489 for ; Wed, 1 Dec 2004 20:09:01 +0530 From: "Mania" To: Date: Wed, 1 Dec 2004 20:04:54 +0530 Message-ID: <00b901c4d7b2$ed63aea0$1e09040a@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 V6.00.2800.1106 X-Spam-Score: 0.2 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 7bit Subject: [Pppext] PPPoE - VJ compression support. X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mania@future.futsoft.com List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: 7bit Hi All, Most of the freeware PPPoE clients do not seem to support VJ compression on the PPPoE sessions and it looks like VJ compression is not supported on PPPoE sessions. I am not able to locate any references in the standard RFC mentioning about VJ compression on PPPoE sessions. I understand that VJ is primarily used for PPP over HDLC (slow-speed links)/ISDN links. Could anyone clarify whether VJ compression needs to supported on PPPoE sessions or not ? Thanks in advance Mani. *************************************************************************** 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. *************************************************************************** _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Wed Dec 1 14:31:13 2004 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 OAA14658 for ; Wed, 1 Dec 2004 14:31:13 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZaHR-0001Uc-2w for pppext-web-archive@ietf.org; Wed, 01 Dec 2004 14:36:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZZRi-0005d2-5A; Wed, 01 Dec 2004 13:43:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZYhN-0001Ck-NR for pppext@megatron.ietf.org; Wed, 01 Dec 2004 12:55:29 -0500 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 MAA04232 for ; Wed, 1 Dec 2004 12:55:27 -0500 (EST) Received: from pc9.faradsl.ftech.co.uk ([212.32.46.170] helo=GENERAL.hq.farsitecommunications.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZYmk-0006qM-49 for pppext@ietf.org; Wed, 01 Dec 2004 13:01:02 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Subject: RE: [Pppext] PPPoE - VJ compression support. Date: Wed, 1 Dec 2004 17:55:17 -0000 Message-ID: <7C078C66B7752B438B88E11E5E20E72E01095539@general.hq.farsitecommunications.com> Thread-Topic: [Pppext] PPPoE - VJ compression support. Thread-Index: AcTXy2kpFWjhrqxvR/i+CLm7vopi/AAAbXqg From: "Jonathan Goodchild" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: quoted-printable Cc: mania@future.futsoft.com X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: quoted-printable > Could anyone clarify whether VJ compression needs to supported on PPPoE sessions or not ? VJ compression doesn't work too well when packets can get discarded silently, and that may well be the situation with PPPoE, so perhaps that explains why the freeware implementations don't support it. In any case, I don't believe VJ compression should have to be supported by any particular PPP implementation - it is after all an option which can be rejected. Jonathan Goodchild _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Wed Dec 1 16:44:03 2004 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 QAA28900 for ; Wed, 1 Dec 2004 16:44:03 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZcLy-0005YS-VE for pppext-web-archive@ietf.org; Wed, 01 Dec 2004 16:49:40 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZbgZ-0004R2-DU; Wed, 01 Dec 2004 16:06:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZbA6-0000yj-Ba for pppext@megatron.ietf.org; Wed, 01 Dec 2004 15:33:18 -0500 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 PAA21207 for ; Wed, 1 Dec 2004 15:33:15 -0500 (EST) Received: from imh.informatik.uni-bremen.de ([134.102.224.4] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZbFT-00034S-Sj for pppext@ietf.org; Wed, 01 Dec 2004 15:38:52 -0500 Received: from [IPv6:::1] (imh [134.102.224.4]) by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id iB1KV643022518; Wed, 1 Dec 2004 21:31:08 +0100 (MET) In-Reply-To: <00b901c4d7b2$ed63aea0$1e09040a@future.futsoft.com> References: <00b901c4d7b2$ed63aea0$1e09040a@future.futsoft.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Carsten Bormann Subject: Re: [Pppext] PPPoE - VJ compression support. Date: Wed, 1 Dec 2004 21:31:05 +0100 To: mania@future.futsoft.com X-Mailer: Apple Mail (2.619) X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: 7bit Cc: pppext@ietf.org, Carsten Bormann X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: 7bit On Dec 01 2004, at 15:34 Uhr, Mania wrote: > Hi All, > > Most of the freeware PPPoE clients do not seem to support VJ > compression on > the PPPoE sessions and it looks like VJ compression is not supported on > PPPoE > sessions. I am not able to locate any references in the standard RFC > mentioning about VJ compression on PPPoE sessions. I understand that > VJ is > primarily used for PPP over HDLC (slow-speed links)/ISDN links. > > Could anyone clarify whether VJ compression needs to supported on PPPoE > sessions or not ? It certainly does not need to be (as has already been answered). VJ compression also is a poor match to today's TCPs. With options such as SACK and timestamps prevalent, RFC 1144 simply does not work any longer. The IETF ROHC working group is in the process of finishing a new TCP header compression scheme that will work with current TCPs and also anticipates innovations like ECN. Gruesse, Carsten _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Tue Dec 14 09:47:59 2004 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 JAA03309 for ; Tue, 14 Dec 2004 09:47:59 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeE66-0002xa-JH for pppext-web-archive@ietf.org; Tue, 14 Dec 2004 09:56:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeCud-0007Dm-Uq; Tue, 14 Dec 2004 08:40:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeCK0-0006bS-RI for pppext@megatron.ietf.org; Tue, 14 Dec 2004 08:02:32 -0500 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 IAA21732 for ; Tue, 14 Dec 2004 08:02:31 -0500 (EST) Received: from sandesha.sasken.com ([164.164.56.19] helo=mail3.sasken.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeCS1-0007dK-Hd for pppext@ietf.org; Tue, 14 Dec 2004 08:10:50 -0500 Received: from mail3.sasken.com (localhost [127.0.0.1]) by mail3.sasken.com (8.12.10/8.12.10) with ESMTP id iBED00o6028551 for ; Tue, 14 Dec 2004 18:31:55 +0530 (IST) Received: from sunrnd2.sasken.com (sunrnd2.sasken.com [10.1.48.2])by mail3.sasken.com (8.12.10/8.12.10) with ESMTP id iBECanra023190for ; Tue, 14 Dec 2004 18:06:49 +0530 (IST) Received: from sunrnd2.sasken.com (localhost [127.0.0.1])by sunrnd2.sasken.com (8.12.10/8.12.10) with ESMTP id iBECanlu025434for ; Tue, 14 Dec 2004 18:06:49 +0530 (IST) Received: from localhost (anandvel@localhost)by sunrnd2.sasken.com (8.12.10/8.12.10/Submit) with ESMTP id iBECanmt025429for ; Tue, 14 Dec 2004 18:06:49 +0530 (IST) X-Authentication-Warning: sunrnd2.sasken.com: anandvel owned process doing -bs Date: Tue, 14 Dec 2004 18:06:48 +0530 (IST) From: Anandavel P To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-imss-version: 2.012 X-imss-result: Passed X-imss-scores: Clean:85.36683 C:20 M:3 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d X-Mailman-Approved-At: Tue, 14 Dec 2004 08:40:22 -0500 Subject: [Pppext] PPPoE compression/encapsulation X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 I have a query regarding PPPoE using Compression & encapsulation. The compression and encription protocols often require the packets to be delivered in sequence. In an IP network( over which a PPPoE session is estabished ), packets could get delivered out of sequence. So how does compression/encription work? Is there anything i am missing? Regards, Anand. ----------------------------------------------------------------------- Anandavel P. Tel: + 91 80 25355501 Extn: 4065 Project Leader, Fax: + 91 80 25351133 DSL Group, Products Division, Email: anandvel@sasken.com 139/25, Ring Road, Domlur URL: www.sasken.com Bangalore - 560071 India. ----------------------------------------------------------------------- "SASKEN RATED THE BEST EMPLOYER IN THE COUNTRY by the BUSINESS TODAY Mercer Survey 2004" SASKEN BUSINESS DISCLAIMER This message may contain confidential, proprietary or legally Privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, Disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext From pppext-bounces@ietf.org Tue Dec 14 10:22:17 2004 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 KAA08203 for ; Tue, 14 Dec 2004 10:22:17 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeEdI-00049t-Pa for pppext-web-archive@ietf.org; Tue, 14 Dec 2004 10:30:38 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeER4-0000P3-A3; Tue, 14 Dec 2004 10:17:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeE8t-0000fG-Fo for pppext@megatron.ietf.org; Tue, 14 Dec 2004 09:59:11 -0500 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 JAA04715 for ; Tue, 14 Dec 2004 09:59:09 -0500 (EST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeEGs-0003Rg-7Q for pppext@ietf.org; Tue, 14 Dec 2004 10:07:29 -0500 Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id iBEEx5dt007630 for ; Tue, 14 Dec 2004 07:59:05 -0700 (MST) Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143]) by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id iBEEx58p010952 for ; Tue, 14 Dec 2004 09:59:05 -0500 (EST) Received: from phorcys.East.Sun.COM (localhost [127.0.0.1]) by phorcys.East.Sun.COM (8.13.1+Sun/8.13.1) with ESMTP id iBEEx5fp024974; Tue, 14 Dec 2004 09:59:05 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.13.1+Sun/8.13.1/Submit) id iBEEx5Zo024971; Tue, 14 Dec 2004 09:59:05 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16830.65465.383061.588669@gargle.gargle.HOWL> Date: Tue, 14 Dec 2004 09:59:05 -0500 From: James Carlson To: Anandavel P Subject: Re: [Pppext] PPPoE compression/encapsulation In-Reply-To: Anandavel P's message of 14 December 2004 18:06:48 References: X-Mailer: VM 7.01 under Emacs 21.3.1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: 7bit Cc: pppext@ietf.org X-BeenThere: pppext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: PPP Extensions List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: pppext-bounces@ietf.org Errors-To: pppext-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Content-Transfer-Encoding: 7bit Anandavel P writes: > I have a query regarding PPPoE using Compression & encapsulation. > > The compression and encription protocols often require the packets to be > delivered in sequence. Right. > In an IP network( over which a PPPoE session is > estabished ), PPPoE runs over Ethernet, not IP. Ethernet guarantees sequencing. > packets could get delivered out of sequence. So how > does compression/encription work? Most of the algorithms involved either have their own sequence numbers or have some mechanism for detecting a loss of sender/receiver synchronization. Even if there's reordering and loss, those algorithms can generally deal with it. (Though, of course, with a performance penalty.) > Is there anything i am missing? Just that PPPoE doesn't run over IP, I think. I wouldn't recommend running compression or encryption with PPPoE, as these tend to magnify any errors that occur, but they should work as specified. -- James Carlson, IP Systems Group? Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677 _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext