140 likes | 343 Views
VPLS PE Model with E-Tree Support. draft-jiang-l2vpn-vpls-etree-pe-02.txt. Yuanlong Jiang ( yljiang@huawei.com ) Lucy Yong ( lucyyong@huawei.com ) Manuel Paul ( manuel.paul@telekom.de ) Frederic Jounay ( frederic.jounay@orange-ftgroup.com ). Backgrounds.
E N D
VPLS PE Model with E-Tree Support draft-jiang-l2vpn-vpls-etree-pe-02.txt Yuanlong Jiang (yljiang@huawei.com) Lucy Yong (lucyyong@huawei.com) Manuel Paul (manuel.paul@telekom.de) Frederic Jounay (frederic.jounay@orange-ftgroup.com) 79th IETF - Beijing
Backgrounds • E-Tree Requirements in multiple SDOs • Service Definition: MEF 6.1,MEF 10.2 • Mobile backhaul: MEF 22 • Broadband Network Architecture: BBF WT-145 • MPLS in Carrier Ethernet: BBF WT-224 • Lack of E-Tree support in VPLS standard • Non-standard mechanism for single root topology • Single VSI + extended split horizon mechanism • No VPLS support for multi-roots topology • Multiple nodes with root & leaf attached in a single domain • Multiple roots and leaves located diversely across multiple domains 79th IETF - Beijing
Highlights of the draft • Using VLANs to solve E-Tree in VPLS– the same flavor of E-Tree solution as Ethernet • Cover all VPLS PE models and their interworking scenarios • Benefits • A converged solution compatible with both Ethernet and VSI forwarding planes and applicable to diverse network scenarios • No change to VPLS architecture and PW layer semantics, standard work can be minimized • Scalability with only a single VSI and a single suite of PWs needed 79th IETF - Beijing
VSI Fwder NSP Possible VPLS PE Models for E-Tree PE with Bridge Module RFC 4664 & draft-ietf-l2vpn-vpls-bridge-interop draft-ietf-l2vpn-pbb-vpls-pe-model PE CE AC R PW Bridge Module VSI Fwder L PE CE AC R PE without Bridge Module RFC 3985 & draft-key-l2vpn-vpls-etree-reqt PW L NSP: Native Service Processing; optional 79th IETF - Beijing
E-Tree Solution in Ethernet L R • IEEE uses a pair of SVLANs - Trunk SVLAN and Branch SVLAN to support generic E-Tree, which is incorporated in the latest IEEE 802.1Q standard Root UNI Leaf UNI Root Trunk UNI R Branch MEN A Leaf UNI L 79th IETF - Beijing
VLAN Based E-Tree Solution in VPLS Bridge 2 VLANs into a VSI PE1 PE3 CE1 CE5 AC R VSI Fwder PW Root Bridge Module NSP L VSI Fwder CE2 Leaf L VPLS CE3 MEN R PW VSI Fwder Root Bridge CE4 Leaf L PE2 Tagged PW with 2 VLANs 79th IETF - Beijing
VLAN Mapping Options VLAN mapping options PE1 PE3 CE1 CE5 AC R VSI Fwder PW Root Bridge Module NSP L VSI Fwder CE2 Leaf L VPLS CE3 MEN R PW VSI Fwder Root Bridge CE4 Leaf L PE2 VLAN mapping options 79th IETF - Beijing
E-Tree Processing • PW works in Taggedmode • PEmay be provided with VLAN mapping capability • Remote Root VLAN <==> Local Root VLAN • Remote Leaf VLAN <==> Local Leaf VLAN • At the ingress PE, Ethernet frames with Root or Leaf VLAN encapsulated in the same PW and transparently label switched • At the egress PE, Ethernet frames translated into Local Root or Leaf VLAN • Leaf VLAN traffic filtered either at Leaf UNI on egress PE, or on ingress PE when its egress PE is a pure leaf PE 79th IETF - Beijing
Extension of LDP Protocol • A new E-Tree sub-TLV is defined for PW interface parameters TLV • PEs negotiate the support of E-Tree when a PW is set up • Root VLAN ID and Leaf VLAN ID carried in the sub-TLV • Several bits to help the negotiation procedure 79th IETF - Beijing
Next Step • The authors would like to request more WG feedbacks on mailing list • To be accepted as WG draft? 79th IETF - Beijing
Backup Slides 79th IETF - Beijing
E-Tree Solutions in IEEE (multi-domain) • Trunk SVLAN and Branch SVLAN are also used to provide E-Tree service across multiple domains where roots and leaves located diversely Root UNI Leaf UNI Root UNI NNI NNI Trunk MEN C Branch MEN A MEN B Leaf UNI Leaf UNI Leaf UNI 79th IETF - Beijing
Asymmetric VLAN Mapping in IEEE • Ingress and egress frames at Root and Leaf UNI are tagged with a single C-VLAN • In the network between Roots and Leaves, frames are tagged with Trunk or Branch S-VLAN Ingress Translation Egress Translation Trunk S-VLAN ==>C-VLAN Branch S-VLAN==>C-VLAN At Root C-VLAN ==>Trunk S-VLAN Trunk S-VLAN ==>C-VLAN Branch S-VLAN Discarded At Leaf C-VLAN==>Branch S-VLAN 79th IETF - Beijing
Thank You 79th IETF - Beijing