From owner-freebsd-isp  Tue Nov 19 17:31:07 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA22391
          for isp-outgoing; Tue, 19 Nov 1996 17:31:07 -0800 (PST)
Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA22385
          for <isp@freebsd.org>; Tue, 19 Nov 1996 17:31:02 -0800 (PST)
Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.6.12/8.6.9) with SMTP id UAA10562; Tue, 19 Nov 1996 20:37:21 -0500
Date: Tue, 19 Nov 1996 20:37:21 -0500
Message-Id: <199611200137.UAA10562@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Tony Li <tli@jnx.com>
From: dennis@etinc.com (dennis)
Subject: Re: changed to: Frac T3?
Cc: isp@freebsd.org
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>
>   Clearly we're not talking about the same things here...Im not sure what
>   you mean by routing protocol stablity. Are you talking about IP? BGP?
>   or what?
>
>BGP, OSPF, whatever...  the problem remains the same, only the constants
>change.
>
>   IP is largely self throttling, and queue management shouldnt allow for
>   holding packets longer than the protocols allow for.
>
>And around we go....  queue management needs to guarantee that "my packets
>get out in a timely fashion" (sorry, Unix doesn't).  Queue management that
>drops protocol packets is a Bad Thing, as the protocol will fail sooner...

Well, routing protocol packets are priority packets and packets never get
dropped from the priority queues (well, not normally). This is a feature in
our product's driver...not BSD in general.

Dennis