%% You should probably cite draft-ietf-grow-bmp-path-marking-tlv instead of this I-D.
@techreport{cppy-grow-bmp-path-marking-tlv-00,
    number =    {draft-cppy-grow-bmp-path-marking-tlv-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-cppy-grow-bmp-path-marking-tlv/00/},
    author =    {Camilo Cardona and Paolo Lucente and Pierre Francois and Yunan Gu},
    title =     {{BMP Extension for Path Marking TLV}},
    pagetotal = 8,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {The BGP Monitoring Protocol (BMP) provides the monitoring of BGP adj- rib-in {[}RFC7854{]}, BGP local-rib {[}I-D.ietf-grow-bmp-local-rib{]} and BGP adj-rib-out {[}I-D.ietf-grow-bmp-adj-rib-out{]} through Route Monitoring (RM) messages. With the capability of allowing optional data to be added to the RM Messages in the format of TLV draft-lucente-bmp-tlv {[}I-D.lucente-bmp-tlv{]}, more information about the BGP Update message encapsulated in the RM can be revealed. This document proposes an extension to BMP to describe the BGP path status through the definition and use of Path Marking TLV.},
}