A Pseudo-Protocol for BGP Next Hop Cost Manipulation
draft-mitchell-rtgwg-pseudo-bgp-nh-cost-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jon Mitchell | ||
| Last updated | 2016-04-21 (Latest revision 2015-10-19) | ||
| 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 describes a local router implementation option that provides a facility for the manipulation of the costs of IGP learned routes that are utilized as BGP NextHops rather than using the SPF calculated cost to the same route when running the BGP path selection algorithm. The result is something that works like a pseudo-routing protocol but only impacting the BGP decision making process.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)