PIM fast recovery mechanism
draft-bhattacharya-pim-fast-recovery-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Indranil Bhattacharya | ||
| Last updated | 2015-07-20 (Latest revision 2015-01-12) | ||
| 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
When a PIM router reboots, either because of uncontrolled failover or because of ISSU, it needs to reconcile the PIM entries. For this, rebooting router sends PIM hello with new GenId. In reponse, neighbors send a new hello and replay PIM J/P message. Regardless an application maintaing full mroute states, the rebooting route must wait for this replay to complete only after which it can mark the oif reconciliation complete. This process is undeterministic today. This draft proposes a new mechanism to achieve a faster reconcilaition time. For this a new Hello option and a new message type has been introduced.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)