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.
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.
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.
-- Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
