The problem statement of RBridge edge group state synchronization
draft-hao-trill-rb-syn-03
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Hao Weiguo , Yizhou Li , Liang Xia , Hongjun Zhai | ||
Last updated | 2014-12-07 (Latest revision 2014-06-05) | ||
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 TRILL multi-homing scenario, the concept of virtual RBridge in [TRILLPN], was introduced to address the MAC flip-flopping problem at remote RBridges. Based on virtual RBridge mechanism, Coordinated Multicast Trees (CMT) solution in [CMT] was introduced to solve the related RPF issues. In this document, additional problems are described regarding virtual Bridges members' state synchronization in multi-homing scenario, including virtual RBridge membership auto discovery, pseudo-nickname static configuration consistency check, dynamic pseudo-nickname allocation, CMT configuration synchronization ,LACP configuration and state synchronization, node/link failure detection, MAC table synchronization, DHCP snooping information, and dynamically joined VLANs and multicast groups. To address these problems, a communication protocol among members of a virtual RBridge group should be provided. Requirements for this protocol are also discussed.
Authors
Hao Weiguo
Yizhou Li
Liang Xia
Hongjun Zhai
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)