From owner-cvs-all Fri Aug 18 8:49:45 2000 Delivered-To: cvs-all@freebsd.org Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (Postfix) with ESMTP id F383237B422; Fri, 18 Aug 2000 08:49:40 -0700 (PDT) Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id IAA18913; Fri, 18 Aug 2000 08:49:39 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id IAA07643; Fri, 18 Aug 2000 08:49:39 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008181549.IAA07643@bubba.whistle.com> Subject: Re: cvs commit: src/usr.sbin/ppp README.changes mp.c In-Reply-To: <200008180654.e7I6sKF44766@hak.lan.Awfulhak.org> from Brian Somers at "Aug 18, 2000 07:54:20 am" To: Brian Somers Date: Fri, 18 Aug 2000 08:49:38 -0700 (PDT) Cc: Archie Cobbs , Brian Somers , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, brian@Awfulhak.orgg X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers writes: > > Mixing MP frames with non-MP frames is slightly dangerous. The > > problem is that the PPP link layer is required to deliver packets > > in order. When you go from MP encapsulating packets to not MP > > encapsulating packets (or vice-versa) you can't guarantee that the > > peer will deliver the packets in the same order that you sent them > > without being careful. This is mainly a problem when going from 1 > > -> 2 links I believe... or when mixing MP and non-MP over multiple > > links. > > It should only ever be possible to deliver out-of-order network layer > frames here, and even then, only a single frame can be out of order > at the time of the second link opening. > > I think the reason behind the link layer being required to deliver in > order is so that the control protocol packets don't make a mess of > the peers state machine (out of order IPCP frames for example). > > As ppp currently only does IP as an NCP, and IP packets are allowed > to be delivered out-of-order, I think this is ok. If you're doing Van Jacobson header compression, for example, with connection ID compression, out of order packets can really screw things up. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message