1 / 11

VPLS PE Model with E-Tree Support

VPLS PE Model with E-Tree Support. draft-jiang-l2vpn-vpls-etree-pe-00.txt. Yuanlong Jiang ( yljiang@huawei.com ). E-Tree Requirements on VPLS. E-Tree Service An EVC service defined in MEF (MEF 6.1, MEF 10.2) Rooted Multipoint EVC (Multi-root possible), each UNI is either Root or Leaf

carlos-cervantes
Download Presentation

VPLS PE Model with E-Tree Support

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VPLS PE Model with E-Tree Support draft-jiang-l2vpn-vpls-etree-pe-00.txt Yuanlong Jiang (yljiang@huawei.com) 77th IETF - Anahaim

  2. E-Tree Requirements on VPLS • E-TreeService • An EVC service defined in MEF (MEF 6.1,MEF 10.2) • Rooted Multipoint EVC (Multi-root possible), each UNI is either Root or Leaf • Connectivity: Root to Leaf, Leaf to Root, Root to Root • Prohibited: Leaf to Leaf • Problems • VPLS is based on full mesh connectivity, how to provide E-Tree service in VPLS and guarantee the segregation between the leaves when E-Tree is a multi-rooted tree? • History • 2009.09, problem of E-Tree in PBB-VPLS first raised in BBF • 2009.10, two I-Ds proposed to solve the general problem of E-Tree in VPLS in IETF • 2010.01, two presentations discussed to solve the problem of E-Tree in Ethernet in IEEE 77th IETF - Anahaim

  3. E-Tree Challenges in VPLS CE Leaf Leaf Root UNI CE UNI UNI CE Leaf UNI Leaf Root CE UNI UNI CE UNI CE Leaf CE How to provide E-Tree service with scalability in the MPLS/VPLS network? How to do Leaf segregation when PE dual feed both Root & Leaf? 77th IETF - Anahaim

  4. E-Tree Scheme in IEEE • Asymmetric VLAN (IEEE 802.1Q) • Root/Leafattached to bridge in untaggedmode • Configure PVID and member set for each access port • Stephen Haddock proposed to use only a pair of Trunk VLAN and Branch VLAN for muti-root E-Tree, this capability is anticipated to be provided in future revisions of 802.1Q Server Member Sets: Red – Port 1, 2 Blue – Port 3 Green-Port 3 Untagged Sets: Red – Port 1, 2 Blue – Port 3 Green-Port 3 R Port3 PVID=3 PVID=2 Port2 PVID=1 Port1 L L 77th IETF - Anahaim

  5. VPLS PE Model Defined in IETF (Model 2) draft-ietf-l2vpn-vpls-bridge-interop-04 CE AC C PW CVLAN Bridge S-VLAN-1 VSI C SVLAN Bridge C PW CVLAN Bridge S-VLAN-2 VSI C VPLS PE Model VPLSPE Model (802.1ad)with 2 stages of bridge - a typical implementation 77th IETF - Anahaim

  6. A Model 2 Compatible E-Tree Scheme CE AC R PW CVLAN Bridge Root VLAN VSI L SVLAN Bridge R PW CVLAN Bridge VSI Leaf VLAN L VPLS PEModel – 2 VSI per E-Tree 2 VSIs and 2 sets of PWs are needed per E-Tree if we incorporate the enhanced Asymmetric VLAN into the VPLS PE model 2 77th IETF - Anahaim

  7. Enhanced Model 2 (Tree VSI) Bridge 2 S-VLANsinto Tree VSI CE AC R PW Root CVLAN Bridge T-VSI Leaf L SVLAN Bridge R PW CVLAN Bridge S-VLAN-2 VSI L Enhanced VPLS PE • Tree VSI (T-VSI) attached to S-VLAN bridge with Root VLANand Leaf VLAN, and work in shared VLAN learning • Traffic from Root or LeafUNI distributed into Root VLANand Leaf VLAN • Only one T-VSI and one set of PWs needed per E-Tree 77th IETF - Anahaim

  8. Interconnection Scenario CE PE1 AC R PW Root SVLAN Bridge CVLAN Bridge T-VSI Leaf L R PW Root CVLAN Bridge SVLAN Bridge T-VSI L Leaf PE2 PE Interconnection with T-VSI • Either PE1 or PE2 can do VLAN translation (either when enter or exit PW) • Bridge module filters Leaf VLAN traffic on the egress Leaf port 77th IETF - Anahaim

  9. PW Processing • PW works in Taggedmode • At least one end of PEprovided with the VLAN mapping capability • Remote Root VLAN <-> Local Root VLAN • Remote Leaf VLAN <-> Local Leaf VLAN • At the PW ingress, Root or Leaf VLAN encapsulated in the same PW and transparently label switched • At the PW egress, Ethernet frames translated into Local Root or Leaf VLAN 77th IETF - Anahaim

  10. Extension of LDP Protocol • E-Tree sub-TLV is defined as one of interface parameters • PEs negotiate their supports of E-Tree (T-VSI) when the PW is set up • Root VLAN ID and Leaf VLAN ID carried in the sub-TLV • P bit indicate that PE is attached with “Pure Leaves” • R bit is a request flag for “Remote VLAN Translation” 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | E-Tree | Length=8 | Reserved |P|R| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Root VLAN ID | Leaf VLAN ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 77th IETF - Anahaim

  11. Next Step • The authors would like to request more WG feedbacks 77th IETF - Anahaim

More Related