Dear GROW Working Group, I've been reviewing draft-ietf-grow-bmp-rel-04 and want to suggest extending it to RPKI validation use case which is beyond normal policy-related changes.
After looking at the existing drafts and discussing the idea with a few community members, I believe this is the right draft to propose this enhancement. The draft does a great job supporting validation RPKI Invalids reporting via Event Reason (Validation Fail) and explicitly mentions usage of "artificial BGP Update" PDUs in Section 3.5. I suggest to cover RPKI Cache-triggered state change events in Section 3 : > Events may be generated as a result of re-evaluation not directly tied to the > reception of a BGP Update, for example changes in validation state following > an RPKI cache serial advance or reset. In such cases the BGP Update PDU > carried in the BGP Message TLV may be artificial and include only the > affected NLRI. > RPKI Cache resets or large serial advances can cause large volumes of > validation status changes. Implementations SHOULD apply rate limiting. I also would like to propose adding a new optional Informational TLV (RPKI Cache Context TLV) which will carry RTR Session ID and Serial Number for correlating events with cache updates, plus optional cache identifier. The good thing is, that under "RPKI Cache" we already have ROA, ASPA, BGPSec and other objects, which are relevant to the global RPKI infrastructure. Overall, I liked compact and precise structure of current problem statement in draft-ietf-grow-bmp-rel-04. Happy to discuss further or provide more clarification if needed. Best regards, Fedor Vompe Software Engineer Deutsche Telekom
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
