VPLS OAM Requirements & Framework draft-mohan-sajassi-l2vpn-oam-req-frmk-00.txt

1. VPLS OAM Requirements & Frameworkdraft-mohan-sajassi-l2vpn-oam-req-frmk-00.txt Dinesh Mohan (Nortel) mohand@nortelnetworks.com Ali Sajassi (Cisco) sajassi@cisco.com IETF-60, San Diego August 3, 2004

2. Contributors & Acknowledgements • Other contributors • Norm Finn (Cisco) • Vasile Radoaca (Nortel) • Shahram Davari (PMC Sierra) • Other Standards Participants • ITU-T (Q.3/13) • IEEE (802.1) • MEF

3. Past Discussions • IETF-59 (Seoul) • draft-mohan-sajassi-l2vpn-vpls-fm-00.txt • Draft-sajassi-mohan-l2vpn-vpls-pm-00.txt • Discussions & Agreements • L2VPN WG should work on VPLS specific OAM mechanisms • L2VPN WG should work on VPLS specific OAM requirements • Support other Standard Organizations in their work • L2VPN WG should identify extensions to existing IETF protocols for VPLS specific OAM • Other Standards Organizations would continue working on non-VPLS specific OAM

4. Scope • Within L2VPN Charter • “L2VPN-specific OAM extensions--extensions to existing OAM solutions for VPLS, VPWS, and IP-only L2VPNs” • OAM Requirements and Framework for VPLS, VPWS, and IP-only L2VPNs is within scope • Alignment with other Standard Bodies • ITU-T Q.3/13, IEEE 802.1, MEF

5. VPLS OAM Requirements

6. Requirements Areas • Discovery • Connectivity Fault Management • Connectivity Fault Detection • Connectivity Fault Verification • Connectivity Fault Localization • Connectivity Fault Alarm • Frame Loss • Frame Delay • Frame Delay Variation • Data Path Execution • Scalability • Extensibility • Security • Transport Independence • Application Independence • Backward Compatibility • Availability

7. VPLS OAM Framework

8. Ethernet Layer VPLS OAM Layering – Service Layer Customer Service Provider Customer Eth Access MPLS Core MPLS Access Device View CE U-PE B B N-PE P P P N-PE P U-PE CE Example Scenario with Single Service Provider Network

9. OAM Domain – Service/Network Customer Service Provider Customer Eth Access MPLS Core MPLS Access Customer Domain Provider Domain Operator Domain Operator Domain Operator Domain • Domains necessary to contain OAM flows & bound OAM responsibilities

10. Maintenance Point Intermediate Point Maintenance Points (MP) & Intermediate Points (IP) Customer Service Provider Customer Eth Access MPLS Core MPLS Access Customer Domain Service OAM Provider Domain Network OAM Operator Domain Operator Domain Operator Domain PW/MPLS OAM MPLS Domain MPLS Domain • Location of MPs and IPs is dependent on Business Models & Deployment Scenarios

11. Services Service OAM Network Network OAM Transport Links Ethernet link OAM PW/MPLS OAM EoSONET OAM Other OAM VPLS OAM – How diff. layers come together? • OAM Interworking possible to utilize OAM across Layers • However, each layer must support OAM capabilities independently

12. What’s next?

13. Next Steps • Proposal to accept the document as a Work Group Item • Further discussion & participation on VPLS OAM FM & PM work • Continued coordination with other bodies • IEEE 802.1 • ITU-T Q.3/13 • MEF • Extend this document as an overall L2VPN Requirements and Framework document? • Include VPWS Framework and Requirements with solutions in PWE3 • Include L2VPN OAM Interworking Framework and Requirements with solutions in L2VPN/PWE3 WGs