[155872] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Bird vs Quagga revisited

daemon@ATHENA.MIT.EDU (David Lamparter)
Tue Aug 28 19:35:23 2012

Date: Fri, 24 Aug 2012 00:26:27 +0200
From: David Lamparter <equinox@opensourcerouting.org>
To: nanog@nanog.org
In-Reply-To: <CAEj5p9Sa5jDWDrs+Z_=p3EdEYfHV0UYGUJ4Jy5-EmTx4kDa7aQ@mail.gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


--54u2kuW9sGWg/X+X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

> > Personally I would like to see more work on all three opensource
> > implementations, i.e. BIRD, OpenBGPd and Quagga.
>
> http://opensourcerouting.org/ to the rescue?

Hi, I'm David Lamparter, employed at the OpenSourceRouting (OSR) project
to maintain Quagga.

I can tell you that the OSR's interest is in providing a stable
open-source routing platform for actual switches/routers (with either a
software or hardware forwarding plane).  Quagga and BIRD were considered
equally; Quagga's single-RIB design and existence of isisd were what
tipped the scales.

We primarily perform conformance and scale testing and fix/enhance in
those areas; also we support 3rd parties in cleaning and submitting
Quagga patches/features.

OSPF and IS-IS are stronger targets currently since they need more work
than BGP, and also Euro-IX already did much of the latter.  Merging that
is on the TODO, but it's a lot of work.  Even as a Quagga maintainer, I
must currently recommend against using mainline Quagga as a route
server.  Please use Euro-IX Quagga, and if you can/want, convince your
decisionmakers to support Chris Hall on that -- I've been told future
work on the Euro-IX Quagga branch is not certain.

There's been a BoF on RIPE64 with OSR, BIRD and Quagga involvement.
There'll be one at RIPE65 again I think.  Either way if you have
questions, feel free to ask.


-David

--54u2kuW9sGWg/X+X
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlA2rhMACgkQCy20tTec6eM8SQEApKvgkj80EAx6ldzt6wxPrvfj
+zYlzLVfe+ZsrwKTukYBAJmQ4ZAKz65+7iPxrM4bxDdWEUnfx8FksLAaA1kt9Mk8
=be0W
-----END PGP SIGNATURE-----

--54u2kuW9sGWg/X+X--


home help back first fref pref prev next nref lref last post