%% You should probably cite draft-ietf-grow-bmp-tlv-ebit instead of this I-D. @techreport{lucente-grow-bmp-tlv-ebit-02, number = {draft-lucente-grow-bmp-tlv-ebit-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-lucente-grow-bmp-tlv-ebit/02/}, author = {Paolo Lucente and Yunan Gu}, title = {{Support for Enterprise-specific TLVs in the BGP Monitoring Protocol}}, pagetotal = 6, year = 2022, month = jan, day = 17, abstract = {Message types defined by the BGP Monitoring Protocol (BMP) do provision for data in TLV - Type, Length, Value - format, either in the shape of optional TLVs at the end of a BMP message or Stats Reports TLVs. 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.}, }