Multicast Virtual Private Network (MVPN): Using Bidirectional P-Tunnels
RFC 7582

Document Type RFC - Proposed Standard (July 2015; No errata)
Last updated 2015-10-14
Replaces draft-ietf-l3vpn-mvpn-bidir
Stream IETF
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Thomas Morin
Shepherd write-up Show (last changed 2015-02-18)
IESG IESG state RFC 7582 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to (None)
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                          E. Rosen
Request for Comments: 7582                        Juniper Networks, Inc.
Updates: 6513, 6514, 6625                                   IJ. Wijnands
Category: Standards Track                            Cisco Systems, Inc.
ISSN: 2070-1721                                                   Y. Cai
                                                               Microsoft
                                                                A. Boers
                                                               July 2015

               Multicast Virtual Private Network (MVPN):
                     Using Bidirectional P-Tunnels

Abstract

   A set of prior RFCs specify procedures for supporting multicast in
   BGP/MPLS IP VPNs.  These procedures allow customer multicast data to
   travel across a service provider's backbone network through a set of
   multicast tunnels.  The tunnels are advertised in certain BGP
   multicast auto-discovery routes, by means of a BGP attribute known
   as the "Provider Multicast Service Interface (PMSI) Tunnel"
   attribute.  Encodings have been defined that allow the PMSI Tunnel
   attribute to identify bidirectional (multipoint-to-multipoint)
   multicast distribution trees.  However, the prior RFCs do not provide
   all the necessary procedures for using bidirectional tunnels to
   support multicast VPNs.  This document updates RFCs 6513, 6514, and
   6625 by specifying those procedures.  In particular, it specifies the
   procedures for assigning customer multicast flows (unidirectional or
   bidirectional) to specific bidirectional tunnels in the provider
   backbone, for advertising such assignments, and for determining which
   flows have been assigned to which tunnels.

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

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

Rosen, et al.                Standards Track                    [Page 1]
RFC 7582           MVPN: Using Bidirectional P-Tunnels         July 2015

Copyright Notice

   Copyright (c) 2015 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Rosen, et al.                Standards Track                    [Page 2]
RFC 7582           MVPN: Using Bidirectional P-Tunnels         July 2015

Table of Contents

   1. Introduction ....................................................4
      1.1. Terminology ................................................4
      1.2. Overview ...................................................9
           1.2.1. Bidirectional P-Tunnel Technologies ................10
           1.2.2. Reasons for Using Bidirectional P-Tunnels ..........11
           1.2.3. Knowledge of Group-to-RP and/or
                  Group-to-RPA Mappings ..............................12
           1.2.4. PMSI Instantiation Methods .........................12
   2. The All BIDIR-PIM Wildcard .....................................15
   3. Using Bidirectional P-Tunnels ..................................15
      3.1. Procedures Specific to the Tunneling Technology ...........15
           3.1.1. BIDIR-PIM P-Tunnels ................................16
           3.1.2. MP2MP LSPs .........................................17
      3.2. Procedures Specific to the PMSI Instantiation Method ......17
           3.2.1. Flat Partitioning ..................................17
                  3.2.1.1. When an S-PMSI Is a 'Match for
                           Transmission' .............................19
                  3.2.1.2. When an I-PMSI Is a 'Match for
                           Transmission' .............................20
                  3.2.1.3. When an S-PMSI Is a 'Match for Reception' .21
Show full document text