On Sat, 23 Jul 2016, Juliusz Chroboczek wrote:
Please let me know if you're still unconvinced. I love arguing.
Well, in my testing I got the feeling (hard to tell since it was really hard to get a comprehensive picture of what was going on over time), that sometimes HNCP lost its connection to other HNCP nodes on the lan, while babel was still working, and the other way around, babel went down and HNCP was up.
Having these two protocols knowing nothing about each other and each others' state is potential source of problems.
I'm trying to think of another case where this has caused problem. A non-perfect example is MPLS requiring LDP to be up before the IGP starts trying to use the LSP switch path. Thus the "ldp igp sync" feature that came in RFC5443 which was quite a lot later in time than when RFC3031 first defined MPLS architecture. This feature came around after operational experience with the protocols and that them not knowing anything about each other caused operational problems and outages.
-- Mikael Abrahamsson email: [email protected] _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
