MPLS On-Demand Connectivity Verification and Route Tracing
RFC 6426

Internet Engineering Task Force (IETF)                           E. Gray
Request for Comments: 6426                                      Ericsson
Updates: 4379                                                 N. Bahadur
Category: Standards Track                         Juniper Networks, Inc.
ISSN: 2070-1721                                               S. Boutros
                                                     Cisco Systems, Inc.
                                                             R. Aggarwal
                                                           November 2011

       MPLS On-Demand Connectivity Verification and Route Tracing

Abstract

   Label Switched Path Ping (LSP ping) is an existing and widely
   deployed Operations, Administration, and Maintenance (OAM) mechanism
   for Multi-Protocol Label Switching (MPLS) Label Switched Paths
   (LSPs).  This document describes extensions to LSP ping so that LSP
   ping can be used for on-demand connectivity verification of MPLS
   Transport Profile (MPLS-TP) LSPs and pseudowires.  This document also
   clarifies procedures to be used for processing the related OAM
   packets.  Further, it describes procedures for using LSP ping to
   perform connectivity verification and route tracing functions in
   MPLS-TP networks.  Finally, this document updates RFC 4379 by adding
   a new address type and creating an IANA registry.

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

Gray, et al.                 Standards Track                    [Page 1]
RFC 6426        MPLS On-Demand Connectivity Verification   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.  Conventions Used in This Document  . . . . . . . . . . . .  3
     1.2.  On-Demand CV for MPLS-TP LSPs Using IP Encapsulation . . .  4
     1.3.  On-Demand CV for MPLS-TP LSPs Using Non-IP
           Encapsulation  . . . . . . . . . . . . . . . . . . . . . .  4
   2.  LSP Ping Extensions  . . . . . . . . . . . . . . . . . . . . .  5
     2.1.  New Address Type for Downstream Mapping TLV  . . . . . . .  5
       2.1.1.  DSMAP/DDMAP Non-IP Address Information . . . . . . . .  5
     2.2.  Source/Destination Identifier TLV  . . . . . . . . . . . .  7
       2.2.1.  Source/Destination Identifier TLV Format . . . . . . .  7
       2.2.2.  Source Identifier TLV  . . . . . . . . . . . . . . . .  7
       2.2.3.  Destination Identifier TLV . . . . . . . . . . . . . .  8
     2.3.  Identifying Statically Provisioned LSPs and PWs  . . . . .  8
       2.3.1.  Static LSP Sub-TLV . . . . . . . . . . . . . . . . . .  9
       2.3.2.  Static Pseudowire Sub-TLV  . . . . . . . . . . . . . . 10
   3.  Performing On-Demand CV over MPLS-TP LSPs  . . . . . . . . . . 10
     3.1.  LSP Ping with IP Encapsulation . . . . . . . . . . . . . . 11
     3.2.  On-Demand CV with IP Encapsulation, over ACH . . . . . . . 11
     3.3.  Non-IP-Based On-Demand CV, Using ACH . . . . . . . . . . . 12
     3.4.  Reverse-Path Connectivity Verification . . . . . . . . . . 13
       3.4.1.  Requesting Reverse-Path Connectivity Verification  . . 13
       3.4.2.  Responder Procedures . . . . . . . . . . . . . . . . . 13
       3.4.3.  Requester Procedures . . . . . . . . . . . . . . . . . 14
     3.5.  P2MP Considerations  . . . . . . . . . . . . . . . . . . . 14
     3.6.  Management Considerations for Operation with Static
           MPLS-TP  . . . . . . . . . . . . . . . . . . . . . . . . . 14
     3.7.  Generic Associated Channel Label (GAL) Processing  . . . . 14
   4.  Performing On-Demand Route Tracing over MPLS-TP LSPs . . . . . 15