[c-nsp] IOS-XR BGP Aggregate-addresses and VRF Export route-policy behaviour

[Mailing Lists]

Need a second opinion on what should be happening with VRF export
route-policies on IOS-XR when using BGP aggregate-address prefixes...

Example scenario:

3 VRF's A,B and C

A and B export specific prefixes to C using an export route-policy

A contains an aggregate-address in BGP

BGP aggregate gets tagged and exported to C even though the route-map
specifies the specific longer prefix. This sort of behavior is repeatable
on ASR9K running 5.2.4 and 5.3.3 SP3 as well as XRv running 5.3.3 which my
example below is taken from

Full Configuration from the XRv test example:

http://pastebin.com/z0q3TTQB

Routing table and BGP table from vrf-c and

http://pastebin.com/nAc2vHza

You can see the aggregate tagged with the RT that should only apply to the
specific prefixes.

Have I properly misunderstood something and this is intentional behavior,
or is this very wrong?

Thanks