BGP Route Policy and Attribute Trace Using BMP

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Feng Xu  , Thomas Graf  , Yunan Gu  , Shunwan Zhuang  , Zhenbin Li 
Last updated 2020-07-08 (latest revision 2020-01-05)
Stream (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Feng Xu (
Thomas Graf (
Yunan Gu (
Shunwan Zhuang (
Zhenbin Li (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)