Resilient MPLS Rings and Multicast
draft-zzhang-mpls-rmr-multicast-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MPLS                                                            Z. Zhang
Internet-Draft                                          Juniper Networks
Intended status: Informational                                  S. Esale
Expires: January 3, 2019                          Juniper Networks, Inc.
                                                            July 2, 2018

                   Resilient MPLS Rings and Multicast
                   draft-zzhang-mpls-rmr-multicast-00

Abstract

   This document discusses multicast with resilient mpls rings.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC2119.

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 January 3, 2019.

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
   (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

Zhang & Esale            Expires January 3, 2019                [Page 1]
Internet-Draft                  bgp-mcast                      July 2018

   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
   2.  P2MP/MP2MP Tunnels on a Ring  . . . . . . . . . . . . . . . . . 3
     2.1.  Tunnel Protoction and FRR . . . . . . . . . . . . . . . . . 4
   3.  End to End Tunnels with Rings . . . . . . . . . . . . . . . . . 5
   4.  End to End Multicast with Rings . . . . . . . . . . . . . . . . 5
     4.1.  End-to-end Native (x,g) Signaling/Forwarding in the
           Global Table  . . . . . . . . . . . . . . . . . . . . . . . 5
     4.2.  mLDP Inband Signaling in the Global Table or VRFs . . . . . 6
     4.3.  MVPN/GTM/EVPN/VPLS  . . . . . . . . . . . . . . . . . . . . 6
       4.3.1.  MVPN/GTM/EVPN/VPLS Tunnel Segmentation  . . . . . . . . 6
   5.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 7

Zhang & Esale            Expires January 3, 2019                [Page 2]
Internet-Draft                  bgp-mcast                      July 2018

1.  Introduction

   [I-D.ietf-mpls-rmr] describes ...

   This document discusses how multicast works with RMRs.

   All existing multicast procedures and solutions can work as is.  This
   include both mpls multicast tunnels and end-to-end multicast that
   makes use of multicast tunnels.  Ring topology is just a special case
   of general topologies so all existing RSVP-TE P2MP and mLDP tunnel
   can be set up the same way.  An Ingress Replication (IR) tunnel
   consists a bunch of p2p LSPs, and it does not matter whether a
   component LSP is a plain old LSP or a Ring LSP.

   On the other hand, there are optimizations that could be done for
   RSVP-TE P2MP tunnel signaling (and perhaps FRR for both mLDP and
   RSVP-TE P2MP tunnels).  This document describes that in high level
   (detailed protocol procedure will be specified in a separate draft),
   and also discusses end to end multicast when there are RMRs (even
   though the two are independent).

2.  P2MP/MP2MP Tunnels on a Ring

   Because mLDP label mapping messages are merged as they propagate from
   the leaves towards the root, ring topology does not lead to any
   further optimization.

   For a conventionally signaled RSVP-TE P2MP tunnel, the ingress
   discovers the leaves and signals one sub-LSP for each leaf.  Even
Show full document text