IP Fast Reroute for BGP-Only Networks
draft-abdelsalam-rtgwg-ipfrr-bgp-only-network-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ahmed Abdelsalam , Clarence Filsfils , Eddie Ruan , Dezhong Cai | ||
| Last updated | 2026-09-03 (Latest revision 2026-03-02) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
IP Fast Reroute (IPFRR) [RFC5714] is widely deployed in IP networks to provide protection against failures by invoking locally determined repair paths. Traditional IPFRR deployments require the use of a link-state IGP to provide locally computed repair paths. This document provides the problem statement and outlines a solution to enable IPFRR computation and deployment in BGP-only networks. The solution maintains standard BGP routing operations while providing fast reroute capabilities comparable to IGP-based deployments.
Authors
Ahmed Abdelsalam
Clarence Filsfils
Eddie Ruan
Dezhong Cai
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)