Skip to main content

Aware Spanning Tree Topology Change on RBridges

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Yizhou Li , Hao Weiguo , Jon Hudson , Naveen Nimmu , Anoop Ghanwani
Last updated 2014-05-25 (Latest revision 2013-11-21)
RFC stream (None)
Intended RFC status (None)
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:


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.


Yizhou Li
Hao Weiguo
Jon Hudson
Naveen Nimmu
Anoop Ghanwani

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)