From owner-freebsd-current@FreeBSD.ORG Tue Mar 2 07:18:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C03416A4CF for ; Tue, 2 Mar 2004 07:18:13 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D76943D1F for ; Tue, 2 Mar 2004 07:18:13 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 55442 invoked from network); 2 Mar 2004 15:18:12 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 15:18:12 -0000 Message-ID: <4044A5B4.789778D8@freebsd.org> Date: Tue, 02 Mar 2004 16:18:12 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302090219.GC3438@astral-on.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: ad@astral-on.net Subject: Re: My planned work on networking stack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 15:18:14 -0000 Brad Knowles wrote: > > At 3:52 PM +0200 2004/03/02, Andrew Degtiariov wrote: > > >> Oh, and then there are all the operational issues where > >> zebra/quagga can't keep sessions going when a neighbor flaps, etc.... > >> Those would require re-architecting the whole routing system, at > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Congratulation. That's namely what the conversation was about. > > Right. We can either re-architect zebra/quagga, or we can start > with something that addresses the weaknesses in these tools, or we > can do something else. The best thing would be to stay by the sideline, be quiet and let the people who know what they do solve these things for everyones benefit. > I'm advocating that we at least take a long hard look at what > Henning Brauer has done, and seriously consider whether it would make > sense for us to start with that to give us a leg up on the > re-architecting process. What Henning, Claudio and me are doing is certainly a step forward. Although there is no re-architecting of the routing system going on. It's just a different and more efficient implementation approach. We do not reinvent the world. > If nothing else, this would at least give us an interesting > insight to what some of the weaknesses are in this category, and > maybe help us identify better solutions faster and more easily. > > In particular, if there are such serious problems with > zebra/quagga that they would need to be completely re-architected in > order to be useful, then I don't see that as being a particularly > fruitful line of work to pursue. I'd rather start with something > that requires less re-work, and would presumably allow us to more > easily add in any additional bits that we feel are necessary or > desirable. I'd like to see you do any real work in this area instead of producing many and longs emails with lots of mis-informed rants in them. Yes, this my official put-up-or-shut-up call to you. -- Andre