[PATCH RFC v2] Preserve BGP attributes from non-BGP protocols

[Matthias Schiffer]

On 05/23/2013 11:36 PM, Ondrej Zajicek wrote:
> On Thu, May 23, 2013 at 07:35:29PM +0200, Matthias Schiffer wrote:
>> I think all routes should be handled the same way, without regard for
>> the source protocol.
> 
> Well, this is nice idea, but BGP standard (RFC 4271) specifies for route
> propagation different behavior based on whether the route was received
> originally from iBGP or from eBGP. So even if you want that non-BGP
> routes should be handled like BGP ones, you would have to specify
> whether like iBGP or like eBGP.
> 
Hmm, this is true, but the distinction becomes hard to define as soon as
you have BGP instances with different local AS# and propagate routes
between then... maybe it would be beneficial to add an (filter
readable/writable) attribute holding the remote AS# the route was
received from and use this to differentiate between iBGP and eBGP?

Matthias

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20130524/fa0f0391/attachment-0001.asc>