Re: [Sidrops] ROV with ATOMIC_AGGREGATE

[Ben Maddison <[e-mail]>]

Thanks Jeff,

You can be kinda hard to parse sometimes!

On Thu, 2020-03-12 at 07:07 -0400, Jeffrey Haas wrote:
> 
> If the origin AS, sans sets, is correct - the implementation should
> believe it.
> 
You're saying that:

```
   o  Route Origin ASN: The origin AS number derived from a Route as
      follows:

      *  the rightmost AS in the final segment of the AS_PATH attribute
         in the Route if that segment is of type AS_SEQUENCE, or

      *  the BGP speaker's own AS number if that segment is of type
         AS_CONFED_SEQUENCE or AS_CONFED_SET or if the AS_PATH is
empty,
         or

      *  the distinguished value "NONE" if the final segment of the
         AS_PATH attribute is of any other type.
```
(https://tools.ietf.org/html/rfc6811#section-2)

Applies, as is, irrespective of the possible presence of
ATOMIC_AGGREGATE, right?

Cheers,

Ben

> If you want path validation, we need bgpsec.
> 
Depending on what you want to validate it *against*, you may need ASPA.
But that's a different conversation.

Cheers,

Ben