MPLS Fault Management Operations, Administration, and Maintenance (OAM)
RFC 6427
Document | Type |
RFC - Proposed Standard
(November 2011; No errata)
Updated by RFC 7214
|
|
---|---|---|---|
Authors | Martin Vigoureux , David Ward , George Swallow , Sami Boutros , Annamaria Fulignoli | ||
Last updated | 2015-10-14 | ||
Replaces | draft-sfv-mpls-tp-fault, draft-boutros-mpls-tp-fault | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6427 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Adrian Farrel | ||
IESG note | Ross Callon (rcallon@juniper.net) is the Document Shepherd. | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) G. Swallow, Ed. Request for Comments: 6427 Cisco Systems, Inc. Category: Standards Track A. Fulignoli, Ed. ISSN: 2070-1721 Ericsson M. Vigoureux, Ed. Alcatel-Lucent S. Boutros Cisco Systems, Inc. D. Ward Juniper Networks, Inc. November 2011 MPLS Fault Management Operations, Administration, and Maintenance (OAM) Abstract 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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6427. Swallow, et al. Standards Track [Page 1] RFC 6427 MPLS Fault Management OAM November 2011 Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................3 1.1. Terminology ................................................4 1.2. Requirements Language ......................................5 2. MPLS Fault Management Messages ..................................5 2.1. MPLS Alarm Indication Signal ...............................5 2.1.1. MPLS Link Down Indication ...........................6 2.2. MPLS Lock Report ...........................................6 2.3. Propagation of MPLS Fault Messages .........................7 3. MPLS Fault Management Channel ...................................7 4. MPLS Fault Management Message Format ............................8 4.1. Fault Management Message TLVs ..............................9 4.1.1. Interface Identifier TLV ...........................10 4.1.2. Global Identifier ..................................10 5. Sending and Receiving Fault Management Messages ................10 5.1. Sending a Fault Management Message ........................10 5.2. Clearing a Fault Management Indication ....................11 5.3. Receiving a Fault Management Indication ...................11 6. Minimum Implementation Requirements ............................12 7. Security Considerations ........................................12 8. IANA Considerations ............................................13 8.1. Pseudowire Associated Channel Type ........................13 8.2. MPLS Fault OAM Message Type Registry ......................13 8.3. MPLS Fault OAM Flag Registry ..............................14 8.4. MPLS Fault OAM TLV Registry ...............................14 9. References .....................................................15 9.1. Normative References ......................................15 9.2. Informative References ....................................15 10. Contributing Authors ..........................................16 Swallow, et al. Standards Track [Page 2] RFC 6427 MPLS Fault Management OAM November 2011Show full document text