70 likes | 239 Views
Radia Perlman Radia.Perlman@sun.com. TRILL issue: VLAN learning. Issue: Should RBridges only see VLAN membership of VLANs they attach to?. Currently spec says just learn endnodes from directly attached VLANs. Advantage of seeing all VLAN memberships.
E N D
Radia Perlman Radia.Perlman@sun.com TRILL issue: VLAN learning
Issue: Should RBridges only see VLAN membership of VLANs they attach to?
Currently spec says just learn endnodes from directly attached VLANs
Advantage of seeing all VLAN memberships • If R1 is attached to VLAN A, and then sees that MAC address X is advertised on VLAN B, then R1 can time X out sooner, or ping it, or something
In current spec • In current spec, VLAN A membership LSPs only go to RBridges directly attached to VLAN A • Other RBridges might forward VLAN A LSPs as data, but not store them, or look at them • VLAN A instance of IS-IS looks like one link
Disadvantages of seeing all VLAN endnodes • More information to store and look through, for RBridges not in that VLAN • Less separation between VLANs (an endnode in VLAN B can claim to be a MAC address in VLAN A, creating a DOS opportunity) • There might legitimately be local MAC assignments, overlapping in the VLANs • Flooding of VLAN information will be less optimal, since it will have to reach all RBridges
Conclusion of mailing list • Leave the design as it is • Check if the spec is sufficiently clear that this is the way it works