RFC 6136 on Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM) Requirements and Framework

rfc-editor@rfc-editor.org Sat, 12 March 2011 02:11 UTC

Return-Path: <wwwrun@rfc-editor.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 C48CF3A6C9F; Fri, 11 Mar 2011 18:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.415
X-Spam-Level:
X-Spam-Status: No, score=-102.415 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 Cj0IQYQVmogQ; Fri, 11 Mar 2011 18:11:19 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 355F23A6C99; Fri, 11 Mar 2011 18:11:14 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4836AE0759; Fri, 11 Mar 2011 18:12:34 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6136 on Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM) Requirements and Framework
From: rfc-editor@rfc-editor.org
Message-Id: <20110312021234.4836AE0759@rfc-editor.org>
Date: Fri, 11 Mar 2011 18:12:34 -0800
Cc: l2vpn@ietf.org, 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: Sat, 12 Mar 2011 02:11:25 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6136

        Title:      Layer 2 Virtual Private Network 
                    (L2VPN) Operations, Administration, and Maintenance 
                    (OAM) Requirements and Framework 
        Author:     A. Sajassi, Ed.,
                    D. Mohan, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       March 2011
        Mailbox:    sajassi@cisco.com, 
                    mohand@nortel.com
        Pages:      42
        Characters: 92170
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l2vpn-oam-req-frmk-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6136.txt

This document provides framework and requirements for Layer 2 Virtual
Private Network (L2VPN) Operations, Administration, and Maintenance
(OAM).  The OAM framework is intended to provide OAM layering across
L2VPN services, pseudowires (PWs), and Packet Switched Network (PSN)
tunnels.  This document is intended to identify OAM requirements
for L2VPN services, i.e., Virtual Private LAN Service (VPLS), Virtual 
Private Wire Service (VPWS), and IP-only LAN Service (IPLS). Furthermore, 
if L2VPN service OAM requirements impose specific requirements on PW
OAM and/or PSN OAM, those specific PW and/or PSN OAM requirements
are also identified.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC