Definition of P2MP PW TLV for LSP-Ping Mechanisms
draft-ietf-pals-p2mp-pw-lsp-ping-05

Document Type Active Internet-Draft (pals WG)
Last updated 2017-08-29 (latest revision 2017-08-21)
Replaces draft-jain-pals-p2mp-pw-lsp-ping
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Andrew Malis
Shepherd write-up Show (last changed 2017-05-01)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Andrew Malis <agmalis@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state MISSREF
PALS Workgroup                                              P. Jain, Ed.
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                              S. Boutros
Expires: February 22, 2018                                  VMWare, Inc.
                                                               S. Aldrin
                                                             Google Inc.
                                                         August 21, 2017

           Definition of P2MP PW TLV for LSP-Ping Mechanisms
                  draft-ietf-pals-p2mp-pw-lsp-ping-05

Abstract

   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 (PW) using LSP Ping.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 22, 2018.

Copyright Notice

   Copyright (c) 2017 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

Jain, et al.            Expires February 22, 2018               [Page 1]
Internet-Draft              P2MP PW LSP Ping                 August 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

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

1.  Introduction

   A Point-to-Multipoint (P2MP) Pseudowire (PW) emulates the essential
   attributes of a unidirectional P2MP Telecommunications service such
   as P2MP ATM over Public Switched Network (PSN).  Requirements for
   P2MP PW are described in [RFC7338].  P2MP PWs are carried over P2MP
   MPLS LSP.  The Procedures for P2MP PW signaling using BGP are
   described in [RFC7117] and LDP for single segment P2MP PWs are
   described in [I-D.ietf-pals-p2mp-pw].  Many P2MP PWs can share the
   same P2MP MPLS LSP and this arrangement is called 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 Inclusive P2MP Tree.  For
   Inclusive P2MP Tree, P2MP MPLS LSP label itself can uniquely identify
   the VPN or VPLS service being carried over P2MP MPLS LSP.  The P2MP
   MPLS LSP can also be used in Selective P2MP Tree arrangement for
   carrying multicast traffic.  In a Selective P2MP Tree arrangement,
   traffic to each multicast group in a VPN or VPLS instance is carried
Show full document text