TRILL Resilient Distribution Trees
draft-ietf-trill-resilient-trees-02
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Mingui Zhang , Tissa Senevirathne , Janardhanan Pathangi , Ayan Banerjee , Anoop Ghanwani | ||
Last updated | 2015-07-01 (Latest revision 2014-12-28) | ||
Replaces | draft-zhang-trill-resilient-trees | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | Donald E. Eastlake 3rd | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | "Donald E. Eastlake 3rd" <d3e3e3@gmail.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
TRILL protocol provides multicast data forwarding based on IS-IS link state routing. Distribution trees are computed based on the link state information through Shortest Path First calculation. When a link on the distribution tree fails, a campus-wide recovergence of this distribution tree will take place, which can be time consuming and may cause considerable disruption to the ongoing multicast service. This document specifies how to build backup distribution trees to protect links on the primary distribution tree. Since the backup distribution tree is built up ahead of the link failure, when a link on the primary distribution tree fails, the pre-installed backup forwarding table will be utilized to deliver multicast packets without waiting for the campus-wide recovergence. This minimizes the service disruption. This document updates RFC 6325.
Authors
Mingui Zhang
Tissa Senevirathne
Janardhanan Pathangi
Ayan Banerjee
Anoop Ghanwani
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)