linda, thanks for the review > Section 3 Egress Processing only has one sentence stating that ... the lack of more words was not an accident; a feature not a bug. :) > "When applied to egress policy, validation state MUST be determined > using the effective origin AS of the route as it will (or would) be > announced to the peer." What other choices there are ? Are there any > routers that support RFC 6480 RPKI not performing this step? how? unfortunately yes. see nick's and chris's emails. first, too many implementations do not even apply rov policy on locally originated routes, routes from ibgp, etc. second, for rov processing, many, maybe most, implementations use the 'global' AS of the router (as if there was one giving multi-AS knobs). chris's email kinda explains that last one pretty clearly. the purpose of this draft is to explain that the problem exists and to make the minimal statement of what implementations should do. i believe the text (i need to read robert's email three more times) is well understood by rov implementors, and even serious bgp/rov ops. randy -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
