L2VPN OAM Requirements & Framework draft-ietf-l2vpn-oam-req-frmk-03.txt

1. L2VPN OAM Requirements & Frameworkdraft-ietf-l2vpn-oam-req-frmk-03.txt Dinesh Mohan (Nortel) mohand@nortel.com Ali Sajassi (Cisco) sajassi@cisco.com IETF-63, Paris August 03, 2005

2. Overview • L2VPN OAM Framework • OAM Layering in context of L2VPN WG technologies • L2VPN Service Layer, PW Layer, PSN Layer • Customer, Service Provider, Network Operators roles • OAM Constructs • OAM Domains, MEPs and MIPs • L2VPN OAM Requirements • Requirements for L2VPN Service OAM • Expectation is that native technology OAM will be used (e.g. IEEE 802 .1ag) • Liaison activities are already taking place • Requirements for underlying facilities OAM e.g. PW OAM

3. Status Update • OAM framework is being adopted for other related work • e.g. draft-delord-pwe3-oam-applications-01.txt • draft-ietf-l2vpn-oam-req-frmk-03.txt update submitted • Section 7 added to discuss specific OAM requirements for L2VPN network layer e.g. PW OAM to support L2VPN Services • VPWS OAM references draft-delord-pwe3-oam-applications-01.txt • Duplication of information is intended to be avoided between two drafts. • IPLS OAM is FFS

4. Next Steps • Add VPWS OAM Requirements • Depending on outcome from PWE3 discussions on draft-delord-pwe3-oam-applications-01.txt • Continue refining the requirements on PW OAM • Other editorial updates • Update Acknowledgements (TBD) • Simon Delord/Philippe Nigel - France Telecom • Neil Harrison - British Telecom • Lior Shabtay/Dan Cauchy - Atrica

5. Backup Slides

6. Ethernet Layer L2VPN 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

7. 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

8. Maintenance Point Intermediate Point Maintenance End Points (MEP) & Maintenance Intermediate Points (MIP) 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

9. 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? L2VPN PWE3 • OAM Interworking possible to utilize OAM across Layers • However, each layer must support OAM capabilities independently

10. Status Update • IETF-62 (Minneapolis – current meeting) • draft-ietf-l2vpn-oam-req-frmk-02.txt update submitted • Editorial updates based on discussion during IETF-61 meeting • IETF-61 (Washington D.C.) • draft-ietf-l2vpn-oam-req-frmk-01.txt discussed • Agreement to continue work for L2VPN Service OAM • Agreement to specifically identify requirements on underlying technologies supporting L2VPN e.g. PWs and/or LSPs • IETF-60 (San Diego) • Draft-ietf-l2vpn-oam-req-frmk-00.txt submitted • Overwhelming support for draft-mohan-sajassi-oam-req-frmk-00.txt to progress as a WG draft (during IETF-59 Seoul meeting and mailing list)