… To follow up on the last couple of comments of the session … the large resource bundles also contain AS numbers … while we can claim NOTFOUND might help routing robustness in RPKI malfunctions … there is no such 3rd state in path validation. The path becomes INVALID in such cases.
Of course this might be the answer to John’s earlier question of when one would keep a route with INVALID path but Valid/NOTFOUND origin. :) I have participated in several public/private working groups where operators often express concern about the RPKI fragility vs utility question. Anything we can do to reduce the fact or FUD about the fragility concerns, would help in these discussions. dougm — Doug Montgomery, Mgr Internet & Scalable Systems Research NIST/ITL/ANTD _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
