[RPKI] Routes containing aggregated AS-set becomes invalid

[Martin J. Levy]

One of these days this draft will become a reality!

    https://tools.ietf.org/html/draft-ietf-idr-deprecate-as-set-confed-set-03

Until then ... good luck!

Martin

> On Jul 14, 2020, at 11:23 PM, Jan Chrillesen via RPKI <rpki at lists.nlnetlabs.nl> wrote:
> 
> Hi,
> 
> I am in the process of turning on validation in our network and I have
> an issue with 2001:948::/32
> 
> When receiving the route over various IX's I get the following AS-path:
> 
> 2603
> {224,39590,64520,64530,65001,65002,65003,65004,65005,65006,65007,65008,65009,65010,65423,65426}
> 
> However when received via transit the AS-path doesn't contain the
> aggregated list of AS numbers (see
> https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/5441-aggregation.html#aggregatingwiththeassetargument
> for an explanation of aggregation with as-set)
> 
> Our Cisco ASR9000 running 6.6.3 considers the route with the aggregated
> as-set as RPKI invalid. Is this expected behavior or a bug?
> 
> - Jan
> -- 
> RPKI mailing list
> RPKI at lists.nlnetlabs.nl
> https://lists.nlnetlabs.nl/mailman/listinfo/rpki
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/rpki/attachments/20200714/f82be87b/attachment.htm>