Definition of P2MP PW TLV for Label Switched Path (LSP) Ping Mechanisms
RFC 8339

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05

Internet Engineering Task Force (IETF)                      P. Jain, Ed.
Request for Comments: 8339                           Cisco Systems, Inc.
Category: Standards Track                                     S. Boutros
ISSN: 2070-1721                                             VMWare, Inc.
                                                               S. Aldrin
                                                             Google Inc.
                                                              March 2018

Definition of P2MP PW TLV for Label Switched Path (LSP) Ping Mechanisms

Abstract

   Label Switched Path (LSP) Ping is a widely deployed Operation,
   Administration, and Maintenance (OAM) mechanism in MPLS networks.
   This document describes a mechanism to verify connectivity of Point-
   to-Multipoint (P2MP) Pseudowires (PWs) using LSP Ping.

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 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8339.

Copyright Notice

   Copyright (c) 2018 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
   (https://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.

Jain, et al.                 Standards Track                    [Page 1]
RFC 8339                P2MP PW TLV for LSP Ping              March 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Specification of Requirements . . . . . . . . . . . . . .   3
     2.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Identifying a P2MP PW . . . . . . . . . . . . . . . . . . . .   5
     3.1.  P2MP Pseudowire Sub-TLV . . . . . . . . . . . . . . . . .   5
   4.  Encapsulation of OAM Ping Packets . . . . . . . . . . . . . .   6
   5.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Controlling Echo Responses  . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

Jain, et al.                 Standards Track                    [Page 2]
RFC 8339                P2MP PW TLV for LSP Ping              March 2018

1.  Introduction

   A Point-to-Multipoint (P2MP) Pseudowire (PW) emulates the essential
   attributes of a unidirectional P2MP Telecommunications service such
   as P2MP ATM over a Public Switched Network (PSN).  Requirements for
   P2MP PWs are described in [RFC7338].  P2MP PWs are carried over a
   P2MP MPLS LSP.  The procedures for P2MP PW signaling using BGP are
   described in [RFC7117]; LDP for single segment P2MP PWs is described
   in [RFC8338].  Many P2MP PWs can share the same P2MP MPLS LSP; this
   arrangement is called an "Aggregate P2MP Tree".  An Aggregate P2MP
   Tree requires an upstream-assigned label so that on the Leaf PE
   (L-PE), the traffic can be associated with a Virtual Private Network
   (VPN) or a Virtual Private LAN Service (VPLS) instance.  When a P2MP
   MPLS LSP carries only one VPN or VPLS service instance, the
   arrangement is called an "Inclusive P2MP Tree".  For an Inclusive
   P2MP Tree, the P2MP MPLS LSP label itself can uniquely identify the
   VPN or VPLS service being carried over the P2MP MPLS LSP.  The P2MP
   MPLS LSP can also be used in the Selective P2MP Tree arrangement to
   carry multicast traffic.  In a Selective P2MP Tree arrangement,
   traffic to each multicast group in a VPN or VPLS instance is carried
   by a separate unique P2MP LSP.  In an Aggregate Selective P2MP Tree