Oscillation Prevention in I-BGP
draft-klockar-ibgp-oscillation-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tomas Klockar | ||
| Last updated | 2005-07-11 | ||
| 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
This memo presents a technique for preventing oscillations in I-BGP. The idea is to utilize already known data in routers to stop oscillation. This builds on the fact that routers can send implicit and explicit withdrawals. Implicit withdrawals are redefined to mean that the route still exist and explicit withdrawal to mean that the route has disappeared. The router can detect and avoid oscillation by storing the implicit withdrawn routes and using them to rule out other routes. The cost is more cheap memory for the RIB-In but no extra expensive memory is needed in the forwarding table.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)