Signaling Root-Initiated Point-to-Multipoint Pseudowire Using LDP
RFC 8338

Document Type RFC - Proposed Standard (March 2018; No errata)
Updates RFC 7385
Last updated 2018-03-06
Replaces draft-ietf-pwe3-p2mp-pw
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Stewart Bryant
Shepherd write-up Show (last changed 2017-04-04)
IESG IESG state RFC 8338 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Stewart Bryant <stewart.bryant@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                   S. Boutros, Ed.
Request for Comments: 8338                                        VMware
Updates: 7385                                          S. Sivabalan, Ed.
Category: Standards Track                                  Cisco Systems
ISSN: 2070-1721                                               March 2018

   Signaling Root-Initiated Point-to-Multipoint Pseudowire Using LDP

Abstract

   This document specifies a mechanism to signal Point-to-Multipoint
   (P2MP) Pseudowire (PW) trees using LDP.  Such a mechanism is suitable
   for any Layer 2 VPN service requiring P2MP connectivity over an IP or
   MPLS-enabled PSN.  A P2MP PW established via the proposed mechanism
   is root initiated.  This document updates RFC 7385 by reassigning the
   reserved value 0xFF to be the wildcard transport tunnel type.

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

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.

Boutros & Sivabalan          Standards Track                    [Page 1]
RFC 8338             Root-Initiated P2MP Pseudowire           March 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
     2.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Signaling P2MP PW . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  PW Ingress-to-Egress Incompatibility Issues . . . . . . .   6
     3.2.  P2MP PW FEC . . . . . . . . . . . . . . . . . . . . . . .   6
       3.2.1.  P2MP PW Upstream FEC Element  . . . . . . . . . . . .   7
       3.2.2.  P2P PW Downstream FEC Element . . . . . . . . . . . .  11
     3.3.  Typed Wildcard FEC Format for a New FEC . . . . . . . . .  11
     3.4.  Group ID Usage  . . . . . . . . . . . . . . . . . . . . .  12
     3.5.  Generic Label TLV . . . . . . . . . . . . . . . . . . . .  12
   4.  LDP Capability Negotiation  . . . . . . . . . . . . . . . . .  12
   5.  P2MP PW Status  . . . . . . . . . . . . . . . . . . . . . . .  14
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     7.1.  FEC Type Name Space . . . . . . . . . . . . . . . . . . .  15
     7.2.  LDP TLV Type  . . . . . . . . . . . . . . . . . . . . . .  15
     7.3.  mLDP Opaque Value Element TLV Type  . . . . . . . . . . .  15
     7.4.  Selective Tree Interface Parameter Sub-TLV Type . . . . .  15
     7.5.  Wildcard PMSI Tunnel Type . . . . . . . . . . . . . . . .  15
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  17
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  18
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   A Point-to-Multipoint (P2MP) Pseudowire (PW) emulates the essential
   attributes of a unidirectional P2MP Telecommunications service such
   as P2MP ATM over PSN.  A major difference between a Point-to-Point
   (P2P) PW outlined in [RFC3985] and a P2MP PW is that the former is
   intended for bidirectional service whereas the latter is intended for
   both unidirectional and, optionally, bidirectional service.
   Requirements for P2MP PWs are described in [RFC7338].  P2MP PWs can
   be constructed as either Single Segment Pseudowires (P2MP SS-PWs) or
   Multi-Segment Pseudowires (P2MP MS-PWs) as mentioned in [RFC7338].
   P2MP MS-PW is outside the scope of this document.  A reference model
Show full document text