Sorry, I did not intend to imply that you were.
I should have prefaced my post with "to add".
Regards,
Jakob.
From: Matthew Petach
Sent: Wednesday, April 15, 2020 4:29 PM
To: Jakob Heitz (jheitz)
Cc: nanog@nanog.org
Subject: Re: Route aggregation w/o AS-Sets
I apologize if I wasn&#
I apologize if I wasn't clear.
I don't recommend ever using AS_SET.
So, in rule 3, I use the atomic-aggregate knob
to announce the single covering aggregate with
my backbone ASN as the atomic-aggregate origin
AS, and I don't generate or propagate any AS_SET
information along with the aggregate.
Suppose you had a set of customers than all announced to you a set of routes
and all those routes complete an aggregate
and you announce only the aggregate to those customers
and you include an AS_SET with it
then those customers will drop your aggregate, thinking there is an AS-loop
and those cust
From: NANOG On Behalf Of Lars Prehn
Sent: Tuesday, April 14, 2020 3:02 PM
To: Christopher Morrow
Cc: nanog list
Subject: Re: Route aggregation w/o AS-Sets
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
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 y
On Tue, Apr 14, 2020 at 3:02 PM Lars Prehn wrote:
>
> 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 (
On Tue, Apr 14, 2020 at 1:04 AM Alejandro Acosta
wrote:
>
> Hello Lars,
>
> As a comment there is a draft that proposes to deprecate AS_SET
> https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-as-set-confed-set/?include_text=1
Ta, thanks.
This completes the work started by RFC6472 - "Reco
On Mon, Apr 13, 2020 at 10:35 AM Lars Prehn 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
>
>
I generally would use the atomic-aggregate knob to
genera
Hello Lars,
As a comment there is a draft that proposes to deprecate AS_SET
https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-as-set-confed-set/?include_text=1
Alejandro,
On 4/11/20 7:09 AM, Lars Prehn wrote:
> Hi everyone,
>
> how exactly do you aggregate routes? When do you add th
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 wrote:
> Hi everyone,
>
> how exactly do you aggregate routes? When do you add the AS_SET
> attribute, when do you omit it? How does
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
11 matches
Mail list logo
