1. Requirements for MEF E-Tree Support in VPLS draft-key-l2vpn-vpls-etree-reqt-02 Presenter : Manuel Paul, Deutsche Telekom IETF79, Nov 2010 Beijing, China Authors : - Raymond Key, Telstra - Simon Delord, Telstra - Frederic Jounay, France Telecom - Lu Huang, China Mobile - Zhihua Liu, China Telecom - Manuel Paul, Deutsche Telekom - Ruediger Kunze, Deutsche Telekom - Nick Del Regno, Verizon - Joshua Rogers, Time Warner Cable Note: Simon Delord has changed affiliation to Alcatel-Lucent in Nov 2010 1

2. Update in 02-Version This is a requirement draft, not a solution draft. The 00-version has been presented in IETF78 July 2010. The 02-version was published in October 2010. Add Authors –Lu Huang, China Mobile –Zhihua Liu, China Telecom –Manuel Paul, Deutsche Telekom –Ruediger Kunze, Deutsche Telekom –Nick Del Regno, Verizon –Joshua Rogers, Time Warner Cable 2

3. Update in 02-Version Add Section 3.4. Generic E-Tree Service –Emphasize the need to support Multiple Roots. –Emphasize the need to support all the following traffic flows Ethernet Unicast from Root to Leaf Ethernet Unicast from Leaf to Root Ethernet Unicast from Root to Root Ethernet Broadcast/Multicast from Root to Roots & Leafs Ethernet Broadcast/Multicast from Leaf to Roots 3

4. Update in 02-Version Section 4.2. Leaf-to-Leaf Communication Restriction –Explicitly state A problem occurs when there are two or more PEs with both Root AC and Leaf AC –Simplify the diagram and add examples in order to explain the problem precisely –Mention possibility to get around the problem without extension to current standard VPLS but come with complexity and deployment constraints 4

5. Update in 02-Version Add Appendix A. Frequently Asked Questions –Are E-Tree requirements addressed in the VPMS requirement draft? [Short Answer: For generic E-Tree service, VPMS will not be able to meet the requirements.] –Are there any potential deployment scenarios for a VPLS Only solution? [Short Answer: There are potential deployment scenarios for a VPLS Only solution. Three examples are given.] Some other minor wording and format changes. 5

6. Recap the Problem Use VPLS to emulate an E-Tree service over a MPLS network +---------+ +---------+ | PE1 | | PE2 | +---+ | +---+ | | +---+ | +---+ |CE1+-----AC1----+--+ | | | | +--+----AC3-----+CE3| +---+ (Root AC) | | V | | Ethernet | | V | | (Root AC) +---+ | | S +--+-----PW-----+--+ S | | +---+ | | I | | | | I | | +---+ |CE2+-----AC2----+--+ | | | | +--+----AC4-----+CE4| +---+ (Leaf AC) | +---+ | | +---+ | (Leaf AC) +---+ +---------+ +---------+ When PE2 receives a frame from PE1 via the Ethernet PW, - PE2 does not know whether the ingress AC is a Leaf AC or not - PE2 does not have sufficient information to enforce the Leaf-to-Leaf communication restriction Examples: - CE2 sends a Broadcast/Multicast frame to PE1 via AC2 - CE2 sends a Unicast frame to PE1 via AC2, destination address in Ethernet header equal to CE4's MAC address 6

7. Recap the Requirements Functional Requirements –MUST prohibit communication between any two Leaf ACs. –MUST allow multiple Root ACs in a VPLS instance. –MUST allow Root AC and Leaf AC of a VPLS instance co-exist on any PE. Backward Compatibility –SHOULD minimise impact on existing VPLS solution. –SHOULD allow a VPLS instance composed of both PEs supporting the solution and PEs not supporting it. 7

8. MEF E-Tree Support in VPLS More network operators have expressed their need for a VPLS-based MEF E-Tree solution. This draft is intended to be a requirement reference for potential solutions. We request this be adopted as a Working Group Draft. Thank you very much. 8