Making Route Flap Damping Usable
draft-ymbk-rfd-usable-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Cristel Pelsser , Keyur Patel , Olaf Maennel , Prodosh Mohapatra , Randy Bush | ||
| Last updated | 2012-06-24 (Latest revision 2011-12-22) | ||
| 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
Route Flap Damping (RFD) was first proposed to reduce BGP churn in routers. Unfortunately, RFD was found to severely penalize sites for being well-connected because topological richness amplifies the number of update messages exchanged. Many operators have turned RFD off. Based on experimental measurement, this document recommends adjusting a few RFD algorithmic constants and limits, to reduce the high risks with RFD, with the result being damping a non-trivial amount of long term churn without penalizing well-behaved prefixes' normal convergence process.
Authors
Cristel Pelsser
Keyur Patel
Olaf Maennel
Prodosh Mohapatra
Randy Bush
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)