ABridges as RBridges: Transparent Routing with Simplified Multiple Spanning Trees.
draft-gibanez-trill-abridge-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Guillermo Ibanez | ||
| Last updated | 2006-06-16 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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
RBridges are link layer devices that use routing protocols as a control plane but do not target to scale up to large campus networks. This document contains an alternative proposal to link-state RBridges, named ABridges. ABridges overcome RBridges L2 network size restrictions allowing applicability to very large Ethernet campus networks while maintaining zero configuration and high performance, by assuming a topological restriction that is automatically performed. The proposal includes a two-layered network architecture with two hierarchical independent spanning tree layers. Expected convergence is fast, probably below two seconds.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)