<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.cppy-grow-bmp-path-marking-tlv" target="https://datatracker.ietf.org/doc/html/draft-cppy-grow-bmp-path-marking-tlv-00">
   <front>
      <title>BMP Extension for Path Marking TLV</title>
      <author initials="C." surname="Cardona" fullname="Camilo Cardona">
         <organization>NTT</organization>
      </author>
      <author initials="P." surname="Lucente" fullname="Paolo Lucente">
         <organization>NTT</organization>
      </author>
      <author initials="P." surname="Francois" fullname="Pierre Francois">
         <organization>INSA</organization>
      </author>
      <author initials="Y." surname="Gu" fullname="Yunan Gu">
         <organization>Huawei</organization>
      </author>
      <date month="July" day="5" year="2019" />
      <abstract>
	 <t>   The 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] through Route Monitoring
   (RM) messages.  With the capability of allowing optional data to be
   added to the RM Messages in the format of TLV draft-lucente-bmp-tlv
   [I-D.lucente-bmp-tlv], more information about the BGP Update message
   encapsulated in the RM can be revealed.  This document proposes an
   extension to BMP to describe the BGP path status through the
   definition and use of Path Marking TLV.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-cppy-grow-bmp-path-marking-tlv-00" />
   
</reference>
