On Thu, Jul 07, 2011 at 01:09:48AM +0400, Alexander V. Chernikov wrote: > Hello list! > > Are there any plans to move from different daemons to single one? > > From user point of view: > We will live with both v4+v6 for the next 10+ years, having all dynamic > routing in single place with single CLI is much more convenient. > > From developer point of view: > At the moment all code is based on ip_addr address type which is defined > to be v4 OR v6 at compile time. FIBs API assume the same: IPv4 OR IPv6.
My idea [*] about the future of IPv4/IPv6 split is to allow IPv4 addresses be embedded in IPv6 ip_addr (probably using IPv4-mapped address prefix). That would allow integration with minimal changes (probably just some UI changes, some FIB integration and some tricks with dual compilation of one-AF protocols). Bird4 would still be IPv4-only (with ip_addr of size 4 B) mainly for users with big route server deployments, but bird6 would support both IPv4 and IPv6. Is this model consistent with your requirements / way of development? [*] originally suggested by Martin Mares. -- 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