On Wed, Nov 20, 2013 at 07:04:45PM +0400, Denis Ovsienko wrote: > > > 2/ Since Babel can use IPv4 to communicate between neighbours (see Section > > 4. of RFC 6126), the IPv4 implementation could use that. However, it > > wouldn't be interoperable with all known Babel implementations (babeld > > and Quagga). > > RFC6126 defines that IPv6 and IPv4 are both eligible for Babel packets > exchange (not to be confused with nexthops). Existing implementations prove > the former and the new implementation could prove the latter.
In the case of Bird, you may either manipule IPv4 data (address of neighbours, routes, next-hop), either manipulate IPv6 data. These two cases are mutually exclusive. Thus, a Babel implementation that manipulates IPv4 routes must also use IPv4 for Babel packets (and similarly for IPv6). Such an implementation wouldn't be able to interoperate with babeld and quagga-babel, since both use IPv6 for Babel packets.
pgp1A1mCDULSb.pgp
Description: PGP signature
_______________________________________________ Babel-users mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
