Root cause notification to solve BGP path hunting
draft-keyupate-bgp-rcn-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Keyur Patel , Chandra Appanna , Prodosh Mohapatra , John Scudder , Jim Uttaro | ||
| Last updated | 2010-08-08 | ||
| 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
Whenever a prefix is withdrawn using BGP withdrawal mechanism, it triggers a number of updates in certain scenarios before the prefix is completly withdrawn from the entire BGP network. This phenomenon is popularly known as _path exploration_ or _path hunting_ and occurs because of path vector property of BGP. It results in a series of unwanted or redundant transitions that overloads the BGP network. This document describes a mechanism to help limit the amount of such path exploration by defining two optional transitive path attributes for BGP: SPEAKERID_PATH and ROOT_CAUSE.
Authors
Keyur Patel
Chandra Appanna
Prodosh Mohapatra
John Scudder
Jim Uttaro
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)