TRILL: Resilient Distribution Trees
draft-ietf-trill-resilient-trees-09
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Mingui Zhang , Tissa Senevirathne , Janardhanan Pathangi , Ayan Banerjee , Anoop Ghanwani | ||
| Last updated | 2018-07-26 (latest revision 2018-01-22) | ||
| Replaces | draft-zhang-trill-resilient-trees | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Donald Eastlake | ||
| Shepherd write-up | Show (last changed 2017-10-18) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Alia Atlas | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-trill-resilient-trees-09.txt
Abstract
The TRILL (Transparent Interconnection of Lots of Links) 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 re-convergence 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 re-convergence. This minimizes the service disruption. This document updates RFC 6325.
Authors
Mingui Zhang
(zhangmingui@huawei.com)
Tissa Senevirathne
(tsenevir@gmail.com)
Janardhanan Pathangi
(path.jana@gmail.com)
Ayan Banerjee
(ayabaner@cisco.com)
Anoop Ghanwani
(anoop@alumni.duke.edu)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)