Fixing Persistent Route Oscillation conditions in BGP RT-Constrain
draft-idr-bgp-rt-oscillation-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Dongling Duan , Keyur Patel , Jeffrey Haas | ||
| Last updated | 2017-01-07 (Latest revision 2016-07-06) | ||
| RFC stream | (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
[RFC4684] defines Multi-Protocol BGP (MP-BGP) procedures that allow BGP speakers to exchange Route Target reachability information (RT- Constrain) to restrict the propagation of Virtual Private Network (VPN) routes. In network scenarios where hierarchical route reflection (RR) is used, the existing RT-Constrain mechanism may result in persistent routing oscillations within RRs. This document describes the problem scenario and proposes solutions to address persistent routing oscillations in hierarchical RR scenario. This document updates RFC 4684 by proposing solutions to avoid the persistent routing oscillations in hierarchical RR scenario.
Authors
Dongling Duan
Keyur Patel
Jeffrey Haas
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)