<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-grow-bmp-tlv-ebit" target="https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-tlv-ebit-03">
   <front>
      <title>Support for Enterprise-specific TLVs in the BGP Monitoring Protocol</title>
      <author initials="P." surname="Lucente" fullname="Paolo Lucente">
         <organization>NTT</organization>
      </author>
      <author initials="Y." surname="Gu" fullname="Yunan Gu">
         <organization>Huawei</organization>
      </author>
      <date month="July" day="24" year="2023" />
      <abstract>
	 <t>   Message types defined by the BGP Monitoring Protocol (BMP) do
   provision for data in TLV - Type, Length, Value - format, either in
   the shape of a TLV message body, ie.  Route Mirroring and Stats
   Reports, or optional TLVs at the end of a BMP message, ie.  Peer Up
   and Peer Down.  However the space for Type value is unique and
   governed by IANA.  To allow the usage of vendor-specific TLVs, a
   mechanism to define per-vendor Type values is required.  In this
   document we introduce an Enterprise Bit, or E-bit, for such purpose.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-grow-bmp-tlv-ebit-03" />
   
</reference>
