%% You should probably cite draft-ietf-grow-route-leak-detection-mitigation-10 instead of this revision.
@techreport{ietf-grow-route-leak-detection-mitigation-00,
    number =    {draft-ietf-grow-route-leak-detection-mitigation-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-ietf-grow-route-leak-detection-mitigation/00/},
    author =    {Kotikalapudi Sriram and Alexander Azimov},
    title =     {{Methods for Detection and Mitigation of BGP Route Leaks}},
    pagetotal = 11,
    year =      2019,
    month =     apr,
    day =       19,
    abstract =  {Problem definition for route leaks and enumeration of types of route leaks are provided in RFC 7908. This document describes a solution for detection and mitigation route leaks which is based on conveying route-leak protection (RLP) information in a Border Gateway Protocol (BGP) community. The RLP information is carried in a new well-known transitive BGP community, called the RLP community. The RLP community helps with detection and mitigation of route leaks at ASes downstream from the leaking AS (in the path of the BGP update). This is an inter-AS (multi-hop) solution mechanism. This solution complements the intra-AS (local AS) route-leak avoidance solution that is described in ietf-idr-bgp-open-policy draft.},
}