The routing and filtering behavior of prefixes is described in the following table. This behavior is dependent on the various combinations of enabling/disabling the following RPKI settings.
[no] bestpath prefix-validation disable
[no] match rpki {not-found | invalid | valid}
[no] bestpath prefix-validation disallow-invalid
In the following table, the term Default Behavior indicates the default behavior of the system. The default behavior is not to validate RPKI prefixes.
| bestpath prefix validation disable | match RPKI | prefix validation disallow-invalid | Routing and Filtering Behavior |
|---|---|---|---|
| Disabled | Disabled | Disabled | Default Behavior |
| Enabled | Enabled/Disabled | Enabled/Disabled | Default Behavior |
| Disabled | Disabled | Enabled | Invalid prefixes are not considered for best path calculations. |
| Disabled | Enabled | Disabled | Routing and filtering behaviour is according to the configured policies. |
| Disabled | Enabled | Enabled | Routing and filtering behaviour is according to the configured policies. However, invalid prefixes will not be considered for best path calculations. |