On Mon, Sep 07, 2015 at 11:10:34PM +0200, Toke Høiland-Jørgensen wrote: > This adds the Babel routing protocol (RFC6126) to Bird. It is a complete > implementation of the IPv6 subset of RFC6126, but does not implement any > of the extensions.
Thanks, i will review the patch ASAP. > Compared to the RFC patch posted earlier, this patch implements several > more SHOULD parts of the protocol, has updated interactions with the > Bird core, and uses fewer timers and resource pools. In addition, > several other tweaks and fixes have been made following interoperability > testing with the official babeld. > > The implementation of the protocol is now, to the best of my knowledge, > complete. The only exception is the propagation of IPv4 routes which has > deliberately been left out due to Bird's lack of support for a > dual-stack operation mode. Juliusz Chroboczek, the author of the Babel > spec, has expressed a preference to not have an IPv4-only implementation > of Babel, so as to avoid fragmenting the community. I have followed that > preference, and so this implementation ignores IPv4 route TLVs entirely. > > As far as interactions with Bird core is concerned, the main thing > missing is the reconfiguration support; I still haven't decided exactly > what is the right thing to do here. But probably some variant of the > OSPF protocol's logic is needed. And of course documentation of the > configuration options. Yes, OSPF-style reconfiguration is a proper way to go. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
signature.asc
Description: Digital signature