<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-grow-bmp-adj-rib-out" target="https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-adj-rib-out-07">
   <front>
      <title>Support for Adj-RIB-Out in the BGP Monitoring Protocol (BMP)</title>
      <author initials="T." surname="Evens" fullname="Tim Evens">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="S." surname="Bayraktar" fullname="Serpil Bayraktar">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Lucente" fullname="Paolo Lucente">
         <organization>NTT Communications</organization>
      </author>
      <author initials="K." surname="Mi" fullname="Kevin Mi">
         <organization>Tencent</organization>
      </author>
      <author initials="S." surname="Zhuang" fullname="Shunwan Zhuang">
         <organization>Huawei</organization>
      </author>
      <date month="August" day="5" year="2019" />
      <abstract>
	 <t>The BGP Monitoring Protocol (BMP) only defines access to the Adj-RIB-In Routing Information Bases (RIBs).  This document updates BMP (RFC 7854) by adding access to the Adj-RIB-Out RIBs.  It also adds a new flag to the peer header to distinguish between Adj-RIB-In and Adj-RIB-Out.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-grow-bmp-adj-rib-out-07" />
   
</reference>
