L2VPN OAM Requirements

1
L2VPN OAM Requirements Frameworkdraft-ietf-l2v
pn-oam-req-frmk-05.txt

• Dinesh Mohan (Nortel)
• mohand_at_nortel.com
• Ali Sajassi (Cisco)
• sajassi_at_cisco.com
• IETF-65, Dallas
• March 23, 2006

2
Draft-05 Updates

• Updated VPLS requirements based on feedback
• Added VPWS requirements based on draft-delord as
  agreed in the last meeting
• Establish the relationship with L2VPN framework
  document
• Identified location of MEPs MIPs wrt L2VPN
  framework modules

3
Next Step

• As agreed in the last meeting all comments
  received by the editors have been addressed
• We would like to proceed with the last call
• So that we can focus our efforts our the right
  solution set

4
History

• IETF-64 (Vancouver)
• Section 3.2 (OAM Domains) updated - Hierarchical
  and Adjacent OAM domains distinction added
• Section 5 (OAM Framework for VPWS) added
• Based on VPWS framework in draft-delord-pwe3-oam-a
  pplications-01.txt
• Section 9 (OAM Operational Scenarios) added
• Indicate what kind of solutions can be used for
  different OAM layers without being prescriptive
• IETF-63 (Paris)
• draft-ietf-l2vpn-oam-req-frmk-03.txt updated
  submitted
• Agreement to include VPWS framework and
  requirements from draft-delord
• Discussion to reflect how the framework can
  accommodate interim solutions
• IETF-62 (Minneapolis)
• 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.
  PWsand/or LSPs
• IETF-60 (San Diego)
• Draft-ietf-l2vpn-oam-req-frmk-00.txt submitted

5
Overview
6
Alternate Next Step ?

• If splitting required, then editors will submit a
  Requirement and Framework drafts based on current
  draft (ver. 05)
• Both will be WG documents and will be taken to
  the last call