datatracker.ietf.org
Sign in
Version 5.3.1, 2014-04-16
Report a bug

Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile
RFC 6428

Internet Engineering Task Force (IETF)                     D. Allan, Ed.
Request for Comments: 6428                                      Ericsson
Category: Standards Track                                G. Swallow, Ed.
ISSN: 2070-1721                                      Cisco Systems, Inc.
                                                           J. Drake, Ed.
                                                                 Juniper
                                                           November 2011

       Proactive Connectivity Verification, Continuity Check, and
        Remote Defect Indication for the MPLS Transport Profile

Abstract

   Continuity Check, Proactive Connectivity Verification, and Remote
   Defect Indication functionalities are required for MPLS Transport
   Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM).

   Continuity Check monitors a Label Switched Path for any loss of
   continuity defect.  Connectivity Verification augments Continuity
   Check in order to provide confirmation that the desired source is
   connected to the desired sink.  Remote Defect Indication enables an
   end point to report, to its associated end point, a fault or defect
   condition that it detects on a pseudowire, Label Switched Path, or
   Section.

   This document specifies specific extensions to Bidirectional
   Forwarding Detection (BFD) and methods for proactive Continuity
   Check, Continuity Verification, and Remote Defect Indication for
   MPLS-TP pseudowires, Label Switched Paths, and Sections using BFD as
   extended by this memo.

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/rfc6428.

Allan, et al.                Standards Track                    [Page 1]
RFC 6428               CC, CV, and RDI for MPLS-TP         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
   2. Conventions Used in This Document ...............................3
      2.1. Terminology ................................................3
      2.2. Requirements Language ......................................5
   3. MPLS-TP CC, Proactive CV, and RDI Mechanism Using BFD ...........5
      3.1. Existing Capabilities ......................................5
      3.2. CC, CV, and RDI Overview ...................................5
      3.3. ACH Code Points for CC and Proactive CV ....................6
      3.4. MPLS-TP BFD CC Message Format ..............................7
      3.5. MPLS-TP BFD Proactive CV Message Format ....................8
           3.5.1. Section MEP-ID ......................................9
           3.5.2. LSP MEP-ID ..........................................9
           3.5.3. PW End Point MEP-ID ................................10
      3.6. BFD Session in MPLS-TP Terminology ........................10
      3.7. BFD Profile for MPLS-TP ...................................11
           3.7.1. Session Initiation and Modification ................12
           3.7.2. Defect Entry Criteria ..............................13
           3.7.3. Defect Entry Consequent Action .....................14
           3.7.4. Defect Exit Criteria ...............................14
           3.7.5. State Machines .....................................15
           3.7.6. Configuration of MPLS-TP BFD Sessions ..............17
           3.7.7. Discriminator Values ...............................17
   4. Configuration Considerations ...................................18
   5. IANA Considerations ............................................18
   6. Security Considerations ........................................19

[include full document text]