%% You should probably cite draft-gu-grow-bmp-route-leak-detection-06 instead of this revision.
@techreport{gu-grow-bmp-route-leak-detection-02,
    number =    {draft-gu-grow-bmp-route-leak-detection-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-gu-grow-bmp-route-leak-detection/02/},
    author =    {Yunan Gu and China Telecom and Di Ma and Shunwan Zhuang},
    title =     {{BMP for BGP Route Leak Detection}},
    pagetotal = 11,
    year =      2019,
    month =     apr,
    day =       2,
    abstract =  {According to RFC7908 {[}RFC7908{]}, Route leaks refer to case that the delivery range of route advertisements is beyond the expected range. For many current security protection solutions, the ISPs (Internet Service Providers) are focusing on finding ways to detect the happening of route leaks. However, the real-time route leak detection if any occurs is important as well. This document extends the BGP Monitoring Protocol (BMP) {[}RFC7854{]} to provide a routing security scheme suitable for ISPs to detect BGP route leaks within their own networks.},
}