@ra1n85: Fibbing can encode any (loop-free) path in the network, whatever it might be. It also enables you to do unequal load-balance on any given set of paths.

@ra1n85: Fibbing can encode any (loop-free) path in the network, whatever it might be. It also enables you to do unequal load-balance on any given set of paths. BGP simply does not enable you to do this. Regarding scalability, the OSPF code is extremely optimized these days making Fibbing overhead negligible. We have numbers in the papers showing that routers do not even blink even when you inject 100,000 fake information into the Link-State protocol. Quite obviously, most people only require a few lies to implement their requirements, not that many. Another point, I'd like to mention is that by leveraging the OSPF flooding and distributed computation, Fibbing can install thousands of forwarding entries (network-wide) in less than a second. If you use BGP as a way to provision static route from a central controller for instance, you want reach these kind of performance. The podcast also lists some other differences. Disclaimer: I'm one of the author of Fibbing.