@techreport{ietf-idr-bgp-fwd-rr-04,
    number =    {draft-ietf-idr-bgp-fwd-rr-04},
    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/04/},
    author =    {Kaliraj Vairavakkalai and Natrajan Venkataraman},
    title =     {{BGP Route Reflector with Next Hop Self}},
    pagetotal = 9,
    year =      2025,
    month =     aug,
    day =       22,
    abstract =  {The procedures in BGP Route Reflection (RR) spec RFC4456 primarily deal with scenarios where the RR is reflecting BGP routes with next hop unchanged. In some deployments like Inter-AS Option C (Section 10, RFC4364), the ABRs may perform RR functionality with nexthop set to self. If adequate precautions are not taken, the RFC4456 procedures can result in traffic forwarding loop in such deployments. This document illustrates one such looping scenario, and specifies approaches to minimize possiblity of traffic forwarding loop in such deployments. An example with Inter-AS Option C (Section 10, RFC4364) deployment is used, where RR with next hop self is used at redundant ABRs when they re-advertise BGP transport family routes between multiple IGP domains.},
}