%% You should probably cite draft-xu-grow-bmp-route-policy-attr-trace-08 instead of this revision. @techreport{xu-grow-bmp-route-policy-attr-trace-02, number = {draft-xu-grow-bmp-route-policy-attr-trace-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-xu-grow-bmp-route-policy-attr-trace/02/}, author = {Feng Xu and Thomas Graf and Yunan Gu and Shunwan Zhuang and Zhenbin Li}, title = {{BGP Route Policy and Attribute Trace Using BMP}}, pagetotal = 15, year = ** No value found for 'doc.pub_date.year' **, month = ** No value found for 'doc.pub_date' **, day = ** No value found for 'doc.pub_date.day' **, abstract = {The generation of BGP adj-rib-in, local-rib or adj-rib-out comes from BGP route exchange and route policy processing. BGP Monitoring Protocol (BMP) provides the monitoring of BGP adj-rib-in {[}RFC7854{]}, BGP local-rib {[}I-D.ietf-grow-bmp-local-rib{]} and BGP adj-rib-out {[}I-D.ietf-grow-bmp-adj-rib-out{]}. By monitoring these BGP RIB's the full state of the network is visible, but how route-policies affect the route propagation or changes BGP attributes is still not. This document describes a method of using BMP to record the trace data on how BGP routes are (not) changed under the process of route policies.}, }