PIM Neighbor Hello GenId Option
draft-ietf-pim-hello-genid-01
| Document | Type |
Expired Internet-Draft
(pim WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Billy C. Ng , Y. Li | ||
| Last updated | 1999-06-22 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 memo addresses an issue with the current PIM in Sparse Mode. In the case of router reboot, PIM networks have to converge slowly and suffer long outage of traffic flows. This memo proposes a Generation Identifier (GenId) Option in PIM Hello messages. It enables neighbors to quickly detect router reboot and thus to synchronize RP-Set information and forwarding states by triggering Bootstrap and Join/Prune messages to the rebooted router. The rebooted router then is able to quickly recover from the reboot.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)