[mpls] RFC 6427 on MPLS Fault Management Operations, Administration, and Maintenance (OAM)

rfc-editor@rfc-editor.org Thu, 17 November 2011 07:18 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60F3221F96C9; Wed, 16 Nov 2011 23:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.212
X-Spam-Level:
X-Spam-Status: No, score=-102.212 tagged_above=-999 required=5 tests=[AWL=-0.212, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bIfpV5uhnUuy; Wed, 16 Nov 2011 23:18:15 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 021E821F96C8; Wed, 16 Nov 2011 23:18:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9FA84B1E002; Wed, 16 Nov 2011 23:12:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20111117071258.9FA84B1E002@rfc-editor.org>
Date: Wed, 16 Nov 2011 23:12:58 -0800
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 6427 on MPLS Fault Management Operations, Administration, and Maintenance (OAM)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 07:18:15 -0000

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

        
        RFC 6427

        Title:      MPLS Fault Management Operations, Administration, 
                    and Maintenance (OAM) 
        Author:     G. Swallow, Ed.,
                    A. Fulignoli, Ed.,
                    M. Vigoureux, Ed.,
                    S. Boutros, 
                    D. Ward
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2011
        Mailbox:    swallow@cisco.com, 
                    annamaria.fulignoli@ericsson.com, 
                    martin.vigoureux@alcatel-lucent.com,  
                    sboutros@cisco.com, 
                    dward@juniper.net
        Pages:      17
        Characters: 34069
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-tp-fault-07.txt

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

This document specifies Operations, Administration, and Maintenance (OAM)
messages to indicate service disruptive conditions for MPLS-based
transport network Label Switched Paths.  The notification mechanism
employs a generic method for a service disruptive condition to be
communicated to a Maintenance Entity Group End Point.  This document
defines an MPLS OAM channel, along with messages to communicate
various types of service disruptive conditions.  [STANDARDS-TRACK]

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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