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

Document Type Active Internet-Draft (individual)
Last updated 2019-01-14
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: July 18, 2019                            Juniper Networks, Inc.
                                                        January 14, 2019

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

Abstract

   With Resilient MPLS Rings (RMR), although all existing multicast
   procedures and solutions can work as is, there are optimizations that
   could be done for RSVP-TE P2MP tunnel signaling and Fast-ReRouting
   for both mLDP and RSVP-TE P2MP tunnels.  This document describes that
   in high level (detailed protocol procedure is specified in
   [I-D.zzhang-teas-rmr-rsvp-p2mp]), and also discusses end to end
   multicast when there are RMRs.

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 https://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 July 18, 2019.

Copyright Notice

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

Zhang & Esale             Expires July 18, 2019                 [Page 1]
Internet-Draft                  rmr-mcast                   January 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  P2MP/MP2MP Tunnels on a Ring  . . . . . . . . . . . . . . . .   3
     2.1.  Tunnel Protection and FRR . . . . . . . . . . . . . . . .   3
   3.  End to End Tunnels with Rings . . . . . . . . . . . . . . . .   4
   4.  End to End Native Multicast with Rings  . . . . . . . . . . .   5
     4.1.  Native Multicast in the Global Routing Table  . . . . . .   5
     4.2.  mLDP Inband Signaling . . . . . . . . . . . . . . . . . .   5
     4.3.  Overlay Multicast Services  . . . . . . . . . . . . . . .   5
       4.3.1.  Tunnel Segmentation . . . . . . . . . . . . . . . . .   5
   5.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   This document discusses how multicast works with Resilient MPLS Rings
   [I-D.ietf-mpls-rmr].  It is expected that readers are familiar with
   the concept and terms in [I-D.ietf-mpls-rmr].

   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 [RFC4875] and mLDP
   [RFC6388] tunnels can be set up using existing protocols and
   procedures.  An Ingress Replication (IR) tunnel [RFC7988] 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 Fast-ReRouting (FRR) for both mLDP
   and RSVP-TE P2MP tunnels.  This document describes that on a 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 RMR could be transparent to multicast.

Zhang & Esale             Expires July 18, 2019                 [Page 2]
Internet-Draft                  rmr-mcast                   January 2019
Show full document text