<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hao-trill-rb-syn" target="https://datatracker.ietf.org/doc/html/draft-hao-trill-rb-syn-03">
   <front>
      <title>The problem statement of RBridge edge group state synchronization</title>
      <author initials="H." surname="Weiguo" fullname="Hao Weiguo">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="Y." surname="Li" fullname="Yizhou Li">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="L." surname="Xia" fullname="Liang Xia">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="H." surname="Zhai" fullname="Hongjun Zhai">
         <organization>ZTE Corporation</organization>
      </author>
      <date month="June" day="5" year="2014" />
      <abstract>
	 <t>   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&#x27; 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-hao-trill-rb-syn-03" />
   
</reference>
