RBridge: ESADI-Extension
draft-zhai-trill-esadi-extension-for-rbv-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hongjun Zhai , Xuehui Dai | ||
| Last updated | 2013-04-10 (Latest revision 2012-10-07) | ||
| 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
In a virtual RBridge(RBv), traffic from end station ES1 to ES2 will enter a TRILL campus through one member RBridge RB1 of RBv, but reverse traffic might choose another member RBridge RB2 to leave TRILL campus. If RB1 can't obtain the location of ES2 via other means, it has to treat the traffic to ES2 as unknown destination traffic and multicasts it in TRILL campus. However, if RB2 can share its learned MAC addresses with RB1, the above problem can be resolved. Based on appropriate extensions of ESADI, this document proposes, in control plane, an approach for informations synchronization within a group of RBridges. Current informations mainly include end station addresses, but may include other informations in the future.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)