datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

MPLS Transport Profile Lock Instruct and Loopback Functions
RFC 6435

Internet Engineering Task Force (IETF)                   S. Boutros, Ed.
Request for Comments: 6435                             S. Sivabalan, Ed.
Updates: 6371                                        Cisco Systems, Inc.
Category: Standards Track                               R. Aggarwal, Ed.
ISSN: 2070-1721                                             Arktan, Inc.
                                                       M. Vigoureux, Ed.
                                                          Alcatel-Lucent
                                                             X. Dai, Ed.
                                                         ZTE Corporation
                                                           November 2011

      MPLS Transport Profile Lock Instruct and Loopback Functions

Abstract

   Two useful Operations, Administration, and Maintenance (OAM)
   functions in a transport network are "lock" and "loopback".  The lock
   function enables an operator to lock a transport path such that it
   does not carry client traffic, but can continue to carry OAM messages
   and may carry test traffic.  The loopback function allows an operator
   to set a specific node on the transport path into loopback mode such
   that it returns all received data.

   This document specifies the lock function for MPLS networks and
   describes how the loopback function operates in MPLS networks.

   This document updates Sections 7.1.1 and 7.1.2 of RFC 6371.

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

Boutros, et al.              Standards Track                    [Page 1]
RFC 6435           MPLS-TP Lock Instruct and Loopback      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.

1.  Introduction

   Two useful Operations, Administration, and Maintenance (OAM)
   functions in a transport network are "lock" and "loopback".  This
   document discusses these functions in the context of MPLS networks.

   -  The lock function enables an operator to lock a transport path
      such that it does not carry client traffic.  As per RFC 5860 [1],
      lock is an administrative state in which it is expected that no
      client traffic may be carried.  However, test traffic and OAM
      messages can still be mapped onto the locked transport path.  The
      lock function may be applied to the Label Switched Paths (LSPs),
      Pseudowires (PWs) (including multi-segment Pseudowires) (MS-PWs),
      and bidirectional MPLS Sections as defined in RFC 5960 [9]).

   -  The loopback function allows an operator to set a specific node on
      a transport path into loopback mode such that it returns all
      received data.  Loopback can be applied at a Maintenance Entity
      Group End Point (MEP) or a Maintenance Entity Group Intermediate
      Point (MIP) on a co-routed bidirectional LSP, on a PW, or on a
      bidirectional MPLS Section.  It can also be applied at a MEP on an
      associated bidirectional LSP.

      Loopback is used to test the integrity of the transport path to
      and from the node that is performing loopback.  It requires that
      the transport path be locked and that a MEP on the transport path
      send test data that it also validates on receipt.

   This document specifies the lock function for MPLS networks and
   describes how the loopback function operates in MPLS networks.

Boutros, et al.              Standards Track                    [Page 2]
RFC 6435           MPLS-TP Lock Instruct and Loopback      November 2011

1.1.  Updates RFC 6371

   This document updates Sections 7.1.1 and 7.1.2 of RFC 6371 [6].

[include full document text]