PIM Neighbor Hello GenId Option
draft-ietf-pim-hello-genid-01
| Document | Type | Expired Internet-Draft (pim WG) | |
|---|---|---|---|
| Last updated | 1999-06-22 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-pim-hello-genid-01.txt
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
Billy Ng
(bng@NortelNetwork.com)
Y. Li
(yli@baynetworks.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)