TRILL-campus-name
draft-umair-multiple-trill-campus-to-lan-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mohammed Umair | ||
| Last updated | 2015-02-13 (Latest revision 2014-08-12) | ||
| 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
TRILL supports multi-access LAN (Local Area Network) links that can have multiple end stations and RBridges attached. Where multiple RBridges are attached to a link, native traffic to and from end stations on that link is handled by a subset of those RBridges called "Appointed Forwarders", with the intent that native traffic in each VLAN (Virtual LAN) be handled by at most one RBridge. But when two trill campuses are connected through a LAN network, AF selection for each campus should be selected differently. This type of scenario occurs when two different TRILL Campuses are connected to single LAN and want access to common set of VLAN's. The following paper is an attempt to handle such scenario.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)