<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.mi-grow-monitoring-outgoing-bgp-routes" target="https://datatracker.ietf.org/doc/html/draft-mi-grow-monitoring-outgoing-bgp-routes-00">
   <front>
      <title>Monitoring Outgoing Routes Using BMP</title>
      <author initials="K." surname="Mi" fullname="Kevin Mi">
         <organization>Tencent</organization>
      </author>
      <author initials="S." surname="Zhuang" fullname="Shunwan Zhuang">
         <organization>Huawei</organization>
      </author>
      <author initials="J." surname="Dong" fullname="Jie Dong">
         <organization>Huawei</organization>
      </author>
      <date month="March" day="13" year="2017" />
      <abstract>
	 <t>   The BGP Monitoring Protocol (BMP) [RFC7854] is designed to monitor
   BGP [RFC4271] running status, such as BGP peer relationship
   establishment and termination and route updates.  At present, the BMP
   only monitors the incoming bgp routes (Adj-RIB-In), does not monitor
   the outgoing bgp routes (Adj-RIB-Out).

   This draft extends the applicability of BMP [RFC7854] to monitor the
   outgoing bgp routes.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-mi-grow-monitoring-outgoing-bgp-routes-00" />
   
</reference>
