Merging bird and bird6

[Ondrej Zajicek]

On Thu, Jul 07, 2011 at 03:12:15PM +0400, Alexander V. Chernikov wrote:
> It depends on FIB/tricks implementation :)
> Actually, I'm trying to discuss those implementation details.
> 
> At the moment we have at least the following non-standard things in the
> world of routing:
> * VPNv4 address family (RFC 4364) (8-bytes route distinguisher, 4 byte
> IPv4 address)
> * VPNv6 address family (RFC 4659) (8-byte route distinguisher, 16 byte
> IPv6 address)
> * MPLS address family (RFC 3032) (size varies, it may be 16 bytes or
> more since  label stack depth is implementation-specific. for example,
> sizeof(sockaddr_mpls) is ~80 bytes for my implementation)

So you are developing doing some MPLS for BIRD development [*]? This is
interesting. Definitely we could merge it when it will be ready. Before
talking about some implementation details i would like to know your
overall idea of how MPLS could be integrated to BIRD and how it will
interact with other BIRD parts. It seems that MPLS is a bit different
from traditional routing in several ways, so it is not straightforward
(for example, how MPLS 'routes' will be represented in BIRD core, in
struct rte like common routes? In separate tables from IPv4/v6 routes?)
What are interactions (in BIRD) between MPLS and IPv4/v6 routing?
What new concepts have to be introduced?

[*] Rhetorical question, i found http://freebsd.mpls.in/

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at 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."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20110711/0aa47e25/attachment-0001.asc>