[c-nsp] RPKI extended-community RFC8097

[Robert Raszuk]

> was thinking filtering invalids on RIB->FIB level,

Globally this would not work as in global RIB only best path is installed
(unless you run multipath).

Even for bRIB it would be the same.

The selection of eligible paths must happen prior to best path selection
for a given net.

Thx,
R.


On Mon, Dec 21, 2020 at 5:03 PM <adamv0025 at netconsultings.com> wrote:

> > Robert Raszuk
> > Sent: Saturday, December 19, 2020 10:02 AM
> >
> > > As far as I know, no way to set "ineligible" from a route-map.  Is
> there?
> >
> > A workaround could be to set unreachable next hop instead of dropping :)
> > That automatically disables such path from best path comparison yet it
> keeps
> > in BGP.
> >
> > But as said implementation could make it easier with a knob.
> >
> Yeah I was thinking along the same lines, keep it in BGP for sure, just not
> use it for actual data routing, (if that's the desired local policy).
> (was thinking filtering invalids on RIB->FIB level, BGP table map/selective
> route download -and limit the churn between RIB and FIB on a local box
> rather than BGP between boxes).
> -is there an option to filter invalids at the table map/selective route
> download attach point?
>
> > The question to ask if you want to advertise INVALID paths around ? Even
> if
> > not best path once you enable add-paths it may be advertised.
> >
> Well I'd say yes?
> -to leave BGP in a role of a messenger, then let each individual box/AS
> decide locally what to do (with the message).
>
> adam
>
>
>