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

1. L2VPN OAM Requirements & Frameworkdraft-ietf-l2vpn-oam-req-frmk-02.txt Dinesh Mohan (Nortel) mohand@nortel.com Ali Sajassi (Cisco) sajassi@cisco.com IETF-62, Minneapolis March 08, 2005

2. Overview • L2VPN OAM Framework • Propose OAM Layering in context of L2VPN WG technologies • L2VPN Service Layer, PW Layer, PSN Layer • Customer, Service Provider, Network Operators roles • Propose OAM Constructs • OAM Domains, MEPs and MIPs • L2VPN OAM Requirements • Identify requirements for L2VPN Service OAM • Identify requirements for underlying facilities OAM e.g. PWs/PSN OAM

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

4. Editorial Updates • Title of WG draft now reads: L2VPN OAM Requirements and Framework • VPWS and IPLS sections have been added • VPWS is marked as TBD • IPLS is marked as FFS • VPLS OAM Framework has been updated • VPLS as a service • VPLS as a network • VPLS as a LAN/VLAN emulation

5. Editorial Updates (cont’d) • VPLS OAM Requirements • Requirements on transport to be added, e.g. • VPLS as service expects underlying links as bidirectional • VPLS as service expects underlying emulation LAN to have no partial mesh failures • Requirements on VPLS OAM due to underlying network features e.g. ECMP • Requirements on VPLS OAM due to underlying network e.g. hold-off timers etc. • VPWS and IPLS OAM Requirements to be added • VPWS OAM Requirements will account for • draft-delord • draft-wilis • IPLS OAM Requirements are marked FFS • Interested parties should contact editors – SOON!!!!

6. What’s next?

7. Next Steps • Update Acknowledgements • Simon Delord/Philippe Nigel - France Telecom • Neil Harrison - British Telecom • Lior Shabtay/Dan Cauchy - Atrica • Add VPWS OAM Requirements – (service only, no PWE3) • Enhance VPLS OAM Requirements to identify dependency on underlying transport e.g. PW/PSN • Identify specific OAM Requirements on PW

8. Backup Slides

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

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

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

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