Control Plane Requirements for TRILL Active/Active Edge
draft-zhang-trill-active-active-cp-req-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Mingui Zhang , Russ White , Hongjun Zhai | ||
Last updated | 2014-04-24 (Latest revision 2013-10-21) | ||
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 Active/Active Edge enables a Multi-Chassis Link Aggregation Group to connect to multiple RBridges which can ingress and egress data traffic for the same VLAN at the same time. The purpose of introducing the TRILL Active/Active Edge is to increase the access bandwidth and resilience. This new access type puts forward new requirements for TRILL control plane. Current TRILL control plane need be extended in order to make the TRILL Active/Active Edge operational. Requirements are developed in this document as the guidelines for designing those specific control plane functions.
Authors
Mingui Zhang
Russ White
Hongjun Zhai
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)