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

2. draft-ietf-l2vpn-oam-req-frmk-03.txt 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. draft-ietf-l2vpn-oam-req-frmk-03.txt 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. draft-ietf-l2vpn-oam-req-frmk-03.txt 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. draft-ietf-l2vpn-oam-req-frmk-03.txt 5 Backup Slides

6. draft-ietf-l2vpn-oam-req-frmk-03.txt 6 L2VPN OAM Layering – Service Layer CEU-PE N-PE CEBBPPPP Device View Example Scenario with Single Service Provider Network Ethernet Layer Eth AccessMPLS CoreMPLS Access Customer Service Provider

7. draft-ietf-l2vpn-oam-req-frmk-03.txt 7 OAM Domain – Service/Network Eth AccessMPLS CoreMPLS Access Customer Service Provider Customer Domain Provider Domain Operator Domain >Domains necessary to contain OAM flows & bound OAM responsibilities

8. draft-ietf-l2vpn-oam-req-frmk-03.txt 8 Maintenance End Points (MEP) & Maintenance Intermediate Points (MIP) Customer Domain Provider Domain Operator Domain Eth AccessMPLS CoreMPLS Access Customer Service Provider MPLS Domain Maintenance Point Intermediate Point >Location of MPs and IPs is dependent on Business Models & Deployment Scenarios Network OAM Service OAM PW/MPLS OAM

9. draft-ietf-l2vpn-oam-req-frmk-03.txt 9 VPLS OAM – How diff. layers come together? Ethernet link OAM PW/MPLS OAM EoSONET OAM Other OAM Network OAM Service OAM Transport Links Network Services >OAM Interworking possible to utilize OAM across Layers >However, each layer must support OAM capabilities independently L2VPN PWE3

10. draft-ietf-l2vpn-oam-req-frmk-03.txt 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)