Root cause notification to solve BGP path hunting
draft-keyupate-bgp-rcn-00

Document Type Expired Internet-Draft (individual)
Last updated 2010-08-08
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-keyupate-bgp-rcn-00.txt

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 (keyupate@cisco.com)
Chandra Appanna (chandra@cisco.com)
Prodosh Mohapatra (pmohapat@cisco.com)
John Scudder (jgs@juniper.net)
Jim Uttaro (uttaro@att.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)