> was not at the protocol level, but at the daemon level. We have > separate forks of quagga (for ISIS with source sensitive routing), > bird (for ospfv3), stand alone daemons like babels (which also has a > quagga-babel version, but I think it's from another quagga branch than > the ISIS work)
Dave, According to David Lamparter, Quagga-babels work is using the same Zebra interfaces as IS-IS, so the two should be able to merge at some point. The outstanding issue is merging the releavant bits of Quagga-RE into Quagga, which is something that should happen soon, for some value of soon (at least Matthieu and David are discussing it). > So far as I know the quagga-babel"s" work hasn't started yet. Actually, it's running as we speak. It's not feature complete yet (there's no support for redistribution of source-sensitive routes), and I haven't reviewed the code yet (I'm busy reviewing Matthieu's code and merging babels into standalone babeld, check the branch called "ss-tables-merge"). We'll hopefully end up with just two implementations before the end of the summer: - Quagga (Babel, IS-IS, perhaps RIPng at some future point); - babeld (Babel). > It IS a headache to deal with all these different daemons and stuff > flying in loose formation, I know. Trouble is, my job is doing research, so any maintenance work I do happens during my copious free time, which causes my family to complain. Could you please speak to my nephews? (Getting GSOC funding and finding a competent student this summer was a big help, babels-Quagga wouldn't have happened otherwise.) -- Juliusz _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
