BGP RPKI: Routing policy validation state match and action

BGP origin validation uses Resource Public Key Infrastructure (RPKI) to verify that BGP prefixes are being advertised by an authorized autonomous system (AS). This feature supports both setting and matching the RPKI validation state in routing policies. A route-validation import policy can query the route-validation database for the validation state of a prefix in a routing instance and set that state in the routing table. Routing policies can then match routes based on the resulting validation state and apply appropriate policy actions. The validation state can be one of the following values: - Unverified (0): The validation state is not set. - Valid (1): The route origin is validated. - Unknown (2): The route cannot be validated. - Invalid (3): The route origin fails validation. By using the validation state in routing policy, you can control how BGP routes are processed based on their RPKI origin-validation result. If no route-validation instance matches the routing instance, the primary route-validation instance is queried.