While working on an implementation of the rpki-rtr protocol, some questions came up that could not be clarified using the specification draft.
(A) Unexpected withdrawal of white list (WL) entries. (i) What is the routers expected behavior when it receives a withdrawal of a white list (WL) entry that does not exist? (ii) Should the router respond to (A.i) by sending a "Reset Query" or should router silently ignore such information and if so, why? (B) The RPKI Validation cache may contain ROA's whose Prefix/Origin content is identical. An example could be a ROA that is about to expire and the "follow up" ROA is generated in advance to prevent a down time. During a short period of time both would certify the Prefix/Origin content. (i) Should the server send a WL announcement for each instance or should the server reduce the information to a single WL announcement? In other words should the router see the announcement of the new one followed by the withdrawal of the old one? (ii) In case the cache sends a WL announcement for each corresponding ROA entry can we expect the cache also to sends a WL withdrawal for each expired/revoked ROA? Thanks, Oliver ---------------------------------------------------------------------------- Oliver Borchert - Computer Scientist National Institute of Standards and Technology United States Department of Commerce phone: 301-975-4856, fax: 301-975-6238 _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
