Tree Notification to Improve Multicast Fast Reroute
draft-wijnands-rtgwg-mcast-frr-tn-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | IJsbrand Wijnands , Luc De Ghein , Gabor Sandor Envedi , Andras Csaszar , Jeff Tantsura | ||
| Last updated | 2014-07-28 (Latest revision 2014-01-24) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-wijnands-rtgwg-mcast-frr-tn-02.txt
Abstract
This draft proposes dataplane triggered Tree Notifications to support multicast fast reroute for PIM and mLDP. These Tree Notifications are initiated by a node detecting the failure to a Repair Node downstream. A Repair Node is a node that has a pre-built backup path that can circumvent the failure. Using this mechanism, a Repair Node has the ability to learn about non-local failures quickly without having to wait for the IGP to convergence. This draft also covers an optional method to avoid bandwidth usage on the pre-built backup path.
Authors
IJsbrand Wijnands
Luc De Ghein
Gabor Sandor Envedi
Andras Csaszar
Jeff Tantsura
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)