Document Action: 'L2VPN OAM Requirements and Framework' to Informational RFC (draft-ietf-l2vpn-oam-req-frmk-11.txt)
The IESG <iesg-secretary@ietf.org> Mon, 22 November 2010 21:26 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 256193A6AFF; Mon, 22 Nov 2010 13:26:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R7xPRX2huvcI; Mon, 22 Nov 2010 13:26:03 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0135828C180; Mon, 22 Nov 2010 13:25:59 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'L2VPN OAM Requirements and Framework' to Informational RFC (draft-ietf-l2vpn-oam-req-frmk-11.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.09
Message-ID: <20101122212558.12847.45112.idtracker@localhost>
Date: Mon, 22 Nov 2010 13:25:58 -0800
Cc: l2vpn mailing list <l2vpn@ietf.org>, l2vpn chair <l2vpn-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Nov 2010 21:26:06 -0000
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