%% You should probably cite draft-ietf-grow-bmp-tlv-14 instead of this revision.
@techreport{ietf-grow-bmp-tlv-07,
    number =    {draft-ietf-grow-bmp-tlv-07},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-tlv/07/},
    author =    {Paolo Lucente and Yunan Gu},
    title =     {{TLV support for BMP Route Monitoring and Peer Down Messages}},
    pagetotal = 7,
    year =      2022,
    month =     mar,
    day =       7,
    abstract =  {Most of the message types defined by the BGP Monitoring Protocol (BMP) make provision for optional trailing data. However, Route Monitoring messages (which provide a snapshot of the monitored Routing Information Base) and Peer Down messages (which indicate that a peering session was terminated) do not. Supporting optional data in TLV format across all BMP message types allows for a homogeneous and extensible surface that would be useful for the most different use-cases that need to convey additional data to a BMP station. While it is not intended for this document to cover any specific utilization scenario, it defines a simple way to support optional TLV data in all message types.},
}