| 1 |
<pre>Internet Engineering Task Force (IETF) M. Liebsch, Ed. |
| 2 |
Request for Comments: 6279 NEC |
| 3 |
Category: Informational S. Jeong |
| 4 |
ISSN: 2070-1721 ETRI |
| 5 |
Q. Wu |
| 6 |
Huawei |
| 7 |
June 2011 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">Proxy Mobile IPv6 (PMIPv6) Localized Routing Problem Statement</span> |
| 11 |
|
| 12 |
Abstract |
| 13 |
|
| 14 |
Proxy Mobile IPv6 is the IETF Standard for network-based mobility |
| 15 |
management. In Proxy Mobile IPv6, mobile nodes are topologically |
| 16 |
anchored at a Local Mobility Anchor, which forwards all data for |
| 17 |
registered mobile nodes. The setup and maintenance of localized |
| 18 |
routing, which allows forwarding of data packets between two mobile |
| 19 |
nodes' Mobility Access Gateways without involvement of their Local |
| 20 |
Mobility Anchor in forwarding, is not considered. This document |
| 21 |
describes the problem space of localized routing in Proxy Mobile |
| 22 |
IPv6. |
| 23 |
|
| 24 |
Status of This Memo |
| 25 |
|
| 26 |
This document is not an Internet Standards Track specification; it is |
| 27 |
published for informational purposes. |
| 28 |
|
| 29 |
This document is a product of the Internet Engineering Task Force |
| 30 |
(IETF). It represents the consensus of the IETF community. It has |
| 31 |
received public review and has been approved for publication by the |
| 32 |
Internet Engineering Steering Group (IESG). Not all documents |
| 33 |
approved by the IESG are a candidate for any level of Internet |
| 34 |
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 35 |
|
| 36 |
Information about the current status of this document, any errata, |
| 37 |
and how to provide feedback on it may be obtained at |
| 38 |
<a href="http://www.rfc-editor.org/info/rfc6279">http://www.rfc-editor.org/info/rfc6279</a>. |
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 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-2">2</a> |
| 75 |
<a href="#section-2">2</a>. Conventions and Terminology .....................................<a href="#page-3">3</a> |
| 76 |
<a href="#section-3">3</a>. Problem Statement for Localized Routing in PMIPv6 ...............<a href="#page-4">4</a> |
| 77 |
<a href="#section-3.1">3.1</a>. General Observation ........................................<a href="#page-4">4</a> |
| 78 |
<a href="#section-3.2">3.2</a>. Use Cases Analysis .........................................<a href="#page-5">5</a> |
| 79 |
<a href="#section-3.3">3.3</a>. IPv4 Considerations ........................................<a href="#page-8">8</a> |
| 80 |
3.3.1. Localized Routing for Communication between |
| 81 |
IPv4 Home Addresses .................................<a href="#page-8">8</a> |
| 82 |
<a href="#section-3.3.2">3.3.2</a>. IPv4 Transport Network Considerations ...............<a href="#page-9">9</a> |
| 83 |
<a href="#section-4">4</a>. Functional Requirements for Localized Routing ...................<a href="#page-9">9</a> |
| 84 |
<a href="#section-5">5</a>. Roaming Considerations .........................................<a href="#page-10">10</a> |
| 85 |
<a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-11">11</a> |
| 86 |
<a href="#section-7">7</a>. Acknowledgments ................................................<a href="#page-12">12</a> |
| 87 |
<a href="#section-8">8</a>. References .....................................................<a href="#page-13">13</a> |
| 88 |
<a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-13">13</a> |
| 89 |
<a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-13">13</a> |
| 90 |
|
| 91 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 92 |
|
| 93 |
The IETF has specified Proxy Mobile IPv6 (PMIPv6) [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] as the |
| 94 |
base protocol for network-based localized mobility management |
| 95 |
(NetLMM). The scope of the base protocol covers the setup and |
| 96 |
maintenance of a tunnel between a Mobile Node's (MN's) Mobile Access |
| 97 |
Gateway (MAG) and its selected Local Mobility Anchor (LMA). Data |
| 98 |
packets will always traverse the MN's MAG and its LMA, irrespective |
| 99 |
of the location of the MN's remote communication endpoint. Even |
| 100 |
though an MN may be attached to the same MAG or a different MAG as |
| 101 |
its Correspondent Node (CN) within the same provider domain, packets |
| 102 |
being associated with their communication will traverse the MN's and |
| 103 |
the CN's LMA, which can be located topologically far away from the |
| 104 |
MN's and the CN's MAG or even in a separate provider domain. |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 111 |
|
| 112 |
|
| 113 |
[<a id="ref-RFC5213">RFC5213</a>] addresses the need to enable local routing of traffic |
| 114 |
between two nodes being attached to the same MAG, but does not |
| 115 |
specify the complete procedure to establish such localized routing |
| 116 |
state on the shared MAG. |
| 117 |
|
| 118 |
The NetLMM Extensions (NetExt) Working Group has an objective to |
| 119 |
design a solution for localized routing in PMIPv6. This objective |
| 120 |
includes the specification of protocol messages and associated |
| 121 |
protocol operation between PMIPv6 components to support the setup of |
| 122 |
a direct routing path for data packets between the MN's and the CN's |
| 123 |
MAG, while both hosts receive mobility service according to the |
| 124 |
PMIPv6 protocol [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>]. As a result of localized routing, these |
| 125 |
packets will be forwarded between the two associated MAGs without |
| 126 |
traversing the MN's and the CN's LMA(s). In cases where one or both |
| 127 |
nodes hand over to a different MAG, the localized routing protocol |
| 128 |
maintains the localized routing path. Relevant protocol interfaces |
| 129 |
may include the interface between associated MAGs, between a MAG and |
| 130 |
an LMA, and between LMAs. The setup of localized routing with CNs |
| 131 |
not registered with a PMIPv6 network is out of scope of the NetExt |
| 132 |
solution and this problem statement. |
| 133 |
|
| 134 |
This document analyzes and discusses the problem space of always |
| 135 |
using the default route through two communicating mobile nodes' local |
| 136 |
mobility anchors. Furthermore, the problem space of enabling |
| 137 |
localized routing in PMIPv6 is analyzed and described, while |
| 138 |
different communication and mobility scenarios are taken into |
| 139 |
account. Based on the analysis, a list of key functional |
| 140 |
requirements is provided, serving as input to the design of the |
| 141 |
protocol solution. |
| 142 |
|
| 143 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions and Terminology</span> |
| 144 |
|
| 145 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 146 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 147 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 148 |
|
| 149 |
This document uses the terminology of [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>]. In addition, the |
| 150 |
following terms are used in the context of this problem statement: |
| 151 |
|
| 152 |
o Mobile Node (MN): Mobile Node without IP mobility support, which |
| 153 |
is attached to a Mobile Access Gateway (MAG) and registered with a |
| 154 |
Local Mobility Anchor (LMA) according to the PMIPv6 specification |
| 155 |
[<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>]. |
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 167 |
|
| 168 |
|
| 169 |
o Correspondent Node (CN): Correspondent Node according to its |
| 170 |
definition in [<a href="./rfc3775" title=""Mobility Support in IPv6"">RFC3775</a>] with or without IP mobility support. The |
| 171 |
CN represents the communication peer of an MN that is attached to |
| 172 |
a MAG and registered with an LMA according to the PMIPv6 |
| 173 |
specification. |
| 174 |
|
| 175 |
o Localized Routing: Result of signaling to set up routing states on |
| 176 |
relevant network entities to allow forwarding of data packets |
| 177 |
between an MN and a CN, which are attached to MAGs sharing the |
| 178 |
same provider domain, without intervention of the MN's LMA and the |
| 179 |
CN's LMA in data forwarding. |
| 180 |
|
| 181 |
o Localized Routing States: Information for localized routing on |
| 182 |
relevant forwarding entities on the optimized data path between an |
| 183 |
MN and a CN. Such information includes route entries and tunnel |
| 184 |
endpoints and may include further information about the MN and the |
| 185 |
CN, such as the communicating nodes' Mobile Node Identifier and |
| 186 |
their assigned Home Network Prefix. |
| 187 |
|
| 188 |
o Provider Domain: A network domain in which network components are |
| 189 |
administered by a single authority, e.g., the mobile operator. |
| 190 |
|
| 191 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Problem Statement for Localized Routing in PMIPv6</span> |
| 192 |
|
| 193 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. General Observation</span> |
| 194 |
|
| 195 |
The Mobile IPv6 (MIPv6) protocol [<a href="./rfc3775" title=""Mobility Support in IPv6"">RFC3775</a>] has built-in mechanisms |
| 196 |
for direct communication between an MN and a CN. Mechanisms for |
| 197 |
route optimization in MIPv6 cannot be directly applied in PMIPv6. |
| 198 |
Following the paradigm of PMIPv6, MNs are not involved in mobility |
| 199 |
signaling and hence cannot perform signaling to set up localized |
| 200 |
routes. Instead, the solution for localized routing must consider |
| 201 |
functions in the network to find out whether or not a localized route |
| 202 |
is to be used and then control the setup and maintenance of localized |
| 203 |
routing states accordingly without any assistance from the MN and the |
| 204 |
CN. In the case of communication between two nodes attached to the |
| 205 |
PMIPv6 network infrastructure and where each node is registered with |
| 206 |
an LMA, data packets between these two nodes will always traverse the |
| 207 |
responsible LMA(s). At least some deployments would benefit from |
| 208 |
having such communication localized, rather than having packets |
| 209 |
traverse the core network to the LMA(s). In the context of this |
| 210 |
document, such localized communication comprises offloading traffic |
| 211 |
from LMAs and establishing an optimized forwarding path between the |
| 212 |
two communication endpoints. |
| 213 |
|
| 214 |
Localized routing is understood in [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] as optimization of |
| 215 |
traffic between an MN and a CN that are attached to an access link |
| 216 |
connected to the same MAG. In such a case, the MAG forwards traffic |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 223 |
|
| 224 |
|
| 225 |
directly between the MN and the CN, assuming the MAG is enabled to |
| 226 |
support this feature (setting of the EnableMAGLocalRouting flag on |
| 227 |
the MAG) and the MN's LMA enforces this optimization. [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] does |
| 228 |
not specify how an LMA can enforce optimization for such local |
| 229 |
communication. Maintaining local forwarding between the MN and the |
| 230 |
regular IPv6 CN gets more complex in the case where the MN performs a |
| 231 |
handover to a different MAG. Such a use case is not considered in |
| 232 |
the specification and is out of scope of this problem statement. |
| 233 |
This document focuses on use cases where both nodes, the MN and the |
| 234 |
CN, are within a PMIPv6 network and served by an LMA in a domain of |
| 235 |
LMAs. |
| 236 |
|
| 237 |
With localized routing, operators have the possibility of offloading |
| 238 |
traffic from LMAs and from the core network. Establishment of a |
| 239 |
direct path between the MN's and the CN's MAG can be beneficial for |
| 240 |
the following reasons: First, by limiting the communication to the |
| 241 |
access nodes, the data traffic traversing the MAG - LMA path |
| 242 |
(network) can be reduced. This is significant, considering that the |
| 243 |
transport network between the access and the core is often the |
| 244 |
bottleneck in terms of costs and performance. Second, there may be |
| 245 |
performance benefits for data flows between the MN and the CN in |
| 246 |
terms of delay and packet loss, especially when the MN and the CN are |
| 247 |
attached to the same MAG and the LMA is topologically far away from |
| 248 |
that MAG. Even when the MN and the CN are attached to different |
| 249 |
MAGs, there could be benefit in limiting the communication to the |
| 250 |
access network only, rather than traversing the transport network to |
| 251 |
the LMA. Furthermore, offloading traffic from the LMA by means of |
| 252 |
localized routing can improve scalability of the LMA, as it |
| 253 |
represents a bottleneck for traffic being forwarded by many MAGs. |
| 254 |
|
| 255 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Use Cases Analysis</span> |
| 256 |
|
| 257 |
This problem statement focuses on local communication between PMIPv6 |
| 258 |
managed nodes, which attach to MAGs sharing the same provider domain. |
| 259 |
The following list analyzes different use cases, which consider the |
| 260 |
existence of multiple LMAs. Figure 1 depicts a PMIPv6-based network |
| 261 |
with two mobility anchors. According to [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>], the MN moves in |
| 262 |
the PMIPv6 domain being built by its LMA and MAG. The same applies |
| 263 |
to the CN, which moves in the PMIPv6 domain built by the CN's LMA and |
| 264 |
MAG. The analysis takes no assumption on whether the MN and the CN |
| 265 |
share the same PMIPv6 domain or not. |
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 279 |
|
| 280 |
|
| 281 |
Internet Backbone |
| 282 |
: : |
| 283 |
+------------------+ |
| 284 |
| | |
| 285 |
+----+ +----+ |
| 286 |
|LMA1| |LMA2| |
| 287 |
+----+ +----+ |
| 288 |
| | |
| 289 |
| | |
| 290 |
+----+------------------+----+ |
| 291 |
| | |
| 292 |
+----+ +----+ |
| 293 |
|MAG1| |MAG2| |
| 294 |
+----+ +----+ |
| 295 |
: : : |
| 296 |
+---+ +---+ +---+ |
| 297 |
|MN | |CN1| |CN2| |
| 298 |
+---+ +---+ +---+ |
| 299 |
|
| 300 |
Figure 1: Reference Architecture for Localized Routing in PMIPv6 |
| 301 |
|
| 302 |
All "A" use cases below assume that both the MN and the CN are |
| 303 |
registered with an LMA according to the PMIPv6 protocol. Whereas |
| 304 |
MAG1 is always considered as the MN's current Proxy Care-of Address, |
| 305 |
the CN can be either connected to the same MAG or to a different MAG |
| 306 |
or LMA as the MN. Accordingly, these topological differences are |
| 307 |
denoted as follows: |
| 308 |
|
| 309 |
A[number of MAGs][number of LMAs] |
| 310 |
|
| 311 |
A11: The MN and the CN (CN1) connect to the same MAG (MAG1) and are |
| 312 |
registered with the same LMA (LMA). The common MAG may forward |
| 313 |
data packets between the MN and the CN directly without forwarding |
| 314 |
any packet to the LMA. [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] addresses this use case, but |
| 315 |
does not specify the complete procedure to establish such |
| 316 |
localized routing state on the shared MAG. |
| 317 |
|
| 318 |
A12: The MN and the CN (CN1) connect to the same MAG (MAG1) and are |
| 319 |
registered with different LMAs (LMA1 and LMA2). The common MAG |
| 320 |
may forward data packets between the MN and the CN directly |
| 321 |
without forwarding any packet to the LMAs. Following the policy |
| 322 |
of [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] and enforcement of the setup of a localized |
| 323 |
forwarding path, potential problems exist in the case where LMA1 |
| 324 |
and LMA2 differ in their policy to control the MAG. |
| 325 |
|
| 326 |
A21: The CN (CN2) connects to a different MAG (MAG2) than the MN |
| 327 |
(MAG1), but the MN and the CN are registered with the same LMA |
| 328 |
(LMA1). The result of localized routing should be the existence |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 335 |
|
| 336 |
|
| 337 |
of routing information at MAG1 and MAG2, which allows direct |
| 338 |
forwarding of packets between the MN's MAG1 and the CN's MAG2. As |
| 339 |
LMA1 is the common anchor for the MN and the CN and maintains |
| 340 |
location information for both nodes, no major race condition and |
| 341 |
instability in updating the states for localized routing is |
| 342 |
expected. |
| 343 |
|
| 344 |
A22: The CN (CN2) connects to a different MAG (MAG2) and a different |
| 345 |
LMA (LMA2) than the MN (MAG1, LMA1). The result of localized |
| 346 |
routing should be the existence of routing information at MAG1 and |
| 347 |
MAG2, which allows direct forwarding of packets between the MN's |
| 348 |
MAG1 and the CN's MAG2. As the location information of the CN and |
| 349 |
the MN is maintained at different LMAs, both LMAs need to be |
| 350 |
involved in the procedure to set up localized routing. In the |
| 351 |
case of a handover of the MN and/or the CN to a different MAG, |
| 352 |
non-synchronized control of updating the states for localized |
| 353 |
routing may result in race conditions, superfluous signaling, and |
| 354 |
packet loss. |
| 355 |
|
| 356 |
The following list summarizes general problems with setting up and |
| 357 |
maintaining localized routing between an MN and a CN. In the context |
| 358 |
of this problem statement, the MN and the CN are always assumed to be |
| 359 |
registered at an LMA according to the PMIPv6 protocol [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>]. |
| 360 |
|
| 361 |
o MNs do not participate in mobility management and hence cannot |
| 362 |
perform binding registration at a CN on their own. Rather, |
| 363 |
entities in the network infrastructure must take over the role of |
| 364 |
MNs to set up and maintain a direct route. Accordingly, a |
| 365 |
solution for localized routing in PMIPv6 must specify protocol |
| 366 |
operation between relevant network components, such as between a |
| 367 |
MAG and an LMA, to enable localized routing for data traffic |
| 368 |
without traversing the MN's and the CN's LMA(s). |
| 369 |
|
| 370 |
o In the case where the MN and the CN are both registered with |
| 371 |
different LMAs according to the PMIPv6 protocol, relevant |
| 372 |
information for the setup of a localized routing path, such as the |
| 373 |
current MAG of the MN and the CN, is distributed between these |
| 374 |
LMAs. This may complicate the setup and stable maintenance of |
| 375 |
states enabling localized routing. |
| 376 |
|
| 377 |
o In the case where localized routing between an MN and a CN has |
| 378 |
been successfully set up and both nodes move and attach to a new |
| 379 |
access router simultaneously, signaling the new location and |
| 380 |
maintenance of states for localized routing at relevant routers |
| 381 |
may run into a race condition situation. This can happen in the |
| 382 |
case where coordination of signaling for localized routing and |
| 383 |
provisioning of relevant state information is distributed between |
| 384 |
different network entities, e.g., different LMAs. In such a case, |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 391 |
|
| 392 |
|
| 393 |
as a result of the MN's handover, updated information about the |
| 394 |
MN's location may arrive at the CN's previous MAG, while the CN |
| 395 |
has already moved to a new MAG. The same applies to the other |
| 396 |
direction, where the system may update the MN's previous MAG about |
| 397 |
the CN's new location, while the MN has moved to a new MAG in the |
| 398 |
meantime. The protocol solution must deal with such exceptional |
| 399 |
handover cases efficiently to avoid or resolve such problems. |
| 400 |
|
| 401 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. IPv4 Considerations</span> |
| 402 |
|
| 403 |
According to [<a href="./rfc5844" title=""IPv4 Support for Proxy Mobile IPv6"">RFC5844</a>], the basic configuration requirements for |
| 404 |
supporting IPv4 in PMIPv6 are that LMAs and MAGs are both IPv4 and |
| 405 |
IPv6 enabled. Also, LMAs and MAGs must have a globally unique IPv6 |
| 406 |
address configured, irrespective of enabled support for IPv6 routing |
| 407 |
between these components. This requirement should also apply to |
| 408 |
configuration requirements of localized routing. |
| 409 |
|
| 410 |
Additional issues emerge when localized routing is considered for |
| 411 |
PMIPv6 with IPv4 support. These can be classified into two general |
| 412 |
groups: issues with localized routing between an MN's and a CN's IPv4 |
| 413 |
Home Addresses, and transport plane issues. The following |
| 414 |
subsections analyze these two groups. |
| 415 |
|
| 416 |
<span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Localized Routing for Communication between IPv4 Home Addresses</span> |
| 417 |
|
| 418 |
In the case where an LMA and a MAG hold a registration to support |
| 419 |
IPv4 Home Address mobility for an MN, the MAG and the LMA must |
| 420 |
support appropriate encapsulation of IPv4 packets. To enable |
| 421 |
localized routing, the MN's MAG must encapsulate and forward routing |
| 422 |
path optimized packets to the CN's MAG and needs to ensure that the |
| 423 |
chosen encapsulation mode is supported by the correspondent MAG. |
| 424 |
Incompatibility in a selected encapsulation mode causes failure in |
| 425 |
setting up a localized route. |
| 426 |
|
| 427 |
When localized routing is used for IPv4 traffic, the conceptual data |
| 428 |
structures on associated MAGs must be augmented with appropriate |
| 429 |
parameters for forwarding localized traffic. MAGs may need to |
| 430 |
maintain a routing state for each MN-CN-pair and make routing |
| 431 |
decisions for uplink traffic based on the packet's complete IPv4 |
| 432 |
source and destination address. Hence, conceptual data structures to |
| 433 |
handle states for localized routes need to comprise this address |
| 434 |
tuple for unique identification. |
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 447 |
|
| 448 |
|
| 449 |
As a known constraint, IPv4 addresses of two nodes that hold |
| 450 |
addresses from a private address space may overlap. To uniquely |
| 451 |
identify both nodes, the IPv4 address of the MN and the CN must not |
| 452 |
overlap. To cope with overlapping address spaces, the localized |
| 453 |
routing solution could use additional mechanisms to tag and uniquely |
| 454 |
identify the MN and the CN. |
| 455 |
|
| 456 |
<span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. IPv4 Transport Network Considerations</span> |
| 457 |
|
| 458 |
The transport network between the LMA and the MAG may be based on |
| 459 |
IPv6 or IPv4. Deployments may ensure that the same transport |
| 460 |
mechanism (i.e., IPv6 or IPv4) is used for operational consistency. |
| 461 |
Similar to the encapsulation requirement stated in the previous |
| 462 |
section, the IP version used for localized routing is also assumed, |
| 463 |
by configuration, to be consistent across all MAGs within the |
| 464 |
associated provider domain. The design of optional mechanisms for |
| 465 |
negotiating the IP version to use as well as the encapsulation mode |
| 466 |
to use are outside the scope of the NetExt WG's solution for |
| 467 |
localized routing. |
| 468 |
|
| 469 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Functional Requirements for Localized Routing</span> |
| 470 |
|
| 471 |
Several tasks need to be performed by the network infrastructure |
| 472 |
components before relevant information for such direct communication |
| 473 |
is discovered and associated states for localized routing can be set |
| 474 |
up. The following list summarizes some key functions that need to be |
| 475 |
performed by the PMIPv6-enabled network infrastructure to substitute |
| 476 |
mobile nodes in setting up a direct route. |
| 477 |
|
| 478 |
o Detection of the possibility to perform localized routing. This |
| 479 |
function includes looking at a data packet's source and |
| 480 |
destination address. |
| 481 |
|
| 482 |
o Initiation of a procedure that sets up a localized routing path. |
| 483 |
|
| 484 |
o Discovery of stateful entities (i.e., the LMA(s) and/or the |
| 485 |
MAG(s)) that maintain and can provide relevant information needed |
| 486 |
to set up a localized routing path. Such information may include |
| 487 |
the routable address of an LMA or MAG, where one or both mobile |
| 488 |
nodes are connected to and registered with that LMA or MAG. |
| 489 |
|
| 490 |
o Control in setting up and maintaining (e.g., during handover) the |
| 491 |
localized routing path. Control is also needed to terminate the |
| 492 |
use of a localized routing path and to delete associated states, |
| 493 |
whereas a trigger for the termination may come from a non-PMIPv6- |
| 494 |
related component. |
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 503 |
|
| 504 |
|
| 505 |
o Enforcement of administrative policy rules to localized routing. |
| 506 |
Such policies allow operators to have further control of the setup |
| 507 |
of a localized route and enable the possibility to disallow |
| 508 |
localized routing, for example, to ensure that traffic traverses |
| 509 |
charging-related functions on the LMA. Explicit authorization of |
| 510 |
localized routing is, for example, discussed in [<a href="#ref-PMIP6-LR" title=""Diameter Support for Proxy Mobile IPv6 Localized Routing"">PMIP6-LR</a>]. As a |
| 511 |
further example, mobile-node- and operator-specific policy rules |
| 512 |
can be established on PMIPv6 components during PMIPv6 |
| 513 |
bootstrapping according to [<a href="./rfc5779" title=""Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter Server"">RFC5779</a>]. |
| 514 |
|
| 515 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Roaming Considerations</span> |
| 516 |
|
| 517 |
Figure 2 shows PMIPv6 roaming cases where PMIPv6 components (e.g., |
| 518 |
LMAs, MAGs) tied by the MN and the CN may be distributed between |
| 519 |
different provider domains (i.e., domain A, B, C) and the MN and/or |
| 520 |
CN moves from one provider domain to another one. In order to |
| 521 |
support localized routing when roaming occurs, it is required that |
| 522 |
MAGs to which the MN and CN connect be within the same provider |
| 523 |
domain, and each MAG has a security relationship with the |
| 524 |
corresponding LMA, which maintains the registration of the MN or the |
| 525 |
CN, respectively. |
| 526 |
|
| 527 |
According to the roaming model as depicted in Figure 2, the MN's |
| 528 |
PMIPv6 domain is characterized by its MAG (MAG1/MAG1') and its LMA |
| 529 |
(LMA1), whereas the CN's PMIPv6 domain is characterized by the CN's |
| 530 |
MAG (MAG2/MAG2') and its LMA (LMA2/LMA2'). A solution for localized |
| 531 |
routing cannot take any assumption about whether or not the MN and CN |
| 532 |
share the same PMIPv6 domain; hence, MAG1/MAG1' may not share a |
| 533 |
security association with LMA2/LMA2', and MAG2/MAG2' may not share a |
| 534 |
security association with LMA1, respectively. |
| 535 |
|
| 536 |
It is not required that LMAs, which hold the registration for the MN |
| 537 |
and the CN, respectively, be part of the same provider domain as the |
| 538 |
MAGs where the MN and CN attach. When the MN's MAG and LMA belong to |
| 539 |
different provider domains (A and C), localized routing is subject to |
| 540 |
policy governing the service level agreements between these domains. |
| 541 |
The same applies to the provider domains that provide the CN's MAG |
| 542 |
and LMA. Based on the above requirements, four PMIPv6 roaming and |
| 543 |
non-roaming cases can be taken into account. |
| 544 |
|
| 545 |
o Case 1: The MN's MAG (MAG1), the CN's MAG (MAG2), the MN's LMA |
| 546 |
(LMA1), and the CN's LMA (LMA2) are located in the same provider |
| 547 |
domain A. |
| 548 |
|
| 549 |
o Case 2: The MN's MAG (MAG1), the CN's MAG (MAG2), and the MN's LMA |
| 550 |
(LMA1) are located in the same domain A, while the CN's LMA |
| 551 |
(LMA2') is located in provider domain B. |
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 559 |
|
| 560 |
|
| 561 |
o Case 3: The MN's MAG (MAG1') and the CN's MAG (MAG2') are located |
| 562 |
in domain C, while the MN's LMA (LMA1) and the CN's LMA (LMA2) are |
| 563 |
located in provider domain A. |
| 564 |
|
| 565 |
o Case 4: The MN's MAG (MAG1') and the CN's MAG (MAG2') are located |
| 566 |
in provider domain C, while the MN's LMA (LMA1) is located in |
| 567 |
provider domain A and the CN's LMA (LMA2') is located in provider |
| 568 |
domain B. |
| 569 |
|
| 570 |
In these roaming cases, the MN can be allowed to roam within its |
| 571 |
domain (e.g., the MN's home domain in which the MN's LMA is located) |
| 572 |
or over different domains (e.g., the MN moves from its home domain to |
| 573 |
a visited domain). During mobility, the CN and MN should remain |
| 574 |
attached to MAGs of the same provider domain to maintain efficient |
| 575 |
routing of traffic between their MAGs. |
| 576 |
|
| 577 |
| |
| 578 |
+-----+ +-----+ | +-----+ |
| 579 |
|LMA1 | |LMA2 | | |LMA2'| |
| 580 |
+-----+ +-----+ | +-----+ |
| 581 |
| |
| 582 |
| |
| 583 |
| |
| 584 |
| |
| 585 |
+-----+ +-----+ | |
| 586 |
|MAG1 | |MAG2 | | |
| 587 |
+-----+ +-----+ | |
| 588 |
| |
| 589 |
| |
| 590 |
Provider Domain A | Provider Domain B |
| 591 |
------------------------------+------------------------------- |
| 592 |
Provider Domain C |
| 593 |
|
| 594 |
+-----+ +-----+ |
| 595 |
|MAG1'| |MAG2'| |
| 596 |
+-----+ +-----+ |
| 597 |
|
| 598 |
Figure 2: PMIPv6 Roaming Cases Considered for Localized Routing |
| 599 |
|
| 600 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 601 |
|
| 602 |
A protocol solution for localized routing in a PMIPv6 network must |
| 603 |
counter unauthorized change of a routing path. In particular, the |
| 604 |
control plane for localized routing must preclude the blocking or |
| 605 |
hijacking of mobile nodes' traffic by malicious or compromised |
| 606 |
network components. A security solution must support suitable |
| 607 |
mechanisms for authentication of control plane components of the |
| 608 |
localized routing functional architecture for both roaming and |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 615 |
|
| 616 |
|
| 617 |
non-roaming scenarios. Any possibility for Internet hosts to |
| 618 |
interfere with the localized routing procedure in a malicious manner |
| 619 |
must be precluded. |
| 620 |
|
| 621 |
Since network entities other than MNs and CNs perform signaling to |
| 622 |
set up localized routing, the MIPv6 return routability test [<a href="./rfc3775" title=""Mobility Support in IPv6"">RFC3775</a>] |
| 623 |
is not suitable to authenticate associated signaling messages in |
| 624 |
PMIPv6. Solutions for localized routing in PMIPv6 need to mitigate, |
| 625 |
or to provide sufficient defense against, possible security threats. |
| 626 |
When PMIPv6 participants are administered within the same domain, |
| 627 |
infrastructure-based authorization mechanisms, such as IPsec, may be |
| 628 |
usable to protect signaling for localized routing. |
| 629 |
|
| 630 |
Existing security associations according to [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] can be re-used |
| 631 |
to protect signaling for localized routing on the interface between a |
| 632 |
MAG and an LMA. In the case where a protocol solution for localized |
| 633 |
routing in PMIPv6 relies on protocol operation between MAGs, means |
| 634 |
for protection of signaling between these MAGs must be provided. The |
| 635 |
same applies for signaling on a possible protocol interface between |
| 636 |
two LMAs of the same domain. |
| 637 |
|
| 638 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span> |
| 639 |
|
| 640 |
Many aspects of the problem space for route optimization in PMIPv6 |
| 641 |
have been discussed in the context of a PMIPv6 Route Optimization |
| 642 |
Design Goals document, which was submitted to the NetLMM WG in |
| 643 |
November 2007. This group of contributors includes Sangjin Jeong, |
| 644 |
Christian Vogt, Ryuji Wakikawa, Marco Liebsch, Behcet Sarikaya, |
| 645 |
Shinta Sugimoto, Long Le, Alice Qinxia, and Jaehwoon Lee. Many |
| 646 |
thanks to Rajeev Koodli for his comments about the structure and |
| 647 |
scope of this problem statement for the NetExt WG. |
| 648 |
|
| 649 |
This problem statement reflects the results of the discussion in the |
| 650 |
NetExt group. Many thanks to Hidetoshi Yokota, Carlos Bernardos, |
| 651 |
Ashutosh Dutta, Sri Gundavelli, Mohana Jeyatharan, Jouni Korhonen, |
| 652 |
Glen Zorn, Dirk von Hugo, Frank Xia, Xiangsong Cui, and Basavaraj |
| 653 |
Patil for their comments and support to improve the quality of the |
| 654 |
problem statement. |
| 655 |
|
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 674 |
|
| 675 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span> |
| 676 |
|
| 677 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 678 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 679 |
|
| 680 |
[<a id="ref-RFC5213">RFC5213</a>] Gundavelli, S., Ed., Leung, K., Devarapalli, V., |
| 681 |
Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", |
| 682 |
<a href="./rfc5213">RFC 5213</a>, August 2008. |
| 683 |
|
| 684 |
[<a id="ref-RFC5844">RFC5844</a>] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy |
| 685 |
Mobile IPv6", <a href="./rfc5844">RFC 5844</a>, May 2010. |
| 686 |
|
| 687 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span> |
| 688 |
|
| 689 |
[<a id="ref-PMIP6-LR">PMIP6-LR</a>] Zorn, G., Wu, Q., Liebsch, M., and J. Korhonen, "Diameter |
| 690 |
Support for Proxy Mobile IPv6 Localized Routing", Work |
| 691 |
in Progress, May 2011. |
| 692 |
|
| 693 |
[<a id="ref-RFC3775">RFC3775</a>] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support |
| 694 |
in IPv6", <a href="./rfc3775">RFC 3775</a>, June 2004. |
| 695 |
|
| 696 |
[<a id="ref-RFC5779">RFC5779</a>] Korhonen, J., Ed., Bournelle, J., Chowdhury, K., Muhanna, |
| 697 |
A., and U. Meyer, "Diameter Proxy Mobile IPv6: Mobile |
| 698 |
Access Gateway and Local Mobility Anchor Interaction with |
| 699 |
Diameter Server", <a href="./rfc5779">RFC 5779</a>, February 2010. |
| 700 |
|
| 701 |
|
| 702 |
|
| 703 |
|
| 704 |
|
| 705 |
|
| 706 |
|
| 707 |
|
| 708 |
|
| 709 |
|
| 710 |
|
| 711 |
|
| 712 |
|
| 713 |
|
| 714 |
|
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Liebsch, 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="./rfc6279">RFC 6279</a> PMIPv6 Localized Routing PS June 2011</span> |
| 727 |
|
| 728 |
|
| 729 |
Authors' Addresses |
| 730 |
|
| 731 |
Marco Liebsch (editor) |
| 732 |
NEC Laboratories Europe |
| 733 |
NEC Europe Ltd. |
| 734 |
Kurfuersten-Anlage 36 |
| 735 |
69115 Heidelberg |
| 736 |
Germany |
| 737 |
|
| 738 |
Phone: +49 6221 4342146 |
| 739 |
EMail: [email protected] |
| 740 |
|
| 741 |
|
| 742 |
Sangjin Jeong |
| 743 |
ETRI |
| 744 |
218 Gajeongno, Yuseong |
| 745 |
Daejeon 305-700 |
| 746 |
Korea |
| 747 |
|
| 748 |
Phone: +82 42 860 1877 |
| 749 |
EMail: [email protected] |
| 750 |
|
| 751 |
|
| 752 |
Qin Wu |
| 753 |
Huawei Technologies Co., Ltd |
| 754 |
101 Software Avenue, Yuhua District |
| 755 |
Nanjing 210012 |
| 756 |
China |
| 757 |
|
| 758 |
Phone: +86 25 56623633 |
| 759 |
EMail: [email protected] |
| 760 |
|
| 761 |
|
| 762 |
|
| 763 |
|
| 764 |
|
| 765 |
|
| 766 |
|
| 767 |
|
| 768 |
|
| 769 |
|
| 770 |
|
| 771 |
|
| 772 |
|
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
Liebsch, et al. Informational [Page 14] |
| 781 |
</pre> |