%% You should probably cite draft-ietf-grow-bmp-tlv-ebit instead of this I-D.
@techreport{lucente-grow-bmp-tlv-ebit-00,
    number =    {draft-lucente-grow-bmp-tlv-ebit-00},
    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/00/},
    author =    {Paolo Lucente and Yunan Gu},
    title =     {{Support for Enterprise-specific TLVs in the BGP Monitoring Protocol}},
    pagetotal = 6,
    year =      2019,
    month =     nov,
    day =       2,
    abstract =  {Message types defined by the BGP Monitoring Protocol (BMP) do provision for optional trailing data in TLV - Type, Length, Value - format; 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. With this document we want to introduce an Enterprise Bit, or E-bit, for such purpose.},
}