... A provider may wish to override validated RPKI data for their own purposes. While not explicitly a SIDR-driven requirement, this was discussed multiple times as a requirement during the original RPSEC work.
A specific proposal for how to locally override the RPKI structure as retrieved form the repository system is contained in a document being considered as a SIDR WG item: http://tools.ietf.org/html/draft-reynolds-rpki-ltamgmt-00
The resulting output (override or no), is a set of AS:prefix/maxlen tuples that reflects the provider's routing policy with regard to origin validation.
In the case of the doc cited above, it is not in that form.
This policy must now be distributed to routers for implementation. The mechanism for distributing the policy is currently draft-ymbk-rpki-rtr-protocol.
I think the ymbk protocol distributes the results of validating the RPKI data, with whatever policy has been applied to that validation process.
Steve _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
