8114
PROPOSED STANDARD
Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network
Authors: M. Boucadair, C. Qin, C. Jacquenet, Y. Lee, Q. Wang
Date: March 2017
Area: int
Working Group: softwire
Stream: IETF
Abstract
This document specifies a solution for the delivery of IPv4 multicast services to IPv4 clients over an IPv6 multicast network. The solution relies upon a stateless IPv4-in-IPv6 encapsulation scheme and uses an IPv6 multicast distribution tree to deliver IPv4 multicast traffic. The solution is particularly useful for the delivery of multicast service offerings to customers serviced by Dual-Stack Lite (DS-Lite).
RFC 8114
PROPOSED STANDARD
Internet Engineering Task Force (IETF) M. Boucadair
Request for Comments: 8114 Orange
Category: Standards Track C. Qin
ISSN: 2070-1721 Cisco
C. Jacquenet
Orange
Y. Lee
Comcast
Q. Wang
China Telecom
March 2017
<span class="h1">Delivery of IPv4 Multicast Services to IPv4 Clients over</span>
<span class="h1">an IPv6 Multicast Network</span>
Abstract
This document specifies a solution for the delivery of IPv4 multicast
services to IPv4 clients over an IPv6 multicast network. The
solution relies upon a stateless IPv4-in-IPv6 encapsulation scheme
and uses an IPv6 multicast distribution tree to deliver IPv4
multicast traffic. The solution is particularly useful for the
delivery of multicast service offerings to customers serviced by
Dual-Stack Lite (DS-Lite).
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="./rfc7841#section-2">Section 2 of RFC 7841</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/rfc8114">http://www.rfc-editor.org/info/rfc8114</a>.
<span class="grey">Boucadair, et al. Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
Copyright Notice
Copyright (c) 2017 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
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.
<span class="grey">Boucadair, et al. Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-1.1">1.1</a>. Requirements Language . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3">3</a>. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4">4</a>. Solution Overview . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4.1">4.1</a>. IPv4-Embedded IPv6 Prefixes . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-4.2">4.2</a>. Multicast Distribution Tree Computation . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-4.3">4.3</a>. Multicast Data Forwarding . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-5">5</a>. IPv4/IPv6 Address Mapping . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-5.1">5.1</a>. Prefix Assignment . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-5.2">5.2</a>. Multicast Address Translation Algorithm . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-5.3">5.3</a>. Textual Representation . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-5.4">5.4</a>. Examples . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-6">6</a>. Multicast B4 (mB4) . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-6.1">6.1</a>. IGMP-MLD Interworking Function . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-6.2">6.2</a>. Multicast Data Forwarding . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-6.3">6.3</a>. Fragmentation . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-6.4">6.4</a>. Host Built-In mB4 Function . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-6.5">6.5</a>. Preserve the Scope . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-7">7</a>. Multicast AFTR (mAFTR) . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-7.1">7.1</a>. Routing Considerations . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-7.2">7.2</a>. Processing PIM Messages . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-7.3">7.3</a>. Switching from Shared Tree to Shortest Path Tree . . . . <a href="#page-15">15</a>
<a href="#section-7.4">7.4</a>. Multicast Data Forwarding . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-7.5">7.5</a>. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-8">8</a>. Deployment Considerations . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-8.1">8.1</a>. Other Operational Modes . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-8.1.1">8.1.1</a>. The IPv6 DR is Co-located with the mAFTR . . . . . . <a href="#page-16">16</a>
<a href="#section-8.1.2">8.1.2</a>. The IPv4 DR is Co-located with the mAFTR . . . . . . <a href="#page-16">16</a>
<a href="#section-8.2">8.2</a>. Load Balancing . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-8.3">8.3</a>. mAFTR Policy Configuration . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-8.4">8.4</a>. Static vs. Dynamic PIM Triggering . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-9.1">9.1</a>. Firewall Configuration . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-10">10</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
<a href="#section-11.1">11.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
<a href="#section-11.2">11.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
<a href="#appendix-A">Appendix A</a>. Use Case: IPTV . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
<a href="#appendix-B">Appendix B</a>. Older Versions of Group Membership Management
Protocols . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a>
<span class="grey">Boucadair, et al. Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
DS-Lite [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>] is an IPv4 address-sharing technique that enables
operators to multiplex public IPv4 addresses while provisioning only
IPv6 to users. A typical DS-Lite scenario is the delivery of an IPv4
service to an IPv4 user over an IPv6 network (denoted as a 4-6-4
scenario). [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>] covers unicast services exclusively.
This document specifies a generic solution for the delivery of IPv4
multicast services to IPv4 clients over an IPv6 multicast network.
The solution was developed with DS-Lite in mind (see more discussion
below). However, the solution is not limited to DS-Lite; it can also
be applied in other deployment contexts, such as the ones described
in [<a href="./rfc7596" title=""Lightweight 4over6: An Extension to the Dual- Stack Lite Architecture"">RFC7596</a>] and [<a href="./rfc7597" title=""Mapping of Address and Port with Encapsulation (MAP-E)"">RFC7597</a>].
If customers have to access IPv4 multicast-based services through a
DS-Lite environment, Address Family Transition Router (AFTR) devices
will have to process all the Internet Group Management Protocol
(IGMP) Report messages [<a href="./rfc2236" title=""Internet Group Management Protocol, Version 2"">RFC2236</a>] [<a href="./rfc3376" title=""Internet Group Management Protocol, Version 3"">RFC3376</a>] that have been forwarded
by the Customer Premises Equipment (CPE) into the IPv4-in-IPv6
tunnels. From that standpoint, AFTR devices are likely to behave as
a replication point for downstream multicast traffic, and the
multicast packets will be replicated for each tunnel endpoint that
IPv4 receivers are connected to.
This kind of DS-Lite environment raises two major issues:
1. The IPv6 network loses the benefits of efficient multicast
traffic forwarding because it is unable to deterministically
replicate the data as close to the receivers as possible. As a
consequence, the downstream bandwidth in the IPv6 network will be
vastly consumed by sending multicast data over a unicast
infrastructure.
2. The AFTR is responsible for replicating multicast traffic and
forwarding it into each tunnel endpoint connecting IPv4 receivers
that have explicitly asked for the corresponding content. This
process may significantly consume the AFTR's resources and
overload the AFTR.
This document specifies an extension to the DS-Lite model to deliver
IPv4 multicast services to IPv4 clients over an IPv6 multicast-
enabled network.
<span class="grey">Boucadair, et al. Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
This document describes a stateless translation mechanism that
supports either Source-Specific Multicast (SSM) or Any-Source
Multicast (ASM) operation. The recommendation in <a href="./rfc4607#section-1">Section 1 of
[RFC4607]</a> is that multicast services use SSM where possible; the
operation of the translation mechanism is also simplified when SSM is
used, e.g., considerations for placement of the IPv6 Rendezvous Point
(RP) are no longer relevant.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</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">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
This document makes use of the following terms:
IPv4-embedded IPv6 address: an IPv6 address that embeds a 32-bit-
encoded IPv4 address. An IPv4-embedded IPv6 address can be
unicast or multicast.
mPrefix64: a dedicated multicast IPv6 prefix for constructing
IPv4-embedded IPv6 multicast addresses. mPrefix64 can be of two
types: ASM_mPrefix64 used in Any-Source Multicast (ASM) mode or
SSM_mPrefix64 used in Source-Specific Multicast (SSM) mode
[<a href="./rfc4607" title=""Source-Specific Multicast for IP"">RFC4607</a>]. The size of this prefix is /96.
Note: "64" is used as an abbreviation for IPv6-IPv4
interconnection.
uPrefix64: a dedicated IPv6 unicast prefix for constructing
IPv4-embedded IPv6 unicast addresses [<a href="./rfc6052" title=""IPv6 Addressing of IPv4/IPv6 Translators"">RFC6052</a>]. This prefix may
be either the Well-Known Prefix (i.e., 64:ff9b::/96) or a Network-
Specific Prefix (NSP).
Multicast AFTR (mAFTR): a functional entity that supports an
IPv4-IPv6 multicast interworking function (refer to Figure 3). It
receives and encapsulates the IPv4 multicast packets into IPv4-in-
IPv6 packets. Also, it behaves as the corresponding IPv6
multicast source for the encapsulated IPv4-in-IPv6 packets.
Multicast Basic Bridging BroadBand (mB4): a functional entity that
supports an IGMP-MLD Interworking function (refer to <a href="#section-6.1">Section 6.1</a>)
that translates the IGMP messages into the corresponding Multicast
Listener Discovery (MLD) messages and sends the MLD messages to
the IPv6 network. In addition, the mB4 decapsulates IPv4-in-IPv6
multicast packets.
<span class="grey">Boucadair, et al. Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
PIMv4: refers to Protocol Independent Multicast (PIM) when deployed
in an IPv4 infrastructure (i.e., IPv4 transport capabilities are
used to exchange PIM messages).
PIMv6: refers to PIM when deployed in an IPv6 infrastructure (i.e.,
IPv6 transport capabilities are used to exchange PIM messages).
Host portion of the MLD protocol: refers to the part of MLD that
applies to all multicast address listeners (<a href="./rfc3810#section-6">Section 6 of
[RFC3810]</a>). As a reminder, MLD specifies separate behaviors for
multicast address listeners (i.e., hosts or routers that listen to
multicast packets) and multicast routers.
Router portion of IGMP: refers to the part of IGMP that is performed
by multicast routers (<a href="./rfc3376#section-6">Section 6 of [RFC3376]</a>).
DR: refers to the Designated Router as defined in [<a href="./rfc7761" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC7761</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Scope</span>
This document focuses only on the subscription to IPv4 multicast
groups and the delivery of IPv4-formatted content to IPv4 receivers
over an IPv6-only network. In particular, only the following case is
covered:
IPv4 receivers access IPv4 multicast content over IPv6-only
multicast-enabled networks.
This document does not cover the source/receiver heuristics, where
IPv4 receivers can also behave as IPv4 multicast sources. This
document assumes that hosts behind the mB4 are IPv4 multicast
receivers only. Also, the document covers the host built-in mB4
function.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Solution Overview</span>
In the DS-Lite specification [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>], an IPv4-in-IPv6 tunnel is
used to carry bidirectional IPv4 unicast traffic between a B4 and an
AFTR. The solution specified in this document provides an IPv4-in-
IPv6 encapsulation scheme to deliver unidirectional IPv4 multicast
traffic from an mAFTR to an mB4.
An overview of the solution is provided in this section; it is
intended as an introduction to how it works but is not normative.
For the normative specifications of the two new functional elements,
mB4 and mAFTR (Figure 1), refer to Sections <a href="#section-6">6</a> and <a href="#section-7">7</a>.
<span class="grey">Boucadair, et al. Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
------------
/ \
| IPv4 network |
\ /
------------
IPv4 multicast : | ^ PIMv4 Join
v | :
+-------------+
| mAFTR |
+-------------+
IPv6 multicast |:| | ^ PIMv6 Join (PIMv6
(IPv4 embedded) |:| | : routers in between)
------------
/ \
| IPv6 network |
\ /
------------
|:| | ^ MLD Report
|v| | :
+-----------+
| mB4 |
+-----------+
IPv4 multicast : | ^ IGMP Report
v | :
+-----------+
| IPv4 |
| receiver |
+-----------+
Figure 1: Functional Architecture
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. IPv4-Embedded IPv6 Prefixes</span>
In order to map the addresses of IPv4 multicast traffic with IPv6
multicast addresses, an IPv6 multicast prefix (mPrefix64) and an IPv6
unicast prefix (uPrefix64) are provided to the mAFTR and the mB4
elements, both of which contribute to the computation and the
maintenance of the IPv6 multicast distribution tree that extends the
IPv4 multicast distribution tree into the IPv6 multicast network.
The IPv4/IPv6 address mapping is stateless.
The mAFTR and the mB4 use mPrefix64 to convert an IPv4 multicast
address (G4) into an IPv4-embedded IPv6 multicast address (G6). The
mAFTR and the mB4 use uPrefix64 to convert an IPv4 source address
(S4) into an IPv4-embedded IPv6 address (S6). The mAFTR and the mB4
must use the same mPrefix64 and uPrefix64; they also run the same
algorithm for building IPv4-embedded IPv6 addresses. Refer to
<a href="#section-5">Section 5</a> for more details about the address mapping.
<span class="grey">Boucadair, et al. Standards Track [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Multicast Distribution Tree Computation</span>
When an IPv4 receiver connected to the device that embeds the mB4
capability wants to subscribe to an IPv4 multicast group, it sends an
IGMP Report message towards the mB4. The mB4 creates the IPv6
multicast group (G6) address using mPrefix64 and the original IPv4
multicast group address. If the receiver sends a source-specific
IGMPv3 Report message, the mB4 will create the IPv6 source address
(S6) using uPrefix64 and the original IPv4 source address.
The mB4 uses the G6 (and both S6 and G6 in SSM) to create the
corresponding MLD Report message. The mB4 sends the Report message
towards the IPv6 network. The PIMv6 DR receives the MLD Report
message and sends the PIMv6 Join message to join the IPv6 multicast
distribution tree. It can send either PIMv6 Join (*,G6) in ASM or
PIMv6 Join (S6,G6) in SSM to the mAFTR.
The mAFTR acts as the IPv6 DR to which the uPrefix64-derived S6 is
connected. The mAFTR will receive the source-specific PIMv6 Join
message (S6,G6) from the IPv6 multicast network. If the mAFTR is the
Rendezvous Point (RP) of G6, it will receive the any-source PIMv6
Join message (*,G6) from the IPv6 multicast network. If the mAFTR is
not the RP of G6, it will send the PIM Register message to the RP of
G6 located in the IPv6 multicast network. For the sake of
simplicity, it is recommended to configure the mAFTR as the RP for
the IPv4-embedded IPv6 multicast groups it manages; no registration
procedure is required under this configuration.
When the mAFTR receives the PIMv6 Join message (*,G6), it will
extract the IPv4 multicast group address (G4). If the mAFTR is the
RP of G4 in the IPv4 multicast network, it will create a (*,G4) entry
(if such entry does not already exist) in its own IPv4 multicast
routing table. If the mAFTR is not the RP of G4, it will send the
corresponding PIMv4 Join message (*,G4) towards the RP of G4 in the
IPv4 multicast network.
When the mAFTR receives the PIMv6 Join message (S6,G6), it will
extract the IPv4 multicast group address (G4) and IPv4 source address
(S4) and send the corresponding (S4,G4) PIMv4 Join message directly
to the IPv4 source.
A branch of the multicast distribution tree is thus constructed,
comprising both an IPv4 part (from the mAFTR upstream) and an IPv6
part (from mAFTR downstream towards the mB4).
The mAFTR advertises the route of uPrefix64 with an IPv6 Interior
Gateway Protocol (IGP), so as to represent the IPv4-embedded IPv6
source in the IPv6 multicast network and to allow IPv6 routers to run
<span class="grey">Boucadair, et al. Standards Track [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
the Reverse Path Forwarding (RPF) check procedure on incoming
multicast traffic. Injecting internal /96 routes is not problematic
given the recommendation in [<a href="./rfc7608" title=""IPv6 Prefix Length Recommendation for Forwarding"">RFC7608</a>] that requires that forwarding
processes must be designed to process prefixes of any length up to
/128.
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Multicast Data Forwarding</span>
When the mAFTR receives an IPv4 multicast packet, it will encapsulate
the packet into an IPv6 multicast packet using the IPv4-embedded IPv6
multicast address as the destination address and an IPv4-embedded
IPv6 unicast address as the source address. The encapsulated IPv6
multicast packet will be forwarded down the IPv6 multicast
distribution tree, and the mB4 will eventually receive the packet.
The IPv6 multicast network treats the IPv4-in-IPv6 encapsulated
multicast packets as native IPv6 multicast packets. The IPv6
multicast routers use the outer IPv6 header to make their forwarding
decisions.
When the mB4 receives the IPv6 multicast packet (to G6) derived by
mPrefix64, it decapsulates it and forwards the original IPv4
multicast packet towards the receivers subscribing to G4.
Note: At this point, only IPv4-in-IPv6 encapsulation is defined;
however, other types of encapsulation could be defined in the future.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IPv4/IPv6 Address Mapping</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Prefix Assignment</span>
A dedicated IPv6 multicast prefix (mPrefix64) is provisioned to the
mAFTR and the mB4. The mAFTR and the mB4 use the mPrefix64 to form
an IPv6 multicast group address from an IPv4 multicast group address.
The mPrefix64 can be of two types: ASM_mPrefix64 (an mPrefix64 used
in ASM mode) or SSM_mPrefix64 (an mPrefix64 used in SSM mode). The
mPrefix64 MUST be derived from the corresponding IPv6 multicast
address space (e.g., the SSM_mPrefix64 must be in the range of the
multicast address space specified in [<a href="./rfc4607" title=""Source-Specific Multicast for IP"">RFC4607</a>]).
The IPv6 part of the multicast distribution tree can be seen as an
extension of the IPv4 part of the multicast distribution tree. The
IPv4 source address MUST be mapped to an IPv6 source address. An
IPv6 unicast prefix (uPrefix64) is provisioned to the mAFTR and the
mB4. The mAFTR and the mB4 use the uPrefix64 to form an IPv6 source
address from an IPv4 source address as specified in [<a href="./rfc6052" title=""IPv6 Addressing of IPv4/IPv6 Translators"">RFC6052</a>]. The
<span class="grey">Boucadair, et al. Standards Track [Page 9]</span><span id="page-10" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
uPrefix-formed IPv6 source address will represent the original IPv4
source in the IPv6 multicast network. The uPrefix64 MUST be derived
from the IPv6 unicast address space.
The multicast address translation MUST follow the algorithm defined
in <a href="#section-5.2">Section 5.2</a>.
The mPrefix64 and uPrefix64 can be configured in the mB4 using a
variety of methods, including an out-of-band mechanism, manual
configuration, or a dedicated provisioning protocol (e.g., using
DHCPv6 [<a href="./rfc8115" title=""DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 Prefixes"">RFC8115</a>]).
The stateless translation mechanism described in <a href="#section-5">Section 5</a> does not
preclude use of Embedded-RP [<a href="./rfc3956" title=""Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address"">RFC3956</a>] [<a href="./rfc7371" title=""Updates to the IPv6 Multicast Addressing Architecture"">RFC7371</a>].
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Multicast Address Translation Algorithm</span>
IPv4-embedded IPv6 multicast addresses are composed according to the
following algorithm:
o Concatenate the 96 bits of the mPrefix64 and the 32 bits of the
IPv4 address to obtain a 128-bit address.
The IPv4 multicast addresses are extracted from the IPv4-embedded
IPv6 multicast addresses according to the following algorithm:
o If the multicast address has a pre-configured mPrefix64, extract
the last 32 bits of the IPv6 multicast address.
An IPv4 source is represented in the IPv6 realm with its
IPv4-converted IPv6 address [<a href="./rfc6052" title=""IPv6 Addressing of IPv4/IPv6 Translators"">RFC6052</a>].
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Textual Representation</span>
The embedded IPv4 address in an IPv6 multicast address is included in
the last 32 bits; therefore, dotted decimal notation can be used.
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Examples</span>
Group address mapping example:
+---------------------+--------------+----------------------------+
| mPrefix64 | IPv4 address | IPv4-Embedded IPv6 address |
+---------------------+--------------+----------------------------+
| ff0x::db8:0:0/96 | 233.252.0.1 | ff0x::db8:233.252.0.1 |
+---------------------+--------------+----------------------------+
<span class="grey">Boucadair, et al. Standards Track [Page 10]</span><span id="page-11" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
Source address mapping example when a /96 is used:
+---------------------+--------------+----------------------------+
| uPrefix64 | IPv4 address | IPv4-Embedded IPv6 address |
+---------------------+--------------+----------------------------+
| 2001:db8::/96 | 192.0.2.33 | 2001:db8::192.0.2.33 |
+---------------------+--------------+----------------------------+
IPv4 and IPv6 addresses used in this example are derived from the
IPv4 and IPv6 blocks reserved for documentation, as per [<a href="./rfc6676" title=""Multicast Addresses for Documentation"">RFC6676</a>].
The unicast IPv4 address of the above example is derived from the
documentation address block defined in [<a href="./rfc6890" title=""Special-Purpose IP Address Registries"">RFC6890</a>].
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Multicast B4 (mB4)</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. IGMP-MLD Interworking Function</span>
The IGMP-MLD Interworking function combines the IGMP/MLD Proxying
function and the address-synthesizing operations. The IGMP/MLD
Proxying function is specified in [<a href="./rfc4605" title=""Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("">RFC4605</a>]. The address translation
is stateless and MUST follow the address mapping specified in
<a href="#section-5">Section 5</a>.
The mB4 performs the host portion of the MLD protocol on the upstream
interface. The composition of IPv6 membership in this context is
constructed through address-synthesizing operations and MUST
synchronize with the membership database maintained in the IGMP
domain. MLD messages are sent natively to the direct-connected IPv6
multicast routers (they will be processed by the PIM DR). The mB4
also performs the router portion of IGMP on the downstream
interface(s). Refer to [<a href="./rfc4605" title=""Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("">RFC4605</a>] for more details.
+----------+ IGMP +-------+ MLD +---------+
| IPv4 |---------| mB4 |---------| PIM |
| Receiver | | | | DR |
+----------+ +-------+ +---------+
Figure 2: IGMP-MLD Interworking
If SSM is deployed, the mB4 MUST construct the IPv6 source address
(or retrieve the IPv4 source address) using the uPrefix64. The mB4
MAY create a membership database that associates the IPv4-IPv6
multicast groups with the interfaces (e.g., WLAN and Wired Ethernet)
facing IPv4 multicast receivers.
<span class="grey">Boucadair, et al. Standards Track [Page 11]</span><span id="page-12" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Multicast Data Forwarding</span>
When the mB4 receives an IPv6 multicast packet, it MUST check the
group address and the source address. If the IPv6 multicast group
prefix is mPrefix64 and the IPv6 source prefix is uPrefix64, the mB4
MUST decapsulate the IPv6 header [<a href="./rfc2473" title=""Generic Packet Tunneling in IPv6 Specification"">RFC2473</a>]; the decapsulated IPv4
multicast packet will be forwarded through each relevant interface
following standard IPv4 multicast forwarding procedures. Otherwise,
the mB4 MUST silently drop the packet.
As an illustration, if a packet is received from source
2001:db8::192.0.2.33 and needs to be forwarded to group
ff3x:20:2001:db8::233.252.0.1, the mB4 decapsulates it into an IPv4
multicast packet using 192.0.2.33 as the IPv4 source address and
using 233.252.0.1 as the IPv4 destination multicast group. This
example assumes that the mB4 is provisioned with uPrefix64
(2001:db8::/96) and mPrefix64 (ff3x:20:2001:db8::/96).
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Fragmentation</span>
Encapsulating IPv4 multicast packets into IPv6 multicast packets that
will be forwarded by the mAFTR towards the mB4 along the IPv6
multicast distribution tree reduces the effective MTU size by the
size of an IPv6 header. In this specification, the data flow is
unidirectional from the mAFTR to the mB4. The mAFTR MUST fragment
the oversized IPv6 packet after the encapsulation into two IPv6
packets. The mB4 MUST reassemble the IPv6 packets, decapsulate the
IPv6 header, and forward the IPv4 packet to the hosts that have
subscribed to the corresponding multicast group. Further
considerations about fragmentation issues are documented in Sections
5.3 and 6.3 of [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>].
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Host Built-In mB4 Function</span>
If the mB4 function is implemented in the host that is directly
connected to an IPv6-only network, the host MUST implement the
behaviors specified in Sections <a href="#section-6.1">6.1</a>, <a href="#section-6.2">6.2</a>, and <a href="#section-6.3">6.3</a>. The host MAY
optimize the implementation to provide an Application Programming
Interface (API) or kernel module to skip the IGMP-MLD Interworking
function. Optimization considerations are out of scope of this
specification.
<span class="grey">Boucadair, et al. Standards Track [Page 12]</span><span id="page-13" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Preserve the Scope</span>
When several mPrefix64s are available, if each enclosed IPv4-embedded
IPv6 multicast prefix has a distinct scope, the mB4 MUST select the
appropriate IPv4-embedded IPv6 multicast prefix whose scope matches
the IPv4 multicast address used to synthesize an IPv4-embedded IPv6
multicast address (specific mappings are listed in <a href="./rfc2365#section-8">Section 8 of
[RFC2365]</a>). Mapping is achieved such that the scope of the selected
IPv6 multicast prefix does not exceed the original IPv4 multicast
scope. If the mB4 is instructed to preserve the scope but no IPv6
multicast prefix that matches the IPv4 multicast scope is found, IPv6
multicast address mapping SHOULD fail.
The mB4 MAY be configured to not preserve the scope when enforcing
the address translation algorithm.
Consider that an mB4 is configured with two mPrefix64s,
ff0e::db8:0:0/96 (global scope) and ff08::db8:0:0/96 (organization
scope). If the mB4 receives an IGMP Report message from an IPv4
receiver to subscribe to 233.252.0.1, it checks which mPrefix64 to
use in order to preserve the scope of the requested IPv4 multicast
group. In this example, given that 233.252.0.1 is intended for
global use, the mB4 creates the IPv6 multicast group (G6) address
using ff0e::db8:0:0/96 and the original IPv4 multicast group address
(233.252.0.1): ff0e::db8:233.252.0.1.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Multicast AFTR (mAFTR)</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Routing Considerations</span>
The mAFTR is responsible for interconnecting the IPv4 multicast
distribution tree with the corresponding IPv6 multicast distribution
tree. The mAFTR MUST use the uPrefix64 to build the IPv6 source
addresses of the multicast group address derived from mPrefix64. In
other words, the mAFTR MUST be the multicast source whose address is
derived from uPrefix64.
The mAFTR MUST advertise the route towards uPrefix64 with the IPv6
IGP. This is needed by the IPv6 multicast routers so that they
acquire the routing information to discover the source.
<span class="grey">Boucadair, et al. Standards Track [Page 13]</span><span id="page-14" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Processing PIM Messages</span>
The mAFTR MUST interwork PIM Join/Prune messages for (*,G6) and
(S6,G6) on their corresponding (*,G4) and (S4,G4). The following
text specifies the expected behavior of the mAFTR for PIM Join
messages.
+---------+
---------| mAFTR |---------
PIMv6 |uPrefix64| PIMv4
|mPrefix64|
+---------+
Figure 3: PIMv6-PIMv4 Interworking Function
The mAFTR contains two separate Tree Information Bases (TIBs): the
IPv4 Tree Information Base (TIB4) and the IPv6 Tree Information Base
(TIB6), which are bridged by one IPv4-in-IPv6 virtual interface. It
should be noted that TIB implementations may vary (e.g., some may
rely upon a single integrated TIB without any virtual interface), but
they should follow this specification for the sake of global and
functional consistency.
When an mAFTR receives a PIMv6 Join message (*,G6) with an IPv6
multicast group address (G6) that is derived from the mPrefix64, it
MUST check its IPv6 Tree Information Base (TIB6). If there is an
entry for this G6 address, it MUST check whether the interface
through which the PIMv6 Join message has been received is in the
outgoing interface (oif) list. If not, the mAFTR MUST add the
interface to the oif list. If there is no entry in the TIB6, the
mAFTR MUST create a new entry (*,G6) for the multicast group.
Whether or not the IPv4-in-IPv6 virtual interface is set as the
incoming interface of the newly created entry is up to the
implementation, but it should comply with the mAFTR's multicast data
forwarding behavior (see <a href="#section-7.4">Section 7.4</a>).
The mAFTR MUST extract the IPv4 multicast group address (G4) from the
IPv4-embedded IPv6 multicast address (G6) contained in the PIMv6 Join
message. The mAFTR MUST check its IPv4 Tree Information Base (TIB4).
If there is an entry for G4, it MUST check whether the IPv4-in-IPv6
virtual interface is in the outgoing interface list. If not, the
mAFTR MUST add the interface to the oif list. If there is no entry
for G4, the mAFTR MUST create a new (*,G4) entry in its TIB4 and
initiate the procedure for building the shared tree in the IPv4
multicast network without any additional requirement.
<span class="grey">Boucadair, et al. Standards Track [Page 14]</span><span id="page-15" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
If the mAFTR receives a source-specific Join message, the (S6,G6) is
processed rather than (*,G6). The procedures of processing (S6,G6)
and (*,G6) are almost the same. Differences have been detailed in
[<a href="./rfc7761" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC7761</a>].
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Switching from Shared Tree to Shortest Path Tree</span>
When the mAFTR receives the first IPv4 multicast packet, it may
extract the source address (S4) from the packet and send an Explicit
PIMv4 (S4,G4) Join message directly to S4. The mAFTR switches from
the shared Rendezvous Point Tree (RPT) to the Shortest Path Tree
(SPT) for G4.
For IPv6 multicast routers to switch to the SPT, there is no new
requirement. IPv6 multicast routers may send an Explicit PIMv6 Join
to the mAFTR once the first (S6,G6) multicast packet arrives from
upstream multicast routers.
<span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. Multicast Data Forwarding</span>
When the mAFTR receives an IPv4 multicast packet, it checks its TIB4
to find a matching entry and then forwards the packet to the
interface(s) listed in the outgoing interface list. If the IPv4-in-
IPv6 virtual interface also belongs to this list, the packet is
encapsulated with the mPrefix64-derived and uPrefix64-derived
IPv4-embedded IPv6 addresses to form an IPv6 multicast packet
[<a href="./rfc2473" title=""Generic Packet Tunneling in IPv6 Specification"">RFC2473</a>]. Then another lookup is made by the mAFTR to find a
matching entry in the TIB6. Whether or not the RPF check for the
second lookup is performed is up to the implementation and is out of
the scope of this document. The IPv6 multicast packet is then
forwarded along the IPv6 multicast distribution tree, based upon the
outgoing interface list of the matching entry in the TIB6.
As an illustration, if a packet is received from source 192.0.2.33
and needs to be forwarded to group 233.252.0.1, the mAFTR
encapsulates it into an IPv6 multicast packet using
ff3x:20:2001:db8::233.252.0.1 as the IPv6 destination multicast group
and using 2001:db8::192.0.2.33 as the IPv6 source address.
<span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Scope</span>
The Scope field of IPv4-in-IPv6 multicast addresses should be valued
accordingly (e.g., to "E" for global scope) in the deployment
environment. This specification does not discuss the scope value
that should be used.
The considerations in <a href="#section-6.5">Section 6.5</a> are to be followed by the mAFTR.
<span class="grey">Boucadair, et al. Standards Track [Page 15]</span><span id="page-16" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Deployment Considerations</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Other Operational Modes</span>
<span class="h4"><a class="selflink" id="section-8.1.1" href="#section-8.1.1">8.1.1</a>. The IPv6 DR is Co-located with the mAFTR</span>
The mAFTR can embed the MLD Querier function (as well as the PIMv6
DR) for optimization purposes. When the mB4 sends an MLD Report
message to this mAFTR, the mAFTR should process the MLD Report
message that contains the IPv4-embedded IPv6 multicast group address
and then send the corresponding PIMv4 Join message (Figure 4).
+---------+
---------| mAFTR |---------
MLD |uPrefix64| PIMv4
|mPrefix64|
+---------+
Figure 4: MLD-PIMv4 Interworking Function
Discussions about the location of the mAFTR capability and related
ASM or SSM multicast design considerations are out of the scope of
this document.
<span class="h4"><a class="selflink" id="section-8.1.2" href="#section-8.1.2">8.1.2</a>. The IPv4 DR is Co-located with the mAFTR</span>
If the mAFTR is co-located with the IPv4 DR connected to the original
IPv4 source, it may simply use the uPrefix64 and mPrefix64 prefixes
to build the IPv4-embedded IPv6 multicast packets, and the sending of
PIMv4 Join messages becomes unnecessary.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Load Balancing</span>
For robustness and load distribution purposes, several nodes in the
network can embed the mAFTR function. In such case, the same IPv6
prefixes (i.e., mPrefix64 and uPrefix64) and algorithm to build
IPv4-embedded IPv6 addresses must be configured on those nodes.
<span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. mAFTR Policy Configuration</span>
The mAFTR may be configured with a list of IPv4 multicast groups and
sources. Only multicast flows bound to the configured addresses
should be handled by the mAFTR. Otherwise, packets are silently
dropped.
<span class="grey">Boucadair, et al. Standards Track [Page 16]</span><span id="page-17" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
<span class="h3"><a class="selflink" id="section-8.4" href="#section-8.4">8.4</a>. Static vs. Dynamic PIM Triggering</span>
To optimize the usage of network resources in current deployments,
all multicast streams are conveyed in the core network while only the
most popular ones are forwarded in the aggregation/access networks
(static mode). Less popular streams are forwarded in the access
network upon request (dynamic mode). Depending on the location of
the mAFTR in the network, two modes can be envisaged: static and
dynamic.
Static Mode: The mAFTR is configured to instantiate permanent
(S6,G6) and (*,G6) entries in its TIB6 using a pre-configured
(S4,G4) list.
Dynamic Mode: The instantiation or withdrawal of (S6,G6) or (*,G6)
entries is triggered by the receipt of PIMv6 messages.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
Besides multicast scoping considerations (see Sections <a href="#section-6.5">6.5</a> and <a href="#section-7.5">7.5</a>),
this document does not introduce any new security concerns in
addition to those discussed in <a href="./rfc6052#section-5">Section 5 of [RFC6052]</a>, <a href="./rfc3810#section-10">Section 10 of
[RFC3810]</a>, and <a href="./rfc7761#section-6">Section 6 of [RFC7761]</a>.
Unlike solutions that map IPv4 multicast flows to IPv6 unicast flows,
this document does not exacerbate Denial-of-Service (DoS) attacks.
An mB4 SHOULD be provided with appropriate configuration information
to preserve the scope of a multicast message when mapping an IPv4
multicast address into an IPv4-embedded IPv6 multicast address and
vice versa.
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Firewall Configuration</span>
The CPE that embeds the mB4 function SHOULD be configured to accept
incoming MLD messages and traffic forwarded to multicast groups
subscribed to by receivers located in the customer premises.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IANA Considerations</span>
This document does not require any IANA actions.
<span class="grey">Boucadair, et al. Standards Track [Page 17]</span><span id="page-18" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
[<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>,
DOI 10.17487/RFC2119, March 1997,
<<a href="https://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC2365">RFC2365</a>] Meyer, D., "Administratively Scoped IP Multicast", <a href="https://www.rfc-editor.org/bcp/bcp23">BCP 23</a>,
<a href="./rfc2365">RFC 2365</a>, DOI 10.17487/RFC2365, July 1998,
<<a href="https://www.rfc-editor.org/info/rfc2365">http://www.rfc-editor.org/info/rfc2365</a>>.
[<a id="ref-RFC2473">RFC2473</a>] Conta, A. and S. Deering, "Generic Packet Tunneling in
IPv6 Specification", <a href="./rfc2473">RFC 2473</a>, DOI 10.17487/RFC2473,
December 1998, <<a href="https://www.rfc-editor.org/info/rfc2473">http://www.rfc-editor.org/info/rfc2473</a>>.
[<a id="ref-RFC3376">RFC3376</a>] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version
3", <a href="./rfc3376">RFC 3376</a>, DOI 10.17487/RFC3376, October 2002,
<<a href="https://www.rfc-editor.org/info/rfc3376">http://www.rfc-editor.org/info/rfc3376</a>>.
[<a id="ref-RFC3810">RFC3810</a>] Vida, R., Ed. and L. Costa, Ed., "Multicast Listener
Discovery Version 2 (MLDv2) for IPv6", <a href="./rfc3810">RFC 3810</a>,
DOI 10.17487/RFC3810, June 2004,
<<a href="https://www.rfc-editor.org/info/rfc3810">http://www.rfc-editor.org/info/rfc3810</a>>.
[<a id="ref-RFC4605">RFC4605</a>] Fenner, B., He, H., Haberman, B., and H. Sandick,
"Internet Group Management Protocol (IGMP) / Multicast
Listener Discovery (MLD)-Based Multicast Forwarding
("IGMP/MLD Proxying")", <a href="./rfc4605">RFC 4605</a>, DOI 10.17487/RFC4605,
August 2006, <<a href="https://www.rfc-editor.org/info/rfc4605">http://www.rfc-editor.org/info/rfc4605</a>>.
[<a id="ref-RFC4607">RFC4607</a>] Holbrook, H. and B. Cain, "Source-Specific Multicast for
IP", <a href="./rfc4607">RFC 4607</a>, DOI 10.17487/RFC4607, August 2006,
<<a href="https://www.rfc-editor.org/info/rfc4607">http://www.rfc-editor.org/info/rfc4607</a>>.
[<a id="ref-RFC6052">RFC6052</a>] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X.
Li, "IPv6 Addressing of IPv4/IPv6 Translators", <a href="./rfc6052">RFC 6052</a>,
DOI 10.17487/RFC6052, October 2010,
<<a href="https://www.rfc-editor.org/info/rfc6052">http://www.rfc-editor.org/info/rfc6052</a>>.
[<a id="ref-RFC6333">RFC6333</a>] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4
Exhaustion", <a href="./rfc6333">RFC 6333</a>, DOI 10.17487/RFC6333, August 2011,
<<a href="https://www.rfc-editor.org/info/rfc6333">http://www.rfc-editor.org/info/rfc6333</a>>.
<span class="grey">Boucadair, et al. Standards Track [Page 18]</span><span id="page-19" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
[<a id="ref-RFC7608">RFC7608</a>] Boucadair, M., Petrescu, A., and F. Baker, "IPv6 Prefix
Length Recommendation for Forwarding", <a href="https://www.rfc-editor.org/bcp/bcp198">BCP 198</a>, <a href="./rfc7608">RFC 7608</a>,
DOI 10.17487/RFC7608, July 2015,
<<a href="https://www.rfc-editor.org/info/rfc7608">http://www.rfc-editor.org/info/rfc7608</a>>.
[<a id="ref-RFC7761">RFC7761</a>] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
Multicast - Sparse Mode (PIM-SM): Protocol Specification
(Revised)", STD 83, <a href="./rfc7761">RFC 7761</a>, DOI 10.17487/RFC7761, March
2016, <<a href="https://www.rfc-editor.org/info/rfc7761">http://www.rfc-editor.org/info/rfc7761</a>>.
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
[<a id="ref-RFC2236">RFC2236</a>] Fenner, W., "Internet Group Management Protocol, Version
2", <a href="./rfc2236">RFC 2236</a>, DOI 10.17487/RFC2236, November 1997,
<<a href="https://www.rfc-editor.org/info/rfc2236">http://www.rfc-editor.org/info/rfc2236</a>>.
[<a id="ref-RFC3956">RFC3956</a>] Savola, P. and B. Haberman, "Embedding the Rendezvous
Point (RP) Address in an IPv6 Multicast Address",
<a href="./rfc3956">RFC 3956</a>, DOI 10.17487/RFC3956, November 2004,
<<a href="https://www.rfc-editor.org/info/rfc3956">http://www.rfc-editor.org/info/rfc3956</a>>.
[<a id="ref-RFC6676">RFC6676</a>] Venaas, S., Parekh, R., Van de Velde, G., Chown, T., and
M. Eubanks, "Multicast Addresses for Documentation",
<a href="./rfc6676">RFC 6676</a>, DOI 10.17487/RFC6676, August 2012,
<<a href="https://www.rfc-editor.org/info/rfc6676">http://www.rfc-editor.org/info/rfc6676</a>>.
[<a id="ref-RFC6890">RFC6890</a>] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman,
"Special-Purpose IP Address Registries", <a href="https://www.rfc-editor.org/bcp/bcp153">BCP 153</a>,
<a href="./rfc6890">RFC 6890</a>, DOI 10.17487/RFC6890, April 2013,
<<a href="https://www.rfc-editor.org/info/rfc6890">http://www.rfc-editor.org/info/rfc6890</a>>.
[<a id="ref-RFC7371">RFC7371</a>] Boucadair, M. and S. Venaas, "Updates to the IPv6
Multicast Addressing Architecture", <a href="./rfc7371">RFC 7371</a>,
DOI 10.17487/RFC7371, September 2014,
<<a href="https://www.rfc-editor.org/info/rfc7371">http://www.rfc-editor.org/info/rfc7371</a>>.
[<a id="ref-RFC7596">RFC7596</a>] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I.
Farrer, "Lightweight 4over6: An Extension to the Dual-
Stack Lite Architecture", <a href="./rfc7596">RFC 7596</a>, DOI 10.17487/RFC7596,
July 2015, <<a href="https://www.rfc-editor.org/info/rfc7596">http://www.rfc-editor.org/info/rfc7596</a>>.
[<a id="ref-RFC7597">RFC7597</a>] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S.,
Murakami, T., and T. Taylor, Ed., "Mapping of Address and
Port with Encapsulation (MAP-E)", <a href="./rfc7597">RFC 7597</a>,
DOI 10.17487/RFC7597, July 2015,
<<a href="https://www.rfc-editor.org/info/rfc7597">http://www.rfc-editor.org/info/rfc7597</a>>.
<span class="grey">Boucadair, et al. Standards Track [Page 19]</span><span id="page-20" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
[<a id="ref-RFC8115">RFC8115</a>] Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6
Option for IPv4-Embedded Multicast and Unicast IPv6
Prefixes", <a href="./rfc8115">RFC 8115</a>, DOI 10.17487/RFC8115, March 2017,
<<a href="https://www.rfc-editor.org/info/rfc8115">http://www.rfc-editor.org/info/rfc8115</a>>.
<span class="grey">Boucadair, et al. Standards Track [Page 20]</span><span id="page-21" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Use Case: IPTV</span>
IPTV generally includes two categories of service offerings:
o Video on Demand (VoD) that streams unicast video content to
receivers.
o Multicast live TV broadcast services.
Two types of provider are involved in the delivery of this service:
o Content Providers, who usually own the content that is multicast
to receivers. Content providers may contractually define an
agreement with network providers to deliver content to receivers.
o Network Providers, who provide network connectivity services
(e.g., network providers are responsible for carrying multicast
flows from head-ends to receivers).
Note that some contract agreements prevent a network provider from
altering the content as sent by the content provider for various
reasons. Depending on these contract agreements, multicast streams
should be delivered unaltered to the requesting users.
Most current IPTV content is likely to remain IPv4-formatted and out
of the control of network providers. Additionally, there are
numerous legacy receivers (e.g., IPv4-only Set-Top Boxes (STBs)) that
can't be upgraded or easily replaced to support IPv6. As a
consequence, IPv4 service continuity must be guaranteed during the
transition period, including the delivery of multicast services such
as Live TV Broadcasting to users.
<span class="grey">Boucadair, et al. Standards Track [Page 21]</span><span id="page-22" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Older Versions of Group Membership Management Protocols</span>
Given the multiple versions of group membership management protocols,
mismatch issues may arise at the mB4 (refer to <a href="#section-6.1">Section 6.1</a>).
If IGMPv2 operates on the IPv4 receivers while MLDv2 operates on the
MLD Querier, or if IGMPv3 operates on the IPv4 receivers while MLDv1
operates on the MLD Querier, a version mismatch issue will be
encountered. To solve this problem, the mB4 should perform the
router portion of IGMP, which is similar to the corresponding MLD
version (IGMPv2 for MLDv1 or IGMPv3 for MLDv2) operating in the IPv6
domain. Then, the protocol interaction approach specified in
<a href="./rfc3376#section-7">Section 7 of [RFC3376]</a> can be applied to exchange signaling messages
with the IPv4 receivers on which the different version of IGMP is
operating.
Note that the support of IPv4 SSM requires MLDv2 to be enabled in the
IPv6 network.
Acknowledgements
The authors would like to thank Dan Wing for his guidance in the
early discussions that initiated this work. We also thank Peng Sun,
Jie Hu, Qiong Sun, Lizhong Jin, Alain Durand, Dean Cheng, Behcet
Sarikaya, Tina Tsou, Rajiv Asati, Xiaohong Deng, and Stig Venaas for
their valuable comments.
Many thanks to Ian Farrer for the review.
Thanks to Zhen Cao, Tim Chown, Francis Dupont, Jouni Korhonen, and
Stig Venaas for the directorates review.
<span class="grey">Boucadair, et al. Standards Track [Page 22]</span><span id="page-23" ></span>
<span class="grey"><a href="./rfc8114">RFC 8114</a> IPv4 over IPv6 Multicast March 2017</span>
Authors' Addresses
Mohamed Boucadair
Orange
Rennes 35000
France
Email: [email protected]
Chao Qin
Cisco
Shanghai
China
Email: [email protected]
Christian Jacquenet
Orange
Rennes 35000
France
Email: [email protected]
Yiu L. Lee
Comcast
United States of America
Email: [email protected]
URI: <a href="http://www.comcast.com">http://www.comcast.com</a>
Qian Wang
China Telecom
China
Phone: +86 10 58502462
Email: [email protected]
Boucadair, et al. Standards Track [Page 23]
Annotations
Select text to annotate