Re: [Idr] draft-ymbk-sidrops-rov-no-rr

[Gert Doering <[e-mail]>]

Hi,

On Mon, Nov 15, 2021 at 03:45:05PM +0100, Robert Raszuk wrote:
>    When RPKI data cause one or more paths to be dropped, withdrawn, or
>    merely not chosn as best path due to RPKI-based policy (ROV, ASPA,
>    etc.), those paths MUST be saved and marked so that later VRPs can
>    reevaluate them against then current policy.
> 
> 
> And how about the case when we have an inbound policy and today RPKI says
> this is a VALID path. Well tomorrow it may say it is INVALID for zoo of
> reasons. So the above paragraph no longer covers those cases as those VALID
> today would not be per the above definition (specified in section 4) in its
> original format kept in the Adj-Rib-In.

Those prefixes that are accepted "today" (for whatever RPKI status) are
not the problematic ones - those are already there, to be re-evaluated if
needed. 

Problematic is the stuff that the router forgot about, and now needs to
re-evaluate - without "soft in always", a route refresh is needed, which
is costly if the RTR database changes often.

So, yes, I support this draft.  Need to move over and subscribe there :-)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: [phone]         USt-IdNr.: DE813185279