On Mon, 15 Nov 2021 at 16:12, Mark Tinka <[email protected]> wrote: > > > > On 11/14/21 08:58, Saku Ytti wrote: > > > I don't think IETF is making standards for specific implementation. > > The implementation agnostic solution is to keep all routes which we > > rejected due to consulting validation database, regardless of > > validation state. > > Agreed, and covered in the draft:
You better clarify: - when this is implemented, STOP triggering route-refreshes from RTR updates (otherwise there is no point to it in the first place) - implement the above without BREAKING existing route-refresh functionality for non-RTR related code paths (like other RPL changes) Lukas _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
