%% You should probably cite draft-ietf-idr-bgp-fwd-rr-04 instead of this revision.
@techreport{ietf-idr-bgp-fwd-rr-00,
    number =    {draft-ietf-idr-bgp-fwd-rr-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-idr-bgp-fwd-rr/00/},
    author =    {Kaliraj Vairavakkalai and Natrajan Venkataraman},
    title =     {{BGP Route Reflector in Forwarding Path}},
    pagetotal = 8,
    year =      2024,
    month =     feb,
    day =       16,
    abstract =  {The procedures in BGP Route Reflection (RR) spec {[}RFC4456{]} primarily deal with scenarios where the RR is not in forwarding path, and is reflecting BGP routes with next hop unchanged. These procedures can sometimes result in traffic forwarding loops in deployments where the RR is in forwarding path, and is reflecting BGP routes with next hop set to self. This document specifies approaches to minimize possiblity of such traffic forwarding loops. One of those approaches updates path selection procedures specified in Section 9 of BGP RR. {[}RFC4456{]}},
}