Aware Spanning Tree Topology Change on RBridges
draft-yizhou-trill-tc-awareness-03

 
Document Type Expired Internet-Draft (individual)
Last updated 2014-05-25 (latest revision 2013-11-21)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-yizhou-trill-tc-awareness-03.txt

Abstract

When a local LAN running spanning tree protocol connecting to TRILL campus via more than one RBridge, there are several ways to perform loop avoidance. One of them illustrated by RFC6325 [RFC6325] A.3 was to make relevant ports on edge RBridges involving in spanning tree calculation. When edge RBridges are emulated as a single highest priority root, the local bridged LAN will be naturally partitioned after running spanning tree protocol. This approach achieves better link utilization and intra-VLAN load balancing in some scenarios. This document describes how the edge RBridges react to topology change occurring in bridged LAN in order to make the abovementioned spanning tree approach function correct.

Authors

Li Yizhou (liyizhou@huawei.com)
Hao Weiguo (haoweiguo@huawei.com)
Jon Hudson (jon.hudson@gmail.com)
Naveen Nimmu (naveen@broadcom.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.)