120 likes | 251 Views
VLAN Mapping and TRILL draft-ietf-trill-rbridge-vlan-mapping-04.txt. Radia Perlman Radia@alum.mit.edu. Issue. Bridges currently do VLAN mapping. Issue. Bridges currently do VLAN mapping Intentionally, even. Why?. Merge two clouds
E N D
VLAN Mapping and TRILLdraft-ietf-trill-rbridge-vlan-mapping-04.txt Radia Perlman Radia@alum.mit.edu VLAN Mapping
Issue • Bridges currently do VLAN mapping VLAN Mapping
Issue • Bridges currently do VLAN mapping • Intentionally, even VLAN Mapping
Why? • Merge two clouds • VLAN “A” in one cloud means something different from VLAN “A” in another cloud • VLAN “A” in one cloud should be the same as VLAN “B” in the other cloud • Separate a community • (perhaps) make VLAN “A” into two communities (topology has to be cooperative) VLAN Mapping
What we want • We want only RBridges connecting the two clouds to have any notion this is going on VLAN Mapping
RB1 RB2 west east RB3 VLAN Mapping
Configure ports RB1 RB2 west east RB3 VLAN Mapping
RB1, RB2, and RB3 know: (East, VLAN A) = (West, VLAN B) RB1 RB2 west east RB3 When forwarding data between East and West, change the (inner) VLAN tag VLAN Mapping
Other nits • ESADI about VLAN A endnodes tagged by using (inner) VLAN tag=A • So VLAN A ESADI turns into VLAN B ESADI as it is forwarded from East to West • To detect misconfiguration cut set RBridge MAY announce its mappings in its LSP VLAN Mapping
Other nits, cont’d • If RB1 is configured to map (East, VLAN A) to (West, VLAN B), then RB1 MUST announce (in RB1’s LSP) that RB1 is attached to both VLAN A and VLAN B (regardless of whether RB1 is appointed forwarder for anything) • The reason for this is so that, e.g., multicast for VLAN A originating in West will get to RB1 VLAN Mapping
Multicast groups • RB1 MUST announce that RB1 has an IPv4 and IPv6 multicast router in VLAN B attached to RB1 (in RB1’s LSP) VLAN Mapping