<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">One of these days this draft will become a reality!<div><br></div><div> <a href="https://tools.ietf.org/html/draft-ietf-idr-deprecate-as-set-confed-set-03">https://tools.ietf.org/html/draft-ietf-idr-deprecate-as-set-confed-set-03</a></div><div><br></div><div>Until then ... good luck!<br><br><div dir="ltr">Martin</div><div dir="ltr"><br><blockquote type="cite">On Jul 14, 2020, at 11:23 PM, Jan Chrillesen via RPKI <rpki@lists.nlnetlabs.nl> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Hi,</span><br><span></span><br><span>I am in the process of turning on validation in our network and I have</span><br><span>an issue with 2001:948::/32</span><br><span></span><br><span>When receiving the route over various IX's I get the following AS-path:</span><br><span></span><br><span>2603</span><br><span>{224,39590,64520,64530,65001,65002,65003,65004,65005,65006,65007,65008,65009,65010,65423,65426}</span><br><span></span><br><span>However when received via transit the AS-path doesn't contain the</span><br><span>aggregated list of AS numbers (see</span><br><span>https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/5441-aggregation.html#aggregatingwiththeassetargument</span><br><span>for an explanation of aggregation with as-set)</span><br><span></span><br><span>Our Cisco ASR9000 running 6.6.3 considers the route with the aggregated</span><br><span>as-set as RPKI invalid. Is this expected behavior or a bug?</span><br><span></span><br><span>- Jan</span><br><span>-- </span><br><span>RPKI mailing list</span><br><span>RPKI@lists.nlnetlabs.nl</span><br><span>https://lists.nlnetlabs.nl/mailman/listinfo/rpki</span><br></div></blockquote></div></body></html>