> Having spend the better part of last week stepping a vendor through > exactly these semantics while there is no proof of termination of clue insertion, that a BGP/ROV *implementor* did not get it, justifies the hack. As the origin AS of a BGP UPDATE is decided by configuration and outbound policy of the BGP speaker, a validating BGP speaker MUST apply Route Origin Validation policy semantics (see [RFC6811] Sec 2) against the origin Autonomous System number which will actually be put in the AS_PATH (see [RFC4271] 4.3 Path Attributes:b) of the UPDATE to the peer. -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
