Route aggregation w/o AS-Sets

Tue Apr 14 19:02:16 UTC 2020

Thanks for all the answers! I think I have one more detail I'd like to 
know.

Lets say you own X/22. You have delegated X/23 to your customer, keeping 
the other /23 for yourself. For some reason, your customer also owns and 
announced (to you) all remaining IPs necessary to complete X/21.

Do you announce the aggregate X/21 (including addresses not associated 
with you), the aggregate X/22 (only address belonging to you), or the 
more specific route X/23 (including only addresses delegated from you to 
your customer)?

Best regards,

Lars

On 14.04.20 06:07, Christopher Morrow wrote:
> Don't user as-sets step one.
> Rpki does not understand how to express an as-sets' authorization.
>
> Why do you want to do this?
>
> On Mon, Apr 13, 2020, 13:34 Lars Prehn <lprehn at mpi-inf.mpg.de 
> <mailto:lprehn at mpi-inf.mpg.de>> wrote:
>
>     Hi everyone,
>
>     how exactly do you aggregate routes? When do you add the AS_SET
>     attribute, when do you omit it? How does the latter interplay with
>     RPKI?
>
>     Best regards,
>
>     Lars
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20200414/fdf91975/attachment.html>