Tree Notification to Improve Multicast Fast Reroute
draft-wijnands-rtgwg-mcast-frr-tn-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | IJsbrand Wijnands , Andras Csaszar , Jeff Tantsura | ||
| Last updated | 2013-04-18 (Latest revision 2012-10-15) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
This draft proposes using dataplane triggered notifications in order to support multicast fast reroute methods in various ways. Sending such notifications down the tree can be used to trigger fail-over in nodes not adjacent to the failure. Sending such dataplane notification up the tree can help to activate pre-built standby backup tree segments.
Authors
IJsbrand Wijnands
Andras Csaszar
Jeff Tantsura
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)