Subject: Document Action: 'L2VPN OAM Requirements and Framework' to Informational RFC (draft-ietf-l2vpn-oam-req-frmk-11.txt)

From: The IESG <[email-masked]>
Date: Mon, 22 Nov 2010 13:25:58 -0800

The IESG has approved the following document:
- 'L2VPN OAM Requirements and Framework'
  (draft-ietf-l2vpn-oam-req-frmk-11.txt) as an Informational RFC

This document is the product of the Layer 2 Virtual Private Networks
Working Group.

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-l2vpn-oam-req-frmk/

Technical Summary 
This draft provides framework and requirements for Layer 2 Virtual 
Private Networks (L2VPN) Operation, Administration and Maintenance 
(OAM). The OAM framework is intended to provide OAM layering across 
L2VPN services, Pseudo Wires (PWs) and Packet Switched Network (PSN) 
tunnels. The requirements are intended to identify OAM requirement 
for L2VPN services (i.e. VPLS, VPWS, and IPLS). Furthermore, if 
L2VPN services OAM requirements impose specific requirements on PW 
OAM and/or PSN OAM, those specific PW and/or PSN OAM requirements 
are also identified. 

Working Group Summary 
This document has been reviewed by carriers and experts in the L2VPN WG
and there are no outstanding issues. 

Document Quality 
This document was reviewed by Mark Townsley and the L2VPN Chairs. The
document Shepherd is Shane Amante.

Note to RFC Editor
 
In Section 11. Security Considerations

OLD
 This document takes into account the security considerations and 
   imposes requirements on solutions to prevent OAM messages from 
   leaking outside an OAM domain and for OAM domains to be transparent 
   to OAM frames from higher OAM domains, as specified in Section 6.10 
   and 7.10.  
NEW
  This specification assumes that L2VPN components within the OAM domain are mutually trusted.  Based on that
  assumption, confidentiality issues are fully addressed by filtering to prevent OAM frames from leaking outside their
  OAM domain. Similarly, authentication issues are addressed by preventing OAM frames generated outside from 
  entering the OAM domain.  Requirements to prevent OAM messages from leaking outside an OAM domain and for 
  OAM domains to be transparent to OAM frames from higher OAM domains are specified in Section 6.10 and 7.10.  
END