<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-rtgwg-bgp-pic" target="https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-bgp-pic-23">
   <front>
      <title>BGP Prefix Independent Convergence</title>
      <author initials="A." surname="Bashandy" fullname="Ahmed Bashandy">
         <organization>HPE</organization>
      </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Mohapatra" fullname="Prodosh Mohapatra">
         <organization>Sproute Networks</organization>
      </author>
      <author initials="Y." surname="Qu" fullname="Yingzhen Qu">
         <organization>Futurewei Technologies</organization>
      </author>
      <date month="February" day="15" year="2026" />
      <abstract>
	 <t>   In a network comprising thousands of BGP peers exchanging millions of
   routes, it is desirable to restore traffic after failure in a time
   period that does not depend on the number of BGP prefixes.

   This document describes an architecture by which traffic can be re-
   routed to Equal Cost Multi-Path (ECMP) or pre-calculated backup paths
   in a timeframe that does not depend on the number of BGP prefixes.
   The objective is achieved through organizing the forwarding data
   structures in a hierarchical manner and sharing forwarding elements
   among the maximum possible number of routes.  The described technique
   yields prefix independent convergence while ensuring incremental
   deployment, complete automation, and zero management and provisioning
   effort.  It is noteworthy to mention that the benefits of BGP Prefix
   Independent Convergence (BGP-PIC) are hinged on the existence of more
   than one path whether as ECMP or primary-backup.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-rtgwg-bgp-pic-23" />
   
</reference>
