6516
PROPOSED STANDARD
IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane and Selective Provider Multicast Service Interface (S-PMSI) Join Messages
Authors: Y. Cai, E. Rosen, I. Wijnands
Date: February 2012
Area: rtg
Working Group: l3vpn
Stream: IETF
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. [STANDARDS-TRACK]
RFC 6516
PROPOSED STANDARD
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
<span class="h1">IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane</span>
<span class="h1">and Selective Provider Multicast Service Interface (S-PMSI)</span>
<span class="h1">Join Messages</span>
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 (<a href="./rfc6513">RFC 6513</a>) 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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6516">http://www.rfc-editor.org/info/rfc6516</a>.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
<span class="grey">Cai, et al. Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6516">RFC 6516</a> IPv6 MVPN Support February 2012</span>
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
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Specification of Requirements ...................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. S-PMSI Joins Binding IPv6 Flows to GRE/IPv4 P-Tunnels ...........<a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. Encoding ...................................................<a href="#page-3">3</a>
<a href="#section-3.2">3.2</a>. Encapsulation of S-PMSI Joins in UDP Datagrams .............<a href="#page-4">4</a>
<a href="#section-4">4</a>. PE-PE PIM/IPv6 over an IPv4 P-Tunnel ............................<a href="#page-4">4</a>
<a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-5">5</a>
<a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-5">5</a>
<a href="#section-7">7</a>. Acknowledgments .................................................<a href="#page-5">5</a>
<a href="#section-8">8</a>. Normative References ............................................<a href="#page-5">5</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Multicast Virtual Private Network (MVPN) specification [<a href="./rfc6513" title=""Multicast in MPLS/BGP IP VPNs"">RFC6513</a>]
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 [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]) 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, [<a href="./rfc6513" title=""Multicast in MPLS/BGP IP VPNs"">RFC6513</a>] 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 [<a href="./rfc6513" title=""Multicast in MPLS/BGP IP VPNs"">RFC6513</a>] 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 [<a href="./rfc6513" title=""Multicast in MPLS/BGP IP VPNs"">RFC6513</a>] 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 [<a href="./rfc6513" title=""Multicast in MPLS/BGP IP VPNs"">RFC6513</a>]: C-source,
C-group, C-flow, P-group, and (C-S,C-G).
<span class="grey">Cai, et al. Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6516">RFC 6516</a> IPv6 MVPN Support February 2012</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Specification of Requirements</span>
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 [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. S-PMSI Joins Binding IPv6 Flows to GRE/IPv4 P-Tunnels</span>
The S-PMSI Join message is defined in <a href="./rfc6513#section-7.4.2.2">Section 7.4.2.2 of [RFC6513]</a>.
These messages contain a type field, and [<a href="./rfc6513" title=""Multicast in MPLS/BGP IP VPNs"">RFC6513</a>] defines only Type
1 S-PMSI Joins. A Type 1 S-PMSI Join may be used to assign a
customer IPv4 (C-S,C-G) flow to a P-tunnel that is created by
PIM/IPv4. To transmit data or control packets over such a P-tunnel,
the packets are encapsulated in GRE (Generic Routing Encapsulation)
within IPv4, as specified in <a href="./rfc6513#section-12">Section 12 of [RFC6513]</a>.
In this document, we define the Type 4 S-PMSI Join. A Type 4 S-PMSI
Join may be used to assign a customer IPv6 (C-S,C-G) flow to a
P-tunnel that is created by PIM/IPv4. GRE/IPv4 encapsulation is used
to send data or control packets on the P-tunnel.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Encoding</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| C-source |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| C-group |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| P-group |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (8 bits): 4
Length (16 bits): 40, the length in octets of the entire S-PMSI Join
message, including the Type, Length, Reserved, C-source, C-group, and
P-group fields.
<span class="grey">Cai, et al. Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6516">RFC 6516</a> IPv6 MVPN Support February 2012</span>
Reserved (8 bits): this field SHOULD be zero when transmitted and
MUST be ignored when received.
C-source (128 bits): the IPv6 address of the traffic source in the
VPN.
C-group (128 bits): the IPv6 group address of the multicast traffic.
P-group (32 bits): the IPv4 group address identifying the P-tunnel.
Data packets sent on this tunnel are encapsulated in IPv4 GRE packets
with this group address in the IP destination address field of the
outer header.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Encapsulation of S-PMSI Joins in UDP Datagrams</span>
All S-PMSI Joins are encapsulated in UDP datagrams [<a href="./rfc768" title=""User Datagram Protocol"">RFC768</a>]. A Type
4 S-PMSI Join MUST be encapsulated in an IPv6 UDP datagram. The IPv6
source address field of these datagrams SHOULD be the IPv4-mapped
IPv6 address [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] corresponding to the IPv4 address that the
originating PE router uses as its source address in the instance of
PIM that is used to create the specified P-tunnel.
A single UDP datagram MAY carry multiple S-PMSI Join messages, as
many as can fit entirely within it. If there are multiple S-PMSI
Joins in a UDP datagram, they MUST be of the same S-PMSI Join type.
The end of the last S-PMSI Join (as determined by the S-PMSI Join
length field) MUST coincide with the end of the UDP datagram, as
determined by the UDP length field. When processing a received UDP
datagram that contains one or more S-PMSI Joins, a router MUST
process all the S-PMSI Joins that fit into the datagram.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. PE-PE PIM/IPv6 over an IPv4 P-Tunnel</span>
If a VPN customer is using PIM over IPv6, but the SP (service
provider) is using an IPv4 infrastructure (i.e., is using an
IPv4-based control protocol to construct its P-tunnels), then the PE
routers will need to originate IPv6 PIM control messages. The IPv6
Source Address field of any such IPv6 PIM control message SHOULD be
the IPv4-mapped IPv6 address [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] corresponding to the IPv4
address that the originating PE router uses as its source address in
the instance of PIM that is used to create the specified P-tunnel.
If the IPv6 Destination Address field is the multicast address ALL-
PIM-ROUTERS, the IPv6 form of the address (ff02::d) is used. These
IPv6 PIM control messages are, of course, not transmitted natively
over the service provider's network but rather are encapsulated in
GRE/IPv4.
<span class="grey">Cai, et al. Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc6516">RFC 6516</a> IPv6 MVPN Support February 2012</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
[<a id="ref-RFC6513">RFC6513</a>] created an IANA registry for the "S-PMSI Join Message Type
Field". This document registers a new value in that registry:
Value: 4
Description: GRE S-PMSI for IPv6 traffic (unaggregated)
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
There are no additional security considerations beyond those of
[<a href="./rfc6513" title=""Multicast in MPLS/BGP IP VPNs"">RFC6513</a>].
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span>
The authors wish to thank DP Ayyadevara, Arjen Boers, Rayen Mohanty,
Rajesh Sharma, and Karthik Subramanian.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span>
[<a id="ref-RFC768">RFC768</a>] Postel, J., "User Datagram Protocol", STD 6, <a href="./rfc768">RFC 768</a>,
August 1980.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006.
[<a id="ref-RFC4601">RFC4601</a>] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", <a href="./rfc4601">RFC 4601</a>, August 2006.
[<a id="ref-RFC6513">RFC6513</a>] Rosen, E., Ed., and R. Aggarwal, Ed., "Multicast in
MPLS/BGP IP VPNs", <a href="./rfc6513">RFC 6513</a>, February 2012.
<span class="grey">Cai, et al. Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc6516">RFC 6516</a> IPv6 MVPN Support February 2012</span>
Authors' Addresses
Yiqun Cai
Cisco Systems, Inc.
170 Tasman Drive
San Jose, CA 95134
EMail: [email protected]
Eric C. Rosen (editor)
Cisco Systems, Inc.
1414 Massachusetts Avenue
Boxborough, MA 01719
EMail: [email protected]
IJsbrand Wijnands
Cisco Systems, Inc.
De kleetlaan 6a Diegem 1831
Belgium
EMail: [email protected]
Cai, et al. Standards Track [Page 6]
Annotations
Select text to annotate