BGP Stability Improvements
draft-li-bgp-stability-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Geoff Huston , Tony Li | ||
| Last updated | 2007-06-18 | ||
| 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
BGP is the routing protocol used to tie the Autonomous Systems (ASes) of the Internet together. The ongoing stability of BGP in the face of arbitrary inputs, both malicious and unintentional, is of primary importance to the overall stability of the Internet. The overall issue is not a new one. Previously, one aspect of stability, known as route flap damping was originally discussed in RFC 2439. In the intervening years, a great deal of experience with flap damping and other stability concerns has been accumulated. Most recently, the issue of BGP stability has been highlighted in RAWS. This document describes the experience that has been gained concerning stability in the intervening years, hypotheses about remaining problems, suggestions for experiments to be performed, and proposals for possible alternatives.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)