[address-policy-wg] 2008-08 (Initial Certification Policy in the RIPE NCC Service Region) going to Last Call

> You could, for example, adjust routing preference in accordance to 
> the availability of an RPKI signature
> 
>  - prefer routes with a valid RPKI ROA
> 
>  - if no routes with a valid ROA can be found, consider routes with no ROA
>    (neither matching nor invalid)
> 
>  - if no such routes can be found, accept any route, even if the ROA lists
>    a wrong origin AS

from draft-ietf-sidr-origin-ops-07

   Announcements with Valid origins SHOULD be preferred over those with
   NotFound or Invalid origins, if the latter are accepted at all.

   Announcements with NotFound origins SHOULD be preferred over those
   with Invalid origins.

   Announcements with Invalid origins MAY be used, but SHOULD be less
   preferred than those with Valid or NotFound.

randy