%% 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-01, number = {draft-xu-grow-bmp-route-policy-attr-trace-01}, 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/01/}, author = {Feng Xu and Yunan Gu and Shunwan Zhuang and Zhenbin Li}, title = {{BGP Route Policy and Attribute Trace Using BMP}}, pagetotal = 21, year = 2019, month = jul, day = 8, abstract = {The generation of BGP adj-rib-in, local-rib or adj-rib-out comes from BGP protocol communication, 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{]}. However, there lacks monitoring of how BGP routes are transformed from adj-rib-in into local-rib and then adj-rib-out (i.e., the BGP route policy processing procedures). This document describes a method of using BMP to trace the change of BGP routes in correlation with responsible route policies.}, }