<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.xu-grow-bmp-route-policy-attr-trace" target="https://datatracker.ietf.org/doc/html/draft-xu-grow-bmp-route-policy-attr-trace-08">
   <front>
      <title>BGP Route Policy and Attribute Trace Using BMP</title>
      <author initials="F." surname="Xu" fullname="Feng Xu">
         <organization>Tencent</organization>
      </author>
      <author initials="T." surname="Graf" fullname="Thomas Graf">
         <organization>Swisscom</organization>
      </author>
      <author initials="Y." surname="Gu" fullname="Yunan Gu">
         <organization>Huawei</organization>
      </author>
      <author initials="S." surname="Zhuang" fullname="Shunwan Zhuang">
         <organization>Huawei</organization>
      </author>
      <author initials="Z." surname="Li" fullname="Zhenbin Li">
         <organization>Huawei</organization>
      </author>
      <date month="October" day="20" year="2023" />
      <abstract>
	 <t>   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 [RFC9069] and BGP adj-rib-out [RFC8671].  By monitoring
   these BGP RIB&#x27;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.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-xu-grow-bmp-route-policy-attr-trace-08" />
   
</reference>
