IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane and Selective Provider Multicast Service Interface (S-PMSI) Join Messages
RFC 6516

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 02

Internet Engineering Task Force (IETF)                            Y. Cai
Request for Comments: 6516                                 E. Rosen, Ed.
Category: Standards Track                                   IJ. Wijnands
ISSN: 2070-1721                                            Cisco Systems
                                                           February 2012

       IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane
      and Selective Provider Multicast Service Interface (S-PMSI)
                             Join Messages

Abstract

   The specification for Multicast Virtual Private Networks (MVPNs)
   contains an option that allows the use of PIM as the control protocol
   between provider edge routers.  It also contains an option that
   allows UDP-based messages, known as Selective Provider Multicast
   Service Interface (S-PMSI) Join messages, to be used to bind
   particular customer multicast flows to particular tunnels through a
   service provider's network.  This document extends the MVPN
   specification (RFC 6513) so that these options can be used when the
   customer multicast flows are IPv6 flows.

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

Copyright Notice

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

Cai, et al.                  Standards Track                    [Page 1]
RFC 6516                    IPv6 MVPN Support              February 2012

   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.

Table of Contents

   1. Introduction ....................................................2
   2. Specification of Requirements ...................................3
   3. S-PMSI Joins Binding IPv6 Flows to GRE/IPv4 P-Tunnels ...........3
      3.1. Encoding ...................................................3
      3.2. Encapsulation of S-PMSI Joins in UDP Datagrams .............4
   4. PE-PE PIM/IPv6 over an IPv4 P-Tunnel ............................4
   5. IANA Considerations .............................................5
   6. Security Considerations .........................................5
   7. Acknowledgments .................................................5
   8. Normative References ............................................5

1.  Introduction

   The Multicast Virtual Private Network (MVPN) specification [RFC6513]
   defines the notion of a "PMSI" (Provider Multicast Service Interface)
   and specifies how a PMSI can be instantiated by various kinds of
   tunnels through a service provider's network ("P-tunnels").  It also
   specifies the procedures for using PIM (Protocol Independent
   Multicast [RFC4601]) as the control protocol between Provider Edge
   (PE) routers.  When PIM is used as the control protocol, PIM messages
   are sent through a P-tunnel from one PE in an MVPN to others in the
   same MVPN.  These PIM messages carry customer multicast routing
   information.  However, [RFC6513] does not cover the case where the
   customer is using IPv6, but the service provider is using P-tunnels
   created by PIM over an IPv4 infrastructure.

   The MVPN specification [RFC6513] also specifies "S-PMSI (Selective
   PMSI) Join" messages, which are optionally used to bind particular
   customer multicast flows to particular P-tunnels.  However, the
   specification does not cover the case where the customer flows are
   IPv6 flows.

   This document extends [RFC6513] by adding the specification for
   handling customer IPv6 multicast flows when a service provider is
   using PE-PE PIM and/or S-PMSI Join messages over an IPv4
   infrastructure.  This document also specifies how to send multiple
   S-PMSI Join messages in a single UDP datagram.

   This document uses terminology defined in [RFC6513]: C-source,
   C-group, C-flow, P-group, and (C-S,C-G).

Cai, et al.                  Standards Track                    [Page 2]
RFC 6516                    IPv6 MVPN Support              February 2012