| 1 |
<pre>Internet Engineering Task Force (IETF) T. Schmidt |
| 2 |
Request for Comments: 6224 HAW Hamburg |
| 3 |
Category: Informational M. Waehlisch |
| 4 |
ISSN: 2070-1721 link-lab & FU Berlin |
| 5 |
S. Krishnan |
| 6 |
Ericsson |
| 7 |
April 2011 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">Base Deployment for Multicast Listener Support</span> |
| 11 |
<span class="h1">in Proxy Mobile IPv6 (PMIPv6) Domains</span> |
| 12 |
|
| 13 |
Abstract |
| 14 |
|
| 15 |
This document describes deployment options for activating multicast |
| 16 |
listener functions in Proxy Mobile IPv6 domains without modifying |
| 17 |
mobility and multicast protocol standards. Similar to home agents in |
| 18 |
Mobile IPv6, Local Mobility Anchors of Proxy Mobile IPv6 serve as |
| 19 |
multicast subscription anchor points, while Mobile Access Gateways |
| 20 |
provide Multicast Listener Discovery (MLD) proxy functions. In this |
| 21 |
scenario, mobile nodes remain agnostic of multicast mobility |
| 22 |
operations. Support for mobile multicast senders is outside the |
| 23 |
scope of this document. |
| 24 |
|
| 25 |
Status of This Memo |
| 26 |
|
| 27 |
This document is not an Internet Standards Track specification; it is |
| 28 |
published for informational purposes. |
| 29 |
|
| 30 |
This document is a product of the Internet Engineering Task Force |
| 31 |
(IETF). It represents the consensus of the IETF community. It has |
| 32 |
received public review and has been approved for publication by the |
| 33 |
Internet Engineering Steering Group (IESG). Not all documents |
| 34 |
approved by the IESG are a candidate for any level of Internet |
| 35 |
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 36 |
|
| 37 |
Information about the current status of this document, any errata, |
| 38 |
and how to provide feedback on it may be obtained at |
| 39 |
<a href="http://www.rfc-editor.org/info/rfc6224">http://www.rfc-editor.org/info/rfc6224</a>. |
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Schmidt, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2011 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
Table of Contents |
| 73 |
|
| 74 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 75 |
<a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 76 |
<a href="#section-3">3</a>. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 77 |
<a href="#section-4">4</a>. Deployment Details . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 78 |
<a href="#section-4.1">4.1</a>. Operations of the Mobile Node . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 79 |
<a href="#section-4.2">4.2</a>. Operations of the Mobile Access Gateway . . . . . . . . . <a href="#page-8">8</a> |
| 80 |
<a href="#section-4.3">4.3</a>. Operations of the Local Mobility Anchor . . . . . . . . . <a href="#page-10">10</a> |
| 81 |
<a href="#section-4.4">4.4</a>. IPv4 Support . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 82 |
<a href="#section-4.5">4.5</a>. Multihoming Support . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 83 |
<a href="#section-4.6">4.6</a>. Multicast Availability throughout the Access Network . . . <a href="#page-12">12</a> |
| 84 |
<a href="#section-4.7">4.7</a>. A Note on Explicit Tracking . . . . . . . . . . . . . . . <a href="#page-12">12</a> |
| 85 |
<a href="#section-5">5</a>. Message Source and Destination Address . . . . . . . . . . . . <a href="#page-13">13</a> |
| 86 |
<a href="#section-5.1">5.1</a>. Query . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 87 |
<a href="#section-5.2">5.2</a>. Report/Done . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 88 |
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 89 |
<a href="#section-7">7</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a> |
| 90 |
<a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a> |
| 91 |
<a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a> |
| 92 |
<a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a> |
| 93 |
<a href="#appendix-A">Appendix A</a>. Initial MLD Queries on Upcoming Links . . . . . . . . <a href="#page-16">16</a> |
| 94 |
<a href="#appendix-B">Appendix B</a>. State of IGMP/MLD Proxy Implementations . . . . . . . <a href="#page-16">16</a> |
| 95 |
<a href="#appendix-C">Appendix C</a>. Comparative Evaluation of Different Approaches . . . <a href="#page-17">17</a> |
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Schmidt, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
Proxy Mobile IPv6 (PMIPv6) [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] extends Mobile IPv6 (MIPv6) |
| 116 |
[<a href="./rfc3775" title=""Mobility Support in IPv6"">RFC3775</a>] by network-based management functions that enable IP |
| 117 |
mobility for a host without requiring its participation in any |
| 118 |
mobility-related signaling. Additional network entities, called the |
| 119 |
Local Mobility Anchor (LMA) and Mobile Access Gateways (MAGs), are |
| 120 |
responsible for managing IP mobility on behalf of the mobile node |
| 121 |
(MN). |
| 122 |
|
| 123 |
With these entities in place, the mobile node experiences an |
| 124 |
exceptional access topology towards the static Internet in the sense |
| 125 |
that the MAG introduces a routing hop in situations where the LMA |
| 126 |
architecturally acts as the next hop (or designated) router for the |
| 127 |
MN. In the particular case of multicast communication, group |
| 128 |
membership management, as signaled by the Multicast Listener |
| 129 |
Discovery (MLD) protocol [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>] [<a href="./rfc2710" title=""Multicast Listener Discovery (MLD) for IPv6"">RFC2710</a>], requires dedicated |
| 130 |
treatment at the network side. |
| 131 |
|
| 132 |
Multicast routing functions need to be placed carefully within the |
| 133 |
PMIPv6 domain in order to augment unicast transmission with group |
| 134 |
communication services. [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] does not explicitly address |
| 135 |
multicast communication. Bidirectional home tunneling, the minimal |
| 136 |
multicast support arranged by MIPv6, cannot be directly transferred |
| 137 |
to network-based management scenarios, since a mobility-unaware node |
| 138 |
will not initiate such a tunnel after movement. Consequently, even |
| 139 |
minimal multicast listener support in PMIPv6 domains requires an |
| 140 |
explicit deployment of additional functions. |
| 141 |
|
| 142 |
This document describes options for deploying multicast listener |
| 143 |
functions in Proxy Mobile IPv6 domains without modifying mobility and |
| 144 |
multicast protocol standards. Similar to home agents in Mobile IPv6, |
| 145 |
PMIPv6 Local Mobility Anchors serve as multicast subscription anchor |
| 146 |
points, while Mobile Access Gateways provide MLD proxy functions. In |
| 147 |
this scenario, mobile nodes remain agnostic of multicast mobility |
| 148 |
operations. This document does not address specific optimizations |
| 149 |
and efficiency improvements of multicast routing for network-based |
| 150 |
mobility discussed in [<a href="./rfc5757" title=""Multicast Mobility in Mobile IP Version 6 (MIPv6): Problem Statement and Brief Survey"">RFC5757</a>], as such solutions would require |
| 151 |
changes to the base PMIPv6 protocol [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>]. Support for mobile |
| 152 |
multicast senders is also outside the scope of this document. |
| 153 |
|
| 154 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 155 |
|
| 156 |
This document uses the terminology as defined for the mobility |
| 157 |
protocols [<a href="./rfc3775" title=""Mobility Support in IPv6"">RFC3775</a>], [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>], and [<a href="./rfc5844" title=""IPv4 Support for Proxy Mobile IPv6"">RFC5844</a>], as well as the |
| 158 |
multicast edge related protocols [<a href="./rfc3376" title=""Internet Group Management Protocol, Version 3"">RFC3376</a>], [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>], and [<a href="./rfc4605" title=""Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("">RFC4605</a>]. |
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Schmidt, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span> |
| 170 |
|
| 171 |
The reference scenario for multicast deployment in Proxy Mobile IPv6 |
| 172 |
domains is illustrated in Figure 1. Below, LMAA and MN-HNP are the |
| 173 |
LMA Address and Mobile Node's Home Network Prefix as defined in |
| 174 |
[<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>]. |
| 175 |
|
| 176 |
+-------------+ |
| 177 |
| Content | |
| 178 |
| Source | |
| 179 |
+-------------+ |
| 180 |
| |
| 181 |
*** *** *** *** |
| 182 |
* ** ** ** * |
| 183 |
* * |
| 184 |
* Fixed Internet * |
| 185 |
* * |
| 186 |
* ** ** ** * |
| 187 |
*** *** *** *** |
| 188 |
/ \ |
| 189 |
+----+ +----+ |
| 190 |
|LMA1| |LMA2| Multicast Anchor |
| 191 |
+----+ +----+ |
| 192 |
LMAA1 | | LMAA2 |
| 193 |
| | |
| 194 |
\\ //\\ |
| 195 |
\\ // \\ |
| 196 |
\\ // \\ Unicast Tunnel |
| 197 |
\\ // \\ |
| 198 |
\\ // \\ |
| 199 |
\\ // \\ |
| 200 |
Proxy-CoA1 || || Proxy-CoA2 |
| 201 |
+----+ +----+ |
| 202 |
|MAG1| |MAG2| MLD Proxy |
| 203 |
+----+ +----+ |
| 204 |
| | | |
| 205 |
MN-HNP1 | | MN-HNP2 | MN-HNP3 |
| 206 |
MN1 MN2 MN3 |
| 207 |
|
| 208 |
Figure 1: Reference Network for Multicast Deployment in PMIPv6 |
| 209 |
|
| 210 |
An MN in a PMIPv6 domain will decide on multicast group membership |
| 211 |
management completely independent of its current mobility conditions. |
| 212 |
It will submit MLD Report and Done messages, based on application |
| 213 |
triggers, using its link-local source address and multicast |
| 214 |
destination addresses according to [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>] or [<a href="./rfc2710" title=""Multicast Listener Discovery (MLD) for IPv6"">RFC2710</a>]. These |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Schmidt, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 223 |
|
| 224 |
|
| 225 |
link-local signaling messages will arrive at the currently active MAG |
| 226 |
via one of its downstream local (wireless) links. A multicast- |
| 227 |
unaware MAG would simply discard these MLD messages. |
| 228 |
|
| 229 |
To facilitate multicast in a PMIPv6 domain, an MLD proxy function |
| 230 |
[<a href="./rfc4605" title=""Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("">RFC4605</a>] needs to be deployed on the MAG that selects the tunnel |
| 231 |
interface corresponding to the MN's LMA for its upstream interface |
| 232 |
(cf., <a href="./rfc5213#section-6">Section 6 of [RFC5213]</a>). Thereby, each MAG-to-LMA tunnel |
| 233 |
interface defines an MLD proxy domain at the MAG, and it contains all |
| 234 |
downstream links to MNs that share this specific LMA. According to |
| 235 |
standard proxy operations, MLD Report messages will be aggregated and |
| 236 |
then forwarded up the tunnel interface to the MN's corresponding LMA. |
| 237 |
|
| 238 |
Serving as the designated multicast router or an additional MLD |
| 239 |
proxy, the LMA will transpose any MLD message from a MAG into the |
| 240 |
multicast routing infrastructure. Correspondingly, the LMA will |
| 241 |
create appropriate multicast forwarding states at its tunnel |
| 242 |
interface. Traffic of the subscribed groups will arrive at the LMA, |
| 243 |
and the LMA will forward this traffic according to its group/source |
| 244 |
states. In addition, the LMA will act as an MLD querier, seeing its |
| 245 |
downstream tunnel interfaces as multicast-enabled links. |
| 246 |
|
| 247 |
At the MAG, MLD queries and multicast data will arrive on the |
| 248 |
(tunnel) interface that is assigned to a group of access links as |
| 249 |
identified by its Binding Update List (cf., <a href="./rfc5213#section-6.1">Section 6.1 of |
| 250 |
[RFC5213]</a>). As specified for MLD proxies, the MAG will forward |
| 251 |
multicast traffic and initiate related signaling down the appropriate |
| 252 |
access links to the MNs. Hence, all multicast-related signaling and |
| 253 |
the data traffic will transparently flow from the LMA to the MN on an |
| 254 |
LMA-specific tree, which is shared among the multicast sources. |
| 255 |
|
| 256 |
In case of a handover, the MN (unaware of IP mobility) will not send |
| 257 |
unsolicited MLD reports. Instead, the MAG is required to maintain |
| 258 |
group memberships in the following way. On observing a new MN on a |
| 259 |
downstream access link, the MAG sends a MLD General Query. Based on |
| 260 |
its outcome and the multicast group states previously maintained at |
| 261 |
the MAG, a corresponding Report will be sent to the LMA aggregating |
| 262 |
group membership states according to the proxy function. Additional |
| 263 |
Reports can be omitted when the previously established multicast |
| 264 |
forwarding states at the new MAG already cover the subscriptions of |
| 265 |
the MN. |
| 266 |
|
| 267 |
In summary, the following steps are executed on handover: |
| 268 |
|
| 269 |
1. The MAG-MN link comes up and the MAG discovers the new MN. |
| 270 |
|
| 271 |
2. Unicast address configuration and PMIPv6 binding are performed |
| 272 |
after the MAG determines the corresponding LMA. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Schmidt, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 279 |
|
| 280 |
|
| 281 |
3. Following IPv6 address configuration, the MAG should send an |
| 282 |
(early) MLD General Query to the new downstream link as part of |
| 283 |
its standard multicast-enabled router operations. |
| 284 |
|
| 285 |
4. The MAG should determine whether the MN is admissible to |
| 286 |
multicast services; if it's not, then stop here. |
| 287 |
|
| 288 |
5. The MAG adds the new downstream link to the MLD proxy instance |
| 289 |
with up-link to the corresponding LMA. |
| 290 |
|
| 291 |
6. The corresponding proxy instance triggers an MLD General Query on |
| 292 |
the new downstream link. |
| 293 |
|
| 294 |
7. The MN Membership Reports arrive at the MAG, in response either |
| 295 |
to the early query or to the query sent by the proxy instance. |
| 296 |
|
| 297 |
8. The Proxy processes the MLD Report, updates states, and reports |
| 298 |
upstream if necessary. |
| 299 |
|
| 300 |
After Re-Binding, the LMA is not required to issue a MLD General |
| 301 |
Query on the tunnel link to refresh forwarding states. Multicast |
| 302 |
state updates should be triggered by the MAG, which aggregates |
| 303 |
subscriptions of all its MNs (see the call flow in Figure 2). |
| 304 |
|
| 305 |
|
| 306 |
|
| 307 |
|
| 308 |
|
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Schmidt, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 335 |
|
| 336 |
|
| 337 |
MN1 MAG1 MN2 MAG2 LMA |
| 338 |
| | | | | |
| 339 |
| Join(G) | | | | |
| 340 |
+--------------->| | | | |
| 341 |
| | Join(G) | | | |
| 342 |
| |<---------------+ | | |
| 343 |
| | | | | |
| 344 |
| | Aggregated Join(G) | | |
| 345 |
| +================================================>| |
| 346 |
| | | | | |
| 347 |
| | Mcast Data | | | |
| 348 |
| |<================================================+ |
| 349 |
| | | | | |
| 350 |
| Mcast Data | Mcast Data | | | |
| 351 |
|<---------------+--------------->| | | |
| 352 |
| | | | | |
| 353 |
| < Movement of MN 2 to MAG2 & PMIP Binding Update > | |
| 354 |
| | | | | |
| 355 |
| | |--- Rtr Sol -->| | |
| 356 |
| | |<-- Rtr Adv ---| | |
| 357 |
| | | | | |
| 358 |
| | | MLD Query | | |
| 359 |
| | |<--------------+ | |
| 360 |
| | | | | |
| 361 |
| | | Join(G) | | |
| 362 |
| | +-------------->| | |
| 363 |
| | | Aggregated Join(G) |
| 364 |
| | | +===============>| |
| 365 |
| | | | | |
| 366 |
| | Mcast Data | | | |
| 367 |
| |<================================================+ |
| 368 |
| | | | Mcast Data | |
| 369 |
| | | |<===============+ |
| 370 |
| Mcast Data | | | | |
| 371 |
|<---------------+ | Mcast Data | | |
| 372 |
| | |<--------------+ | |
| 373 |
| | | | | |
| 374 |
|
| 375 |
Figure 2: Call Flow of Multicast-Enabled PMIP |
| 376 |
with "MLD Membership Report" Abbreviated by "Join" |
| 377 |
|
| 378 |
These multicast deployment considerations likewise apply for mobile |
| 379 |
nodes that operate with their IPv4 stack enabled in a PMIPv6 domain. |
| 380 |
PMIPv6 can provide IPv4 home address mobility support [<a href="./rfc5844" title=""IPv4 Support for Proxy Mobile IPv6"">RFC5844</a>]. |
| 381 |
Such mobile nodes will use IGMP [<a href="./rfc2236" title=""Internet Group Management Protocol, Version 2"">RFC2236</a>] [<a href="./rfc3376" title=""Internet Group Management Protocol, Version 3"">RFC3376</a>] signaling for |
| 382 |
multicast, which is handled by an IGMP proxy function at the MAG in |
| 383 |
an analogous way. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Schmidt, et al. Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 391 |
|
| 392 |
|
| 393 |
Following these deployment steps, multicast management transparently |
| 394 |
interoperates with PMIPv6. It is worth noting that MNs -- while |
| 395 |
being attached to the same MAG, but associated with different LMAs -- |
| 396 |
can subscribe to the same multicast group. Thereby, data could be |
| 397 |
distributed redundantly in the network and duplicate traffic could |
| 398 |
arrive at a MAG. Additionally, in a point-to-point wireless link |
| 399 |
model, a MAG might be forced to transmit the same data over one |
| 400 |
wireless domain to different MNs. However, multicast traffic |
| 401 |
arriving at one interface of the MN will always remain unique, i.e., |
| 402 |
the mobile multicast distribution system will never cause duplicate |
| 403 |
packets arriving at an MN (see <a href="#appendix-C">Appendix C</a> for further |
| 404 |
considerations). |
| 405 |
|
| 406 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Deployment Details</span> |
| 407 |
|
| 408 |
Multicast activation in a PMIPv6 domain requires to deploy general |
| 409 |
multicast functions at PMIPv6 routers and to define their interaction |
| 410 |
with the PMIPv6 protocol in the following way. |
| 411 |
|
| 412 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Operations of the Mobile Node</span> |
| 413 |
|
| 414 |
A mobile node willing to manage multicast traffic will join, |
| 415 |
maintain, and leave groups as if located in the fixed Internet. No |
| 416 |
specific mobility actions nor implementations are required at the MN. |
| 417 |
|
| 418 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Operations of the Mobile Access Gateway</span> |
| 419 |
|
| 420 |
A Mobile Access Gateway is required to assist in MLD signaling and |
| 421 |
data forwarding between the MNs that it serves and the corresponding |
| 422 |
LMAs associated to each MN. It therefore needs to implement an |
| 423 |
instance of the MLD proxy function [<a href="./rfc4605" title=""Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("">RFC4605</a>] for each upstream tunnel |
| 424 |
interface that has been established with an LMA. The MAG decides on |
| 425 |
the mapping of downstream links to a proxy instance (and hence an |
| 426 |
upstream link to an LMA) based on the regular Binding Update List as |
| 427 |
maintained by PMIPv6 standard operations (cf., <a href="./rfc5213#section-6.1">Section 6.1 of |
| 428 |
[RFC5213]</a>). As links connecting MNs and MAGs change under mobility, |
| 429 |
MLD proxies at MAGs must be able to dynamically add and remove |
| 430 |
downstream interfaces in their configurations. |
| 431 |
|
| 432 |
On the reception of MLD reports from an MN, the MAG must identify the |
| 433 |
corresponding proxy instance from the incoming interface and perform |
| 434 |
regular MLD proxy operations: it will insert/update/remove multicast |
| 435 |
forwarding state on the incoming interface and will merge state |
| 436 |
updates into the MLD proxy membership database. It will then send an |
| 437 |
aggregated Report via the upstream tunnel to the LMA when the |
| 438 |
membership database (cf., <a href="./rfc4605#section-4.1">Section 4.1 of [RFC4605]</a>) changes. |
| 439 |
Conversely, on the reception of MLD queries, the MAG proxy instance |
| 440 |
will answer the Queries on behalf of all active downstream receivers |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Schmidt, et al. Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 447 |
|
| 448 |
|
| 449 |
maintained in its membership database. Queries sent by the LMA do |
| 450 |
not force the MAG to trigger corresponding messages immediately |
| 451 |
towards MNs. Multicast traffic arriving at the MAG on an upstream |
| 452 |
interface will be forwarded according to the group-specific or |
| 453 |
source-specific forwarding states as acquired for each downstream |
| 454 |
interface within the MLD proxy instance. At this stage, it is |
| 455 |
important to note that IGMP/MLD proxy implementations capable of |
| 456 |
multiple instances are expected to closely follow the specifications |
| 457 |
of <a href="./rfc4605#section-4.2">Section 4.2 in [RFC4605]</a>, i.e., treat proxy instances in isolation |
| 458 |
of each other while forwarding. In providing isolated proxy |
| 459 |
instances, the MAG will uniquely serve its downstream links with |
| 460 |
exactly the data that belong to whatever group is subscribed on the |
| 461 |
particular interface. |
| 462 |
|
| 463 |
After a handover, the MAG will continue to manage upstream tunnels |
| 464 |
and downstream interfaces as specified in the PMIPv6 specification. |
| 465 |
It must dynamically associate new access links to proxy instances |
| 466 |
that include the upstream connection to the corresponding LMA. The |
| 467 |
MAG detects the arrival of a new MN by receiving a router |
| 468 |
solicitation message and by an upcoming link. To learn about |
| 469 |
multicast groups subscribed by a newly attaching MN, the MAG should |
| 470 |
send a General Query to the MN's link. Querying an upcoming |
| 471 |
interface is a standard operation of MLD queriers (see <a href="#appendix-A">Appendix A</a>) |
| 472 |
and is performed immediately after address configuration. In |
| 473 |
addition, an MLD query should be initiated by the proxy instance, as |
| 474 |
soon as a new interface has been configured for downstream. In case |
| 475 |
the access link between MN and MAG goes down, interface-specific |
| 476 |
multicast states change. Both cases may alter the composition of the |
| 477 |
membership database and this will trigger corresponding Reports |
| 478 |
towards the LMA. Note that the actual observable state depends on |
| 479 |
the access link model in use. |
| 480 |
|
| 481 |
An MN may be unable to answer MAG multicast membership queries due to |
| 482 |
handover procedures, or its report may arrive before the MAG has |
| 483 |
configured its link as the proxy downstream interface. Such |
| 484 |
occurrences are equivalent to a General Query loss. To prevent |
| 485 |
erroneous query timeouts at the MAG, MLD parameters should be |
| 486 |
carefully adjusted to the mobility regime. In particular, MLD timers |
| 487 |
and the Robustness Variable (see <a href="./rfc3810#section-9">Section 9 of [RFC3810]</a>) should be |
| 488 |
chosen to be compliant with the time scale of handover operations and |
| 489 |
proxy configurations in the PMIPv6 domain. |
| 490 |
|
| 491 |
In proceeding this way, the MAG is able to aggregate multicast |
| 492 |
subscriptions for each of its MLD proxy instances. However, this |
| 493 |
deployment approach does not prevent multiple identical streams |
| 494 |
arriving from different LMA upstream interfaces. Furthermore, a |
| 495 |
multipoint channel forwarding into the wireless domain is prevented |
| 496 |
by the point-to-point link model in use. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Schmidt, et al. Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Operations of the Local Mobility Anchor</span> |
| 506 |
|
| 507 |
For any MN, the Local Mobility Anchor acts as the persistent home |
| 508 |
agent and at the same time as the default multicast querier for the |
| 509 |
corresponding MAG. It implements the function of the designated |
| 510 |
multicast router or a further MLD proxy. According to MLD reports |
| 511 |
received from a MAG (on behalf of the MNs), the LMA establishes/ |
| 512 |
maintains/removes group-/source-specific multicast forwarding states |
| 513 |
at its corresponding downstream tunnel interfaces. At the same time, |
| 514 |
it procures for aggregated multicast membership maintenance at its |
| 515 |
upstream interface. Based on the multicast-transparent operations of |
| 516 |
the MAGs, the LMA treats its tunnel interfaces as multicast-enabled |
| 517 |
downstream links, serving zero to many listening nodes. Multicast |
| 518 |
traffic arriving at the LMA is transparently forwarded according to |
| 519 |
its multicast forwarding information base. |
| 520 |
|
| 521 |
After a handover, the LMA will receive Binding De-Registrations and |
| 522 |
Binding Lifetime Extensions that will cause a re-mapping of home |
| 523 |
network prefix(es) to a new Proxy-CoA in its Binding Cache (see |
| 524 |
<a href="./rfc5213#section-5.3">Section 5.3 of [RFC5213]</a>). The multicast forwarding states require |
| 525 |
updating, as well, if the MN within an MLD proxy domain is the only |
| 526 |
receiver of a multicast group. Two different cases need to be |
| 527 |
considered: |
| 528 |
|
| 529 |
1. The mobile node is the only receiver of a group behind the |
| 530 |
interface at which a De-Registration was received: the membership |
| 531 |
database of the MAG changes, which will trigger a Report/Done |
| 532 |
sent via the MAG-to-LMA interface to remove this group. The LMA |
| 533 |
thus terminates multicast forwarding. |
| 534 |
|
| 535 |
2. The mobile node is the only receiver of a group behind the |
| 536 |
interface at which a Lifetime Extension was received: the |
| 537 |
membership database of the MAG changes, which will trigger a |
| 538 |
Report sent via the MAG-to-LMA interface to add this group. The |
| 539 |
LMA thus starts multicast distribution. |
| 540 |
|
| 541 |
In proceeding this way, each LMA will provide transparent multicast |
| 542 |
support for the group of MNs it serves. It will perform traffic |
| 543 |
aggregation at the MN-group level and will assure that multicast data |
| 544 |
streams are uniquely forwarded per individual LMA-to-MAG tunnel. |
| 545 |
|
| 546 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. IPv4 Support</span> |
| 547 |
|
| 548 |
An MN in a PMIPv6 domain may use an IPv4 address transparently for |
| 549 |
communication as specified in [<a href="./rfc5844" title=""IPv4 Support for Proxy Mobile IPv6"">RFC5844</a>]. For this purpose, LMAs can |
| 550 |
register IPv4-Proxy-CoAs in its Binding Caches, and MAGs can provide |
| 551 |
IPv4 support in access networks. Correspondingly, multicast |
| 552 |
membership management will be performed by the MN using IGMP. For |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Schmidt, et al. Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 559 |
|
| 560 |
|
| 561 |
multicast support on the network side, an IGMP proxy function needs |
| 562 |
to be deployed at MAGs in exactly the same way as for IPv6. |
| 563 |
[<a href="./rfc4605" title=""Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("">RFC4605</a>] defines IGMP proxy behavior in full agreement with IPv6/ |
| 564 |
MLD. Thus, IPv4 support can be transparently provided following the |
| 565 |
obvious deployment analogy. |
| 566 |
|
| 567 |
For a dual-stack IPv4/IPv6 access network, the MAG proxy instances |
| 568 |
should choose multicast signaling according to address configurations |
| 569 |
on the link, but may submit IGMP and MLD queries in parallel, if |
| 570 |
needed. It should further be noted that the infrastructure cannot |
| 571 |
identify two data streams as identical when distributed via an IPv4 |
| 572 |
and IPv6 multicast group. Thus, duplicate data may be forwarded on a |
| 573 |
heterogeneous network layer. |
| 574 |
|
| 575 |
A particular note is worth giving the scenario of [<a href="./rfc5845" title=""Generic Routing Encapsulation (GRE) Key Option for Proxy Mobile IPv6"">RFC5845</a>] in which |
| 576 |
overlapping private address spaces of different operators can be |
| 577 |
hosted in a PMIP domain by using Generic Routing Encapsulation (GRE) |
| 578 |
with key identification. This scenario implies that unicast |
| 579 |
communication in the MAG-LMA tunnel can be individually identified |
| 580 |
per MN by the GRE keys. This scenario still does not impose any |
| 581 |
special treatment of multicast communication for the following |
| 582 |
reasons. |
| 583 |
|
| 584 |
MLD/IGMP signaling between MNs and the MAG is on point-to-point links |
| 585 |
(identical to unicast). Aggregated MLD/IGMP signaling between the |
| 586 |
MAG proxy instance and the LMA remains link-local between the routers |
| 587 |
and independent of any individual MN. So the MAG-proxy and the LMA |
| 588 |
should not use GRE key identifiers, but plain GRE to exchange MLD |
| 589 |
queries and reports. Similarly, multicast traffic sent from an LMA |
| 590 |
to MAGs proceeds as router-to-router forwarding according to the |
| 591 |
multicast forwarding information base (MFIB) of the LMA and |
| 592 |
independent of MN's unicast addresses, while the MAG proxy instance |
| 593 |
distributes multicast data down the point-to-point links (interfaces) |
| 594 |
according to its own MFIB, independent of MN's IP addresses. |
| 595 |
|
| 596 |
It remains an open issue how communication proceeds in a multi- |
| 597 |
operator scenario, i.e., from which network the LMA pulls multicast |
| 598 |
traffic. This could be any mobility Operator itself, or a third |
| 599 |
party. However, this backbone routing in general is out of scope of |
| 600 |
the document, and most likely a matter of contracts. |
| 601 |
|
| 602 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Multihoming Support</span> |
| 603 |
|
| 604 |
An MN can connect to a PMIPv6 domain through multiple interfaces and |
| 605 |
experience transparent unicast handovers at all interfaces (cf., |
| 606 |
<a href="./rfc5213#section-5.4">Section 5.4 of [RFC5213]</a>). In such simultaneous access scenarios, it |
| 607 |
can autonomously assign multicast channel subscriptions to individual |
| 608 |
interfaces (see [<a href="./rfc5757" title=""Multicast Mobility in Mobile IP Version 6 (MIPv6): Problem Statement and Brief Survey"">RFC5757</a>] for additional details). While doing so, |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Schmidt, et al. Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 615 |
|
| 616 |
|
| 617 |
multicast mobility operations described in this document will |
| 618 |
transparently preserve the association of channels to interfaces in |
| 619 |
the following way. |
| 620 |
|
| 621 |
Multicast listener states are kept per interface in the MLD state |
| 622 |
table. An MN will answer to an MLD General Query received on a |
| 623 |
specific (re-attaching) interface according to the specific |
| 624 |
interface's state table. Thereafter, multicast forwarding is resumed |
| 625 |
for channels identical to those under subscription prior to handover. |
| 626 |
Consequently, an MN in a PMIPv6 domain may use multiple interfaces to |
| 627 |
facilitate load balancing or redundancy, but cannot follow a 'make- |
| 628 |
before-break' approach to service continuation on handovers. |
| 629 |
|
| 630 |
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. Multicast Availability throughout the Access Network</span> |
| 631 |
|
| 632 |
There may be deployment scenarios where multicast services are |
| 633 |
available throughout the access network, independent of the PMIPv6 |
| 634 |
infrastructure. Direct multicast access at MAGs may be supported |
| 635 |
through native multicast routing within a flat access network that |
| 636 |
includes a multicast router, via dedicated (tunnel or VPN) links |
| 637 |
between MAGs and designated multicast routers, or by deploying |
| 638 |
Automatic Multicast Tunneling (AMT) [<a href="#ref-AUTO-MULTICAST">AUTO-MULTICAST</a>]. |
| 639 |
|
| 640 |
Multicast deployment can be simplified in these scenarios. A single |
| 641 |
proxy instance at MAGs with up-link to the multicast cloud, for |
| 642 |
instance, could serve group communication purposes. MAGs could |
| 643 |
operate as general multicast routers or AMT gateways as well. |
| 644 |
|
| 645 |
Common to these solutions is that mobility management is covered by |
| 646 |
the dynamics of multicast routing, as initially foreseen in the |
| 647 |
Remote Subscription approach, i.e., join via a local multicast router |
| 648 |
as sketched in [<a href="./rfc3775" title=""Mobility Support in IPv6"">RFC3775</a>]. Care must be taken to avoid avalanche |
| 649 |
problems or service disruptions due to tardy multicast routing |
| 650 |
operations and to adapt to different link-layer technologies |
| 651 |
[<a href="./rfc5757" title=""Multicast Mobility in Mobile IP Version 6 (MIPv6): Problem Statement and Brief Survey"">RFC5757</a>]. The different possible approaches should be carefully |
| 652 |
investigated beyond the initial sketch in <a href="#appendix-C">Appendix C</a>. Such work is |
| 653 |
beyond the scope of this document. |
| 654 |
|
| 655 |
<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. A Note on Explicit Tracking</span> |
| 656 |
|
| 657 |
An IGMPv3/MLDv2 Querier may operate in combination with explicit |
| 658 |
tracking as described in <a href="./rfc3376#appendix-A.2">Appendix A.2 of [RFC3376]</a>, or <a href="./rfc3810#appendix-A.2">Appendix A.2 |
| 659 |
of [RFC3810]</a>. This mechanism allows routers to monitor each |
| 660 |
multicast receiver individually. Even though this procedure is not |
| 661 |
standardized yet, it is widely implemented by vendors as it supports |
| 662 |
faster leave latencies and reduced signaling. |
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Schmidt, et al. Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 671 |
|
| 672 |
|
| 673 |
Enabling explicit tracking on downstream interfaces of the LMA and |
| 674 |
MAG would track a single MAG and MN respectively per interface. It |
| 675 |
may be used to preserve bandwidth on the MAG-MN link. |
| 676 |
|
| 677 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Message Source and Destination Address</span> |
| 678 |
|
| 679 |
This section describes source and destination addresses of MLD |
| 680 |
messages and encapsulating outer headers when deployed in the PMIPv6 |
| 681 |
domain. This overview is for clarification purposes only and does |
| 682 |
not define a behavior different from referenced standards in any way. |
| 683 |
|
| 684 |
The interface identifier A-B denotes an interface on node A, which is |
| 685 |
connected to node B. This includes tunnel interfaces. Destination |
| 686 |
addresses for MLD/IGMP messages shall be as specified in <a href="./rfc2710#section-8">Section 8 of |
| 687 |
[RFC2710]</a> for MLDv1, and Sections <a href="#section-5.1.15">5.1.15</a> and <a href="#section-5.2.14">5.2.14</a> of [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>] for |
| 688 |
MLDv2. |
| 689 |
|
| 690 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Query</span> |
| 691 |
|
| 692 |
+===========+================+======================+==========+ |
| 693 |
| Interface | Source Address | Destination Address | Header | |
| 694 |
+===========+================+======================+==========+ |
| 695 |
| | LMAA | Proxy-CoA | outer | |
| 696 |
+ LMA-MAG +----------------+----------------------+----------+ |
| 697 |
| | LMA-link-local | [<a href="./rfc2710" title=""Multicast Listener Discovery (MLD) for IPv6"">RFC2710</a>], [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>] | inner | |
| 698 |
+-----------+----------------+----------------------+----------+ |
| 699 |
| MAG-MN | MAG-link-local | [<a href="./rfc2710" title=""Multicast Listener Discovery (MLD) for IPv6"">RFC2710</a>], [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>] | -- | |
| 700 |
+-----------+----------------+----------------------+----------+ |
| 701 |
|
| 702 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Report/Done</span> |
| 703 |
|
| 704 |
+===========+================+======================+==========+ |
| 705 |
| Interface | Source Address | Destination Address | Header | |
| 706 |
+===========+================+======================+==========+ |
| 707 |
| MN-MAG | MN-link-local | [<a href="./rfc2710" title=""Multicast Listener Discovery (MLD) for IPv6"">RFC2710</a>], [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>] | -- | |
| 708 |
+-----------+----------------+----------------------+----------+ |
| 709 |
| | Proxy-CoA | LMAA | outer | |
| 710 |
+ MAG-LMA +----------------+----------------------+----------+ |
| 711 |
| | MAG-link-local | [<a href="./rfc2710" title=""Multicast Listener Discovery (MLD) for IPv6"">RFC2710</a>], [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>] | inner | |
| 712 |
+-----------+----------------+----------------------+----------+ |
| 713 |
|
| 714 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 715 |
|
| 716 |
This document does not introduce additional messages or novel |
| 717 |
protocol operations. Consequently, no additional threats are |
| 718 |
introduced by this document beyond those identified as security |
| 719 |
concerns of [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>], [<a href="./rfc4605" title=""Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("">RFC4605</a>], [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>], and [<a href="./rfc5844" title=""IPv4 Support for Proxy Mobile IPv6"">RFC5844</a>]. |
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Schmidt, et al. Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 727 |
|
| 728 |
|
| 729 |
However, particular attention should be paid to implications of |
| 730 |
combining multicast and mobility management at network entities. As |
| 731 |
this specification allows mobile nodes to initiate the creation of |
| 732 |
multicast forwarding states at MAGs and LMAs while changing |
| 733 |
attachments, threats of resource exhaustion at PMIP routers and |
| 734 |
access networks arrive from rapid state changes, as well as from |
| 735 |
high-volume data streams routed into access networks of limited |
| 736 |
capacities. In addition to proper authorization checks of MNs, rate |
| 737 |
controls at replicators may be required to protect the agents and the |
| 738 |
downstream networks. In particular, MLD proxy implementations at |
| 739 |
MAGs should carefully procure automatic multicast state extinction on |
| 740 |
the departure of MNs, as mobile multicast listeners in the PMIPv6 |
| 741 |
domain will not actively terminate group membership prior to |
| 742 |
departure. |
| 743 |
|
| 744 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span> |
| 745 |
|
| 746 |
This memo follows initial requirements work presented in "Multicast |
| 747 |
Support Requirements for Proxy Mobile IPv6" (July 2009), and is the |
| 748 |
outcome of extensive previous discussions and a follow-up of several |
| 749 |
initial documents on the subject. The authors would like to thank |
| 750 |
(in alphabetical order) Jari Arkko, Luis M. Contreras, Greg Daley, |
| 751 |
Gorry Fairhurst, Dirk von Hugo, Liu Hui, Seil Jeon, Jouni Korhonen, |
| 752 |
Guang Lu, Sebastian Meiling, Akbar Rahman, Imed Romdhani, Behcet |
| 753 |
Sarikaya, Pierrick Seite, Stig Venaas, and Juan Carlos Zuniga for |
| 754 |
advice, help, and reviews of the document. Funding by the German |
| 755 |
Federal Ministry of Education and Research within the G-LAB |
| 756 |
Initiative is gratefully acknowledged. |
| 757 |
|
| 758 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 759 |
|
| 760 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span> |
| 761 |
|
| 762 |
[<a id="ref-RFC2710">RFC2710</a>] Deering, S., Fenner, W., and B. Haberman, "Multicast |
| 763 |
Listener Discovery (MLD) for IPv6", <a href="./rfc2710">RFC 2710</a>, |
| 764 |
October 1999. |
| 765 |
|
| 766 |
[<a id="ref-RFC3376">RFC3376</a>] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. |
| 767 |
Thyagarajan, "Internet Group Management Protocol, Version |
| 768 |
3", <a href="./rfc3376">RFC 3376</a>, October 2002. |
| 769 |
|
| 770 |
[<a id="ref-RFC3775">RFC3775</a>] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support |
| 771 |
in IPv6", <a href="./rfc3775">RFC 3775</a>, June 2004. |
| 772 |
|
| 773 |
[<a id="ref-RFC3810">RFC3810</a>] Vida, R. and L. Costa, "Multicast Listener Discovery |
| 774 |
Version 2 (MLDv2) for IPv6", <a href="./rfc3810">RFC 3810</a>, June 2004. |
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Schmidt, et al. Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 783 |
|
| 784 |
|
| 785 |
[<a id="ref-RFC4605">RFC4605</a>] Fenner, B., He, H., Haberman, B., and H. Sandick, |
| 786 |
"Internet Group Management Protocol (IGMP) / Multicast |
| 787 |
Listener Discovery (MLD)-Based Multicast Forwarding |
| 788 |
("IGMP/MLD Proxying")", <a href="./rfc4605">RFC 4605</a>, August 2006. |
| 789 |
|
| 790 |
[<a id="ref-RFC5213">RFC5213</a>] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., |
| 791 |
and B. Patil, "Proxy Mobile IPv6", <a href="./rfc5213">RFC 5213</a>, August 2008. |
| 792 |
|
| 793 |
[<a id="ref-RFC5844">RFC5844</a>] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy |
| 794 |
Mobile IPv6", <a href="./rfc5844">RFC 5844</a>, May 2010. |
| 795 |
|
| 796 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span> |
| 797 |
|
| 798 |
[<a id="ref-AUTO-MULTICAST">AUTO-MULTICAST</a>] |
| 799 |
Thaler, D., Talwar, M., Aggarwal, A., Vicisano, L., and T. |
| 800 |
Pusateri, "Automatic IP Multicast Without Explicit Tunnels |
| 801 |
(AMT)", Work in Progress, March 2010. |
| 802 |
|
| 803 |
[<a id="ref-RFC2236">RFC2236</a>] Fenner, W., "Internet Group Management Protocol, Version |
| 804 |
2", <a href="./rfc2236">RFC 2236</a>, November 1997. |
| 805 |
|
| 806 |
[<a id="ref-RFC5757">RFC5757</a>] Schmidt, T., Waehlisch, M., and G. Fairhurst, "Multicast |
| 807 |
Mobility in Mobile IP Version 6 (MIPv6): Problem Statement |
| 808 |
and Brief Survey", <a href="./rfc5757">RFC 5757</a>, February 2010. |
| 809 |
|
| 810 |
[<a id="ref-RFC5845">RFC5845</a>] Muhanna, A., Khalil, M., Gundavelli, S., and K. Leung, |
| 811 |
"Generic Routing Encapsulation (GRE) Key Option for Proxy |
| 812 |
Mobile IPv6", <a href="./rfc5845">RFC 5845</a>, June 2010. |
| 813 |
|
| 814 |
|
| 815 |
|
| 816 |
|
| 817 |
|
| 818 |
|
| 819 |
|
| 820 |
|
| 821 |
|
| 822 |
|
| 823 |
|
| 824 |
|
| 825 |
|
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Schmidt, et al. Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Initial MLD Queries on Upcoming Links</span> |
| 842 |
|
| 843 |
According to [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>] and [<a href="./rfc2710" title=""Multicast Listener Discovery (MLD) for IPv6"">RFC2710</a>], when an IGMP-/MLD-enabled |
| 844 |
multicast router starts operating on a subnet, by default it |
| 845 |
considers itself as querier and sends several General Queries. Such |
| 846 |
initial query should be sent by the router immediately, but could be |
| 847 |
delayed by a (tunable) Startup Query Interval (see Sections <a href="#section-7.6.2">7.6.2</a> and |
| 848 |
9.6 of [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>]). |
| 849 |
|
| 850 |
Experimental tests on Linux and Cisco systems have revealed immediate |
| 851 |
IGMP Queries followed a link trigger event (within a fraction of 1 |
| 852 |
ms), while MLD queries immediately followed the autoconfiguration of |
| 853 |
IPv6 link-local addresses at the corresponding interface. |
| 854 |
|
| 855 |
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. State of IGMP/MLD Proxy Implementations</span> |
| 856 |
|
| 857 |
The deployment scenario defined in this document requires certain |
| 858 |
proxy functionalities at the MAGs that implementations of [<a href="./rfc4605" title=""Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("">RFC4605</a>] |
| 859 |
need to contribute. In particular, a simultaneous support of IGMP |
| 860 |
and MLD is needed, as well as a configurable list of downstream |
| 861 |
interfaces that may be altered during runtime, and the deployment of |
| 862 |
multiple proxy instances at a single router that can operate |
| 863 |
independently on separated interfaces. |
| 864 |
|
| 865 |
A brief experimental trial undertaken in February 2010 revealed the |
| 866 |
following divergent statuses of selected IGMP/MLD proxy |
| 867 |
implementations. |
| 868 |
|
| 869 |
Cisco Edge Router: Software-based commodity edge routers (test |
| 870 |
device from the 26xx-Series) implement IGMPv2/v3 proxy functions |
| 871 |
only in combination with Protocol Independent Multicast - Sparse |
| 872 |
Mode (PIM-SM). There is no support of MLD proxy. Interfaces are |
| 873 |
dynamically configurable at runtime via the command line |
| 874 |
interface, but multiple proxy instances are not supported. |
| 875 |
|
| 876 |
Linux igmpproxy: IGMPv2 Proxy implementation that permits a static |
| 877 |
configuration of downstream interfaces (simple bug fix required). |
| 878 |
Multiple instances are prevented by a lock (corresponding code |
| 879 |
reused from a previous Distance Vector Multicast Routing Protocol |
| 880 |
(DVMRP) implementation). IPv6/MLD is unsupported. Project page: |
| 881 |
<a href="http://sourceforge.net/projects/igmpproxy/">http://sourceforge.net/projects/igmpproxy/</a>. |
| 882 |
|
| 883 |
Linux gproxy: IGMPv3 Proxy implementation that permits configuration |
| 884 |
of the upstream interface, only. Downstream interfaces are |
| 885 |
collected at startup without dynamic extension of this list. No |
| 886 |
support of multiple instances or MLD. |
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Schmidt, et al. Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 895 |
|
| 896 |
|
| 897 |
Linux ecmh: MLDv1/2 Proxy implementation without IGMP support that |
| 898 |
inspects IPv4 tunnels and detects encapsulated MLD messages. |
| 899 |
Allows for dynamic addition of interfaces at runtime and multiple |
| 900 |
instances. However, downstream interfaces cannot be configured. |
| 901 |
Project page: <a href="http://sourceforge.net/projects/ecmh/">http://sourceforge.net/projects/ecmh/</a> |
| 902 |
|
| 903 |
<span class="h2"><a class="selflink" id="appendix-C" href="#appendix-C">Appendix C</a>. Comparative Evaluation of Different Approaches</span> |
| 904 |
|
| 905 |
In this section, we briefly evaluate two orthogonal PMIP concepts for |
| 906 |
multicast traffic organization at LMAs. In scenario A, multicast is |
| 907 |
provided by combined unicast/multicast LMAs as described in this |
| 908 |
document. Scenario B directs traffic via a dedicated, central |
| 909 |
multicast router ("LMA-M") that tunnels packets to MAGs independent |
| 910 |
of unicast handoffs. |
| 911 |
|
| 912 |
Neither approach establishes native multicast distribution between |
| 913 |
the LMA and MAG; instead, they use tunneling mechanisms. In scenario |
| 914 |
A, a MAG is connected to different multicast-enabled LMAs and can |
| 915 |
receive the same multicast stream via multiple paths depending on the |
| 916 |
group subscriptions of MNs and their associated LMAs. This problem, |
| 917 |
a.k.a. the tunnel convergence problem, may lead to redundant traffic |
| 918 |
at the MAGs. In contrast, scenario B configures MAGs to establish a |
| 919 |
tunnel to a single, dedicated multicast LMA for all attached MNs and |
| 920 |
relocates overhead costs to the multicast anchor. This eliminates |
| 921 |
redundant traffic but may result in an avalanche problem at the LMA. |
| 922 |
|
| 923 |
We quantify the costs of both approaches based on two metrics: the |
| 924 |
amount of redundant traffic at MAGs and the number of simultaneous |
| 925 |
streams at LMAs. Realistic values depend on the topology and the |
| 926 |
group subscription model. To explore scalability in a large PMIP |
| 927 |
domain of 1,000,000 MNs, we consider the following two extreme |
| 928 |
multicast settings. |
| 929 |
|
| 930 |
1. All MNs participate in distinct multicast groups. |
| 931 |
|
| 932 |
2. All MNs join the same multicast group. |
| 933 |
|
| 934 |
A typical PMIP deployment approximately allows for 5,000 MNs attached |
| 935 |
to one MAG, while 50 MAGs can be served by one LMA. Hence 1,000,000 |
| 936 |
MNs require approximately 200 MAGs backed by 4 LMAs for unicast |
| 937 |
transmission. In scenario A, these LMAs also forward multicast |
| 938 |
streams, while in scenario B one additional dedicated LMA (LMA-M) |
| 939 |
serves multicast. In the following, we calculate the metrics |
| 940 |
described above. In addition, we display the number of packet |
| 941 |
streams that cross the interconnecting (wired) network within a |
| 942 |
PMIPv6 domain. |
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Schmidt, et al. Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 951 |
|
| 952 |
|
| 953 |
Setting 1: |
| 954 |
+===================+==============+================+===============+ |
| 955 |
| PMIP multicast | # of redund. | # of simul. | # of total | |
| 956 |
| scheme | streams | streams | streams in | |
| 957 |
| | at MAG | at LMA/LMA-M | the network | |
| 958 |
+===================+==============+================+===============+ |
| 959 |
| Combined Unicast/ | 0 | 250,000 | 1,000,000 | |
| 960 |
| Multicast LMA | | | | |
| 961 |
+-------------------+--------------+----------------+---------------+ |
| 962 |
| Dedicated | 0 | 1,000,000 | 1,000,000 | |
| 963 |
| Multicast LMA | | | | |
| 964 |
+-------------------+--------------+----------------+---------------+ |
| 965 |
|
| 966 |
1,000,000 MNs are subscribed to distinct multicast groups. |
| 967 |
|
| 968 |
Setting 2: |
| 969 |
+===================+==============+================+===============+ |
| 970 |
| PMIP multicast | # of redund. | # of simul. | # of total | |
| 971 |
| scheme | streams | streams | streams in | |
| 972 |
| | at MAG | at LMA/LMA-M | the network | |
| 973 |
+===================+==============+================+===============+ |
| 974 |
| Combined Unicast/ | 3 | 200 | 800 | |
| 975 |
| Multicast LMA | | | | |
| 976 |
+-------------------+--------------+----------------+---------------+ |
| 977 |
| Dedicated | 0 | 200 | 200 | |
| 978 |
| Multicast LMA | | | | |
| 979 |
+-------------------+--------------+----------------+---------------+ |
| 980 |
|
| 981 |
1,000,000 MNs are subscribed to the same multicast group. |
| 982 |
|
| 983 |
These considerations of extreme settings show that packet duplication |
| 984 |
and replication effects apply in changing intensities for different |
| 985 |
use cases of multicast data services. However, tunnel convergence, |
| 986 |
i.e., duplicate data arriving at a MAG, does cause much smaller |
| 987 |
problems in scalability than the stream replication at LMAs |
| 988 |
(avalanche problem). For scenario A, it should also be noted that |
| 989 |
the high stream replication requirements at LMAs in setting 1 can be |
| 990 |
attenuated by deploying additional LMAs in a PMIP domain, while |
| 991 |
scenario B does not allow for distributing the LMA-M, as no handover |
| 992 |
management is available at LMA-M. |
| 993 |
|
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Schmidt, et al. Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc6224">RFC 6224</a> Multicast Listeners in PMIPv6 April 2011</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
Authors' Addresses |
| 1010 |
|
| 1011 |
Thomas C. Schmidt |
| 1012 |
HAW Hamburg |
| 1013 |
Berliner Tor 7 |
| 1014 |
Hamburg 20099 |
| 1015 |
Germany |
| 1016 |
|
| 1017 |
EMail: [email protected] |
| 1018 |
URI: <a href="http://inet.cpt.haw-hamburg.de/members/schmidt">http://inet.cpt.haw-hamburg.de/members/schmidt</a> |
| 1019 |
|
| 1020 |
|
| 1021 |
Matthias Waehlisch |
| 1022 |
link-lab & FU Berlin |
| 1023 |
Hoenower Str. 35 |
| 1024 |
Berlin 10318 |
| 1025 |
Germany |
| 1026 |
|
| 1027 |
EMail: [email protected] |
| 1028 |
|
| 1029 |
|
| 1030 |
Suresh Krishnan |
| 1031 |
Ericsson |
| 1032 |
8400 Decarie Blvd. |
| 1033 |
Town of Mount Royal, QC |
| 1034 |
Canada |
| 1035 |
|
| 1036 |
EMail: [email protected] |
| 1037 |
|
| 1038 |
|
| 1039 |
|
| 1040 |
|
| 1041 |
|
| 1042 |
|
| 1043 |
|
| 1044 |
|
| 1045 |
|
| 1046 |
|
| 1047 |
|
| 1048 |
|
| 1049 |
|
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
Schmidt, et al. Informational [Page 19] |
| 1061 |
</pre> |