PIM neighbor selection with ECMP routes
draft-joshi-pim-ecmp-neighbor-select-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bharat Joshi , Jithesh Kaveetil | ||
| Last updated | 2014-01-10 (Latest revision 2013-07-09) | ||
| 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
A Protocol Independent Multicast (PIM) router uses local forwarding table to select the upstream PIM neighbor towards the source or Rendezvous Point (RP). A router need to choose one upstream PIM neighbor from the list of PIM neighbors if the route for a source or RP is an Equal Cost Multipath (ECMP) route. Currently PIM routers use vendor specific algorithm to choose one neighbor. This may lead to unnecessary wastage of network resources. This draft first explains the need for a standard algorithm to select a PIM neighbor with ECMP route and then suggest such an algorithm.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)