| 1 |
<pre>Network Working Group G. Tsirtsis |
| 2 |
Request for Comments: 5454 V. Park |
| 3 |
Category: Standards Track Qualcomm |
| 4 |
H. Soliman |
| 5 |
Elevate Technologies |
| 6 |
March 2009 |
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">Dual-Stack Mobile IPv4</span> |
| 10 |
|
| 11 |
Status of This Memo |
| 12 |
|
| 13 |
This document specifies an Internet standards track protocol for the |
| 14 |
Internet community, and requests discussion and suggestions for |
| 15 |
improvements. Please refer to the current edition of the "Internet |
| 16 |
Official Protocol Standards" (STD 1) for the standardization state |
| 17 |
and status of this protocol. Distribution of this memo is unlimited. |
| 18 |
|
| 19 |
Copyright Notice |
| 20 |
|
| 21 |
Copyright (c) 2009 IETF Trust and the persons identified as the |
| 22 |
document authors. All rights reserved. |
| 23 |
|
| 24 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 25 |
Provisions Relating to IETF Documents in effect on the date of |
| 26 |
publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). |
| 27 |
Please review these documents carefully, as they describe your rights |
| 28 |
and restrictions with respect to this document. |
| 29 |
|
| 30 |
Abstract |
| 31 |
|
| 32 |
This specification provides IPv6 extensions to the Mobile IPv4 |
| 33 |
protocol. The extensions allow a dual-stack node to use IPv4 and |
| 34 |
IPv6 home addresses as well as to move between IPv4 and dual stack |
| 35 |
network infrastructures. |
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a> |
| 60 |
<a href="#section-1.1">1.1</a>. Requirements Notation ......................................<a href="#page-3">3</a> |
| 61 |
<a href="#section-1.2">1.2</a>. Goals ......................................................<a href="#page-3">3</a> |
| 62 |
<a href="#section-1.3">1.3</a>. Non-Goals ..................................................<a href="#page-4">4</a> |
| 63 |
<a href="#section-1.4">1.4</a>. Implicit and Explicit Modes ................................<a href="#page-4">4</a> |
| 64 |
<a href="#section-2">2</a>. Extension Formats ...............................................<a href="#page-4">4</a> |
| 65 |
<a href="#section-2.1">2.1</a>. IPv6 Prefix Request Extension ..............................<a href="#page-4">4</a> |
| 66 |
<a href="#section-2.2">2.2</a>. IPv6 Prefix Reply Extension ................................<a href="#page-5">5</a> |
| 67 |
<a href="#section-2.3">2.3</a>. IPv6 Tunneling Mode Extension ..............................<a href="#page-7">7</a> |
| 68 |
<a href="#section-3">3</a>. Mobile IP Registrations .........................................<a href="#page-8">8</a> |
| 69 |
<a href="#section-3.1">3.1</a>. Registration Request .......................................<a href="#page-8">8</a> |
| 70 |
<a href="#section-3.2">3.2</a>. Registration Reply .........................................<a href="#page-8">8</a> |
| 71 |
<a href="#section-3.3">3.3</a>. Home Agent Considerations ..................................<a href="#page-9">9</a> |
| 72 |
<a href="#section-3.3.1">3.3.1</a>. IPv6 Reachability ..................................<a href="#page-10">10</a> |
| 73 |
<a href="#section-3.3.2">3.3.2</a>. Processing Intercepted IPv6 Packets ................<a href="#page-10">10</a> |
| 74 |
<a href="#section-3.3.3">3.3.3</a>. IPv6 Multicast Membership Control ..................<a href="#page-12">12</a> |
| 75 |
<a href="#section-3.4">3.4</a>. Foreign Agent Considerations ..............................<a href="#page-12">12</a> |
| 76 |
<a href="#section-3.5">3.5</a>. Mobile Node Considerations ................................<a href="#page-12">12</a> |
| 77 |
<a href="#section-3.6">3.6</a>. Tunneling Impacts .........................................<a href="#page-13">13</a> |
| 78 |
<a href="#section-3.7">3.7</a>. IPv6 Prefixes .............................................<a href="#page-14">14</a> |
| 79 |
<a href="#section-3.7.1">3.7.1</a>. Dynamic IPv6 Prefix Delegation .....................<a href="#page-14">14</a> |
| 80 |
<a href="#section-3.8">3.8</a>. Deregistration of IPv6 Prefix .............................<a href="#page-15">15</a> |
| 81 |
<a href="#section-3.9">3.9</a>. Registration with a Private CoA ...........................<a href="#page-15">15</a> |
| 82 |
<a href="#section-4">4</a>. Security Considerations ........................................<a href="#page-15">15</a> |
| 83 |
<a href="#section-5">5</a>. IANA Considerations ............................................<a href="#page-16">16</a> |
| 84 |
<a href="#section-6">6</a>. Acknowledgements ...............................................<a href="#page-16">16</a> |
| 85 |
<a href="#section-7">7</a>. References .....................................................<a href="#page-16">16</a> |
| 86 |
<a href="#section-7.1">7.1</a>. Normative References ......................................<a href="#page-16">16</a> |
| 87 |
<a href="#section-7.2">7.2</a>. Informative References ....................................<a href="#page-17">17</a> |
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
Mobile IPv4 [<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>] allows a mobile node with an IPv4 address to |
| 116 |
maintain communications while moving in an IPv4 network. |
| 117 |
|
| 118 |
Extensions defined in this document allow a node that has IPv4 and |
| 119 |
IPv6 addresses [<a href="./rfc2460" title=""Internet Protocol, Version 6 (IPv6) Specification"">RFC2460</a>] to maintain communications through any of |
| 120 |
its addresses while moving in IPv4 or dual stack networks. |
| 121 |
|
| 122 |
Essentially, this specification separates the Mobile IPv4 signaling |
| 123 |
from the IP version of the traffic it tunnels. Mobile IPv4 with the |
| 124 |
present extensions remains a signaling protocol that runs over IPv4, |
| 125 |
and yet can set up both IPv4 and IPv6 tunnels over IPv4. |
| 126 |
|
| 127 |
The aim is two-fold: |
| 128 |
|
| 129 |
On one hand, Mobile IPv4 with the present extensions becomes a |
| 130 |
useful transition mechanism, allowing automated but controlled |
| 131 |
tunneling of IPv6 traffic over IPv4 tunnels. Dual-stack nodes in |
| 132 |
dual-stack home networks can now roam to and from legacy IPv4 |
| 133 |
networks, while IPv4 mobile nodes and networks can migrate to IPv6 |
| 134 |
without changing mobility management, and without upgrading all |
| 135 |
network nodes to IPv6 at once. |
| 136 |
|
| 137 |
On the other hand, and more importantly, it allows dual-stack |
| 138 |
mobile nodes and networks to utilize a single protocol for the |
| 139 |
movement of both IPv4 and IPv6 stacks in the network topology. |
| 140 |
|
| 141 |
Note that features like Mobile IPv6 [<a href="./rfc3775" title=""Mobility Support in IPv6"">RFC3775</a>] style route |
| 142 |
optimization will not be possible with this solution as it still |
| 143 |
relies on Mobile IPv4 signaling, which does not provide route |
| 144 |
optimization. |
| 145 |
|
| 146 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Notation</span> |
| 147 |
|
| 148 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 149 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 150 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 151 |
|
| 152 |
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Goals</span> |
| 153 |
|
| 154 |
a. The solution supports the registration of IPv6 home prefix(es) in |
| 155 |
addition to regular IPv4 home address (HoA) registration. |
| 156 |
|
| 157 |
b. The solution supports static and dynamic IPv6 prefix delegation. |
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Non-Goals</span> |
| 170 |
|
| 171 |
a. The solution does not provide support for IPv6 care-of address |
| 172 |
(CoA) registration. |
| 173 |
|
| 174 |
<span class="h3"><a class="selflink" id="section-1.4" href="#section-1.4">1.4</a>. Implicit and Explicit Modes</span> |
| 175 |
|
| 176 |
As defined in Network Mobility (NEMO) [<a href="./rfc3963" title=""Network Mobility (NEMO) Basic Support Protocol"">RFC3963</a>], this specification |
| 177 |
also supports two modes of operation; the implicit mode and the |
| 178 |
explicit mode. |
| 179 |
|
| 180 |
In the implicit mode, the mobile node does not include any IPv6 |
| 181 |
prefix request extensions in the registration request. The home |
| 182 |
agent can use any mechanism (not defined in this document) to |
| 183 |
determine the IPv6 prefix(es) owned by the mobile node and to set up |
| 184 |
forwarding for these prefixes. In this mode of operation, all |
| 185 |
traffic to and from the IPv6 prefixes MUST be encapsulated over the |
| 186 |
IPv4 tunnel between the mobile node's IPv4 home address and the IPv4 |
| 187 |
address of the home agent, and as such, it is transparent to any |
| 188 |
foreign agent in the path. This IPv4 tunnel is established by |
| 189 |
mechanisms that are out of the scope of this document on both the |
| 190 |
mobile node and home agent when operating in the implicit mode. |
| 191 |
|
| 192 |
In the explicit mode, IPv6 bindings are signaled explicitly. The |
| 193 |
mobile node includes one or more IPv6 prefix request extensions in |
| 194 |
the registration request, while the home agent returns corresponding |
| 195 |
IPv6 prefix reply extensions to accept/reject the IPv6 bindings. |
| 196 |
|
| 197 |
Additionally, in the explicit mode, the mobile node (when co-located |
| 198 |
mode of operation is used) can indicate whether IPv6 traffic should |
| 199 |
be tunneled to the care-of address or the home address of the mobile |
| 200 |
node. |
| 201 |
|
| 202 |
The rest of this specification is primarily defining the explicit |
| 203 |
mode. |
| 204 |
|
| 205 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Extension Formats</span> |
| 206 |
|
| 207 |
The following extensions are defined according to this specification. |
| 208 |
|
| 209 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. IPv6 Prefix Request Extension</span> |
| 210 |
|
| 211 |
A new skippable extension to the Mobile IPv4 registration request |
| 212 |
message in accordance to the short extension format of [<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>] is |
| 213 |
defined here. |
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 223 |
|
| 224 |
|
| 225 |
This extension contains a Mobile IPv6 network prefix and its prefix |
| 226 |
length. |
| 227 |
|
| 228 |
0 1 2 3 |
| 229 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 230 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 231 |
| Type | Length | Subtype | Prefix Length | |
| 232 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 233 |
| | |
| 234 |
+ + |
| 235 |
| | |
| 236 |
+ Mobile IPv6 Network Prefix + |
| 237 |
| | |
| 238 |
+ + |
| 239 |
| | |
| 240 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 241 |
|
| 242 |
Figure 1: IPv6 Prefix Request Extension |
| 243 |
|
| 244 |
Type |
| 245 |
|
| 246 |
152 (Dual-Stack Mobile IPv4 (DSMIPv4) Extension) |
| 247 |
|
| 248 |
Length |
| 249 |
|
| 250 |
18 |
| 251 |
|
| 252 |
Subtype |
| 253 |
|
| 254 |
1 (IPv6 Prefix Request) |
| 255 |
|
| 256 |
Prefix Length |
| 257 |
|
| 258 |
A sixteen-byte field containing the Mobile IPv6 Network Prefix; |
| 259 |
all insignificant (low-order) bits (beyond the Prefix Length) MUST |
| 260 |
be set to 0 by the originator of the option and ignored by the |
| 261 |
receiver. |
| 262 |
|
| 263 |
Mobile IPv6 Network Prefix |
| 264 |
|
| 265 |
A sixteen-byte field containing the Mobile IPv6 Network Prefix |
| 266 |
|
| 267 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. IPv6 Prefix Reply Extension</span> |
| 268 |
|
| 269 |
A new skippable extension to the Mobile IPv4 registration reply |
| 270 |
message in accordance to the short extension format of [<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>] is |
| 271 |
defined here. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 279 |
|
| 280 |
|
| 281 |
This extension defines a Mobile IPv6 Network Prefix and its prefix |
| 282 |
length, as well as a code. |
| 283 |
|
| 284 |
0 1 2 3 |
| 285 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 286 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 287 |
| Type | Length | Subtype | Code | |
| 288 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 289 |
| Prefix Length | Reserved | | |
| 290 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |
| 291 |
| | |
| 292 |
+ + |
| 293 |
| | |
| 294 |
+ Mobile IPv6 Network Prefix + |
| 295 |
| | |
| 296 |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 297 |
| | |
| 298 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 299 |
|
| 300 |
Figure 2: IPv6 Prefix Reply Extension |
| 301 |
|
| 302 |
Type |
| 303 |
|
| 304 |
152 (DSMIPv4 Extension) |
| 305 |
|
| 306 |
Length |
| 307 |
|
| 308 |
20 |
| 309 |
|
| 310 |
Subtype |
| 311 |
|
| 312 |
2 (IPv6 Prefix Reply) |
| 313 |
|
| 314 |
Code |
| 315 |
|
| 316 |
A value indicating the result of the registration request with |
| 317 |
respect to the IPv6 home prefix registration. See below for |
| 318 |
currently defined Codes. |
| 319 |
|
| 320 |
Prefix Length |
| 321 |
|
| 322 |
Indicates the prefix length of the prefix included in the Mobile |
| 323 |
IPv6 Network Prefix field. A value of 255 indicates that a link- |
| 324 |
local address is included in the Mobile IPv6 Network Prefix field. |
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 335 |
|
| 336 |
|
| 337 |
Reserved |
| 338 |
|
| 339 |
Set to 0 by the sender, ignored by the receiver |
| 340 |
|
| 341 |
Mobile IPv6 Network Prefix |
| 342 |
|
| 343 |
A sixteen-byte field containing the Mobile IPv6 Network Prefix; |
| 344 |
all insignificant (low-order) bits (beyond the Prefix Length) MUST |
| 345 |
be set to 0 by the originator of the option and ignored by the |
| 346 |
receiver. |
| 347 |
|
| 348 |
The following values are defined for use as a Code value in the above |
| 349 |
extension: |
| 350 |
|
| 351 |
0 registration accepted, IPv6 to be tunneled to HoA |
| 352 |
|
| 353 |
1 registration accepted, IPv6 to be tunneled to CoA |
| 354 |
|
| 355 |
8 registration rejected, reason unspecified |
| 356 |
|
| 357 |
9 registration rejected, administratively prohibited |
| 358 |
|
| 359 |
Note that a registration reply that does not include an IPv6 prefix |
| 360 |
reply extension, when received in response to a registration request |
| 361 |
carrying at least one instance of the IPv6 prefix request extension, |
| 362 |
indicates that the home agent does not support IPv6 extensions and |
| 363 |
thus has ignored such extensions in the registration request. |
| 364 |
|
| 365 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. IPv6 Tunneling Mode Extension</span> |
| 366 |
|
| 367 |
A new skippable extension to the Mobile IPv4 registration request |
| 368 |
message in accordance to the short extension format of [<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>] is |
| 369 |
defined here. |
| 370 |
|
| 371 |
By including this extension in a registration request, the sender |
| 372 |
indicates that IPv6 traffic can be tunneled to the mobile node's CoA. |
| 373 |
|
| 374 |
0 1 2 3 |
| 375 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 376 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 377 |
| Type | Length | Subtype | Reserved | |
| 378 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 379 |
|
| 380 |
Figure 3: IPv6 Tunneling Mode Extension |
| 381 |
|
| 382 |
Type |
| 383 |
|
| 384 |
152 (DSMIPv4 Extension) |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 391 |
|
| 392 |
|
| 393 |
Length |
| 394 |
|
| 395 |
2 |
| 396 |
|
| 397 |
Subtype |
| 398 |
|
| 399 |
3 (IPv6 Tunneling Mode) |
| 400 |
|
| 401 |
Reserved |
| 402 |
|
| 403 |
Set to 0 by the sender, ignored by the receiver |
| 404 |
|
| 405 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Mobile IP Registrations</span> |
| 406 |
|
| 407 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Registration Request</span> |
| 408 |
|
| 409 |
A mobile node MAY include in a registration request one or more IPv6 |
| 410 |
prefix request extensions defined in this specification. |
| 411 |
|
| 412 |
A mobile node MAY also include exactly one IPv6 tunneling mode |
| 413 |
extension when it uses the co-located care-of address mode of |
| 414 |
[<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>]. |
| 415 |
|
| 416 |
When IPv6 prefix and/or IPv6 tunneling mode extensions are used by |
| 417 |
the mobile IP client, they MUST be placed after the registration |
| 418 |
request header and before the mobile -- home authentication extension |
| 419 |
so they MUST be included in the computation of any authentication |
| 420 |
extension. |
| 421 |
|
| 422 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Registration Reply</span> |
| 423 |
|
| 424 |
The mechanism described in this specification depends on skippable |
| 425 |
extensions. For that reason, a registration reply that does not |
| 426 |
include an IPv6 prefix reply extension, in response to a registration |
| 427 |
request including an IPv6 prefix request extension, indicates that |
| 428 |
the home agent does not support IPv6 extensions and has ignored the |
| 429 |
request. |
| 430 |
|
| 431 |
If an IPv6 prefix reply extension is included in a registration |
| 432 |
reply, then the extension indicates the success or failure of the |
| 433 |
IPv6 prefix registration. The IPv6 prefix reply extension does not |
| 434 |
affect, in any way, the code value in the registration reply header |
| 435 |
but it is superseded by it. In other words, if the code field in the |
| 436 |
registration reply header is set to a reject code, then all IPv6 |
| 437 |
prefix request extensions are also rejected. If the code field in |
| 438 |
the registration reply header, however, is set to an accept code, |
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 447 |
|
| 448 |
|
| 449 |
then an IPv6 prefix reply extension with a code field set to a reject |
| 450 |
code only rejects the binding for the specific IPv6 prefix indicated |
| 451 |
in the same extension. |
| 452 |
|
| 453 |
Note that a rejecting IPv6 prefix reply extension has the same effect |
| 454 |
as not including such an extension at all, in the sense that, in both |
| 455 |
cases, the mobile node must act as if the corresponding IPv6 prefix |
| 456 |
request extension included in the registration request was rejected. |
| 457 |
Of course, the inclusion of the IPv6 prefix reply extension allows |
| 458 |
the home agent to indicate why a given IPv6 prefix request extension |
| 459 |
was rejected. A detailed description of how the mobile node handles |
| 460 |
different IPv6 prefix reply extension code values and the absence of |
| 461 |
IPv6 prefix reply extensions is given in <a href="#section-3.5">Section 3.5</a>. |
| 462 |
|
| 463 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Home Agent Considerations</span> |
| 464 |
|
| 465 |
The dual-stack home agent defined in this specification is a Mobile |
| 466 |
IPv4 home agent in that, it MUST operate as defined in MIPv4 |
| 467 |
[<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>]. In addition to that, the following mechanisms are defined |
| 468 |
in this specification. |
| 469 |
|
| 470 |
For each IPv6 prefix request extension included in a valid |
| 471 |
registration request, a home agent that supports this specification |
| 472 |
SHOULD include a corresponding IPv6 prefix reply extension in the |
| 473 |
registration reply message. The home agent MUST NOT include more |
| 474 |
than one IPv6 prefix reply extension for the same prefix. For each |
| 475 |
accepted IPv6 prefix, the home agent MUST decide the tunneling mode |
| 476 |
it is going to use and set the code field of the IPv6 prefix reply |
| 477 |
extension to the appropriate value. The IPv6 prefix field of each of |
| 478 |
the IPv6 prefix reply extensions included in the registration reply |
| 479 |
MUST match the IPv6 prefix field of an IPv6 prefix request extension |
| 480 |
included in the corresponding registration request message. |
| 481 |
|
| 482 |
When the home agent sends a successful registration reply to the |
| 483 |
mobile node, with the code field of a corresponding IPv6 prefix reply |
| 484 |
extension set to one of the "registration accepted" values, the home |
| 485 |
agent indicates that the IPv6 prefix is registered for the lifetime |
| 486 |
granted for the binding. It also indicates the tunneling mode used |
| 487 |
i.e., tunneling to home address or care-of address, based on the |
| 488 |
value of the code field used in the IPv6 prefix reply extension. |
| 489 |
|
| 490 |
Note that since only IPv6 prefixes (and not addresses) are supported |
| 491 |
by this specification, there is no need for Duplicate Address |
| 492 |
Detection. The home agent, however, MUST check that registered |
| 493 |
prefixes are not overlapping so that all addresses under each |
| 494 |
registered prefix belong to a single mobile node at any one time. |
| 495 |
These prefixes MUST NOT appear as on-link to any other node (e.g., |
| 496 |
via Router Advertisements). |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. IPv6 Reachability</span> |
| 506 |
|
| 507 |
For each registered IPv6 prefix, the home agent MUST advertise its |
| 508 |
reachability as defined in NEMO <a href="./rfc3963#section-6.3">Section 6.3 of [RFC3963]</a>. |
| 509 |
|
| 510 |
<span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. Processing Intercepted IPv6 Packets</span> |
| 511 |
|
| 512 |
A dual-stack home agent that supports the IPv6 extensions defined in |
| 513 |
this specification MUST keep track of the following IPv6 related |
| 514 |
state for the mobile nodes it supports, in addition to the state |
| 515 |
defined in [<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>]. |
| 516 |
|
| 517 |
- Registered IPv6 prefix(es) and prefix length(s). |
| 518 |
|
| 519 |
- Tunneling mode for IPv6 traffic: |
| 520 |
|
| 521 |
- Tunnel to IPv4 HoA and accept IPv6 tunneled from IPv4 HoA. |
| 522 |
|
| 523 |
- Tunnel to CoA and accept IPv6 tunneled from CoA. |
| 524 |
|
| 525 |
When IPv6 traffic is encapsulated over the tunnel between the home |
| 526 |
agent (HA) and the mobile node's care-of address, the tunneling |
| 527 |
mechanism used should be the same as the mechanism negotiated by the |
| 528 |
Mobile IP header as defined in MIPv4 [<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>]. In that case, when |
| 529 |
IPinIP encapsulation is negotiated, IPv6 is tunneled over IPv4 |
| 530 |
according to [<a href="./rfc4213" title=""Basic Transition Mechanisms for IPv6 Hosts and Routers"">RFC4213</a>]. Generic Routing Encapsulation (GRE) also |
| 531 |
allows tunneling of IPv6 packets by setting the Protocol Type |
| 532 |
[<a href="./rfc2784" title=""Generic Routing Encapsulation (GRE)"">RFC2784</a>] field, to the appropriate payload type defined for IPv6 by |
| 533 |
IANA. Minimal Encapsulation [<a href="./rfc2004" title=""Minimal Encapsulation within IP"">RFC2004</a>] cannot be used, since the |
| 534 |
second (inner) IP header is IPv6, which is not supported by |
| 535 |
[<a href="./rfc2004" title=""Minimal Encapsulation within IP"">RFC2004</a>]. |
| 536 |
|
| 537 |
When IPv6 traffic is encapsulated over the tunnel between the HA and |
| 538 |
the mobile node's home address, IPv6 is always tunneled over IPv4 |
| 539 |
according to [<a href="./rfc4213" title=""Basic Transition Mechanisms for IPv6 Hosts and Routers"">RFC4213</a>]. The resulting IPv4 packet is then delivered |
| 540 |
just like any other IPv4 packet addressed to the IPv4 HoA (using the |
| 541 |
tunneling for normal IPv4 traffic, possibly going via the foreign |
| 542 |
agent (FA)). |
| 543 |
|
| 544 |
Tunneling mode selection for IPv6 traffic depends on the following |
| 545 |
parameters in a successful registration request: |
| 546 |
|
| 547 |
1) A registration request is received with one or more IPv6 prefix |
| 548 |
request extensions. An IPv6 tunneling mode extension is not |
| 549 |
included. |
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 559 |
|
| 560 |
|
| 561 |
All IPv6 packets destined to the registered IPv6 prefix(es) |
| 562 |
MUST be tunneled by the home agent to the registered IPv4 home |
| 563 |
address of the mobile node. The home agent first encapsulates |
| 564 |
the IPv6 packet, addressing it to the mobile node's IPv4 home |
| 565 |
address, and then tunnels this encapsulated packet to the |
| 566 |
foreign agent. This extra level of encapsulation is required |
| 567 |
so that IPv6 routing remains transparent to a foreign agent |
| 568 |
that does not support IPv6. When received by the foreign |
| 569 |
agent, the unicast encapsulated packet is de-tunneled and |
| 570 |
delivered to the mobile node in the same way as any other |
| 571 |
packet. The mobile node must decapsulate the received IPv4 |
| 572 |
packet in order to recover the original IPv6 packet. |
| 573 |
|
| 574 |
Additionally, the home agent MUST be prepared to accept |
| 575 |
reverse-tunneled packets from the IPv4 home address of the |
| 576 |
mobile node encapsulating IPv6 packets sent by that mobile |
| 577 |
node. |
| 578 |
|
| 579 |
2) A registration request is received with one or more IPv6 prefix |
| 580 |
request extensions. An IPv6 tunneling mode extension is |
| 581 |
included. |
| 582 |
|
| 583 |
All IPv6 packets destined to the registered IPv6 prefix(es) |
| 584 |
SHOULD be tunneled by the home agent to the registered care-of |
| 585 |
address of the mobile node. Additionally, the home agent |
| 586 |
SHOULD be prepared to accept reverse-tunneled packets from the |
| 587 |
care-of address of the mobile node encapsulating IPv6 packets |
| 588 |
sent by that mobile node. The home agent MAY ignore the |
| 589 |
presence of the IPv6 tunneling mode extension and act as in |
| 590 |
case (1) above. |
| 591 |
|
| 592 |
The home agent MUST check that all inner IPv6 packets received from |
| 593 |
the mobile node over a tunnel with the mobile node's home address or |
| 594 |
the care-of address as the outer source address, include a source |
| 595 |
address that falls under the registered IPv6 prefix(es) for that |
| 596 |
mobile node. If the source address of the outer header of a tunneled |
| 597 |
packet is not the registered IPv4 care-of address or the registered |
| 598 |
IPv4 home addresses, the packet SHOULD be dropped. If the source |
| 599 |
address of the inner header of an tunneled packet does not match any |
| 600 |
of the registered prefixes, the packet SHOULD be dropped. |
| 601 |
|
| 602 |
Multicast packets addressed to a group to which the mobile node has |
| 603 |
successfully subscribed, MUST be tunneled to the mobile node. |
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h4"><a class="selflink" id="section-3.3.3" href="#section-3.3.3">3.3.3</a>. IPv6 Multicast Membership Control</span> |
| 618 |
|
| 619 |
IPv6 multicast membership control is provided as defined in MIPv6 |
| 620 |
<a href="./rfc3775#section-10.4.3">[RFC3775], Section 10.4.3</a>. The only clarification required for the |
| 621 |
purpose of this specification is that all Multicast Listener |
| 622 |
Discovery (MLD) [<a href="./rfc2710" title=""Multicast Listener Discovery (MLD) for IPv6"">RFC2710</a>] or MLDv2 [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>] messages between the |
| 623 |
mobile node and the home agent MUST be tunneled over an IPv4 tunnel |
| 624 |
between the mobile node's IPv4 home address and the home agent's IPv4 |
| 625 |
address, bypassing the foreign agent. Note that if tunneling to the |
| 626 |
care-of address has been negotiated for other traffic, then the rest |
| 627 |
of the traffic continues using this tunnel. |
| 628 |
|
| 629 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Foreign Agent Considerations</span> |
| 630 |
|
| 631 |
This specification does not affect the operation of the foreign |
| 632 |
agent. |
| 633 |
|
| 634 |
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Mobile Node Considerations</span> |
| 635 |
|
| 636 |
A dual-stack mobile node that supports the extensions described in |
| 637 |
this document MAY use these extensions to register its IPv6 |
| 638 |
prefix(es) while moving between access routers. |
| 639 |
|
| 640 |
The mobile node MAY include one or more IPv6 prefix request |
| 641 |
extension(s) in the registration request. |
| 642 |
|
| 643 |
In this case, the mobile node MUST take the following action |
| 644 |
depending on the extensions included in the registration reply it |
| 645 |
receives in response to the registration request: |
| 646 |
|
| 647 |
1) The registration reply does not include any IPv6 prefix reply |
| 648 |
extensions. |
| 649 |
|
| 650 |
The mobile node MUST assume that the home agent does not |
| 651 |
support the extensions defined in this specification. The |
| 652 |
mobile node SHOULD continue to operate according to MIPv4 |
| 653 |
[<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>]. |
| 654 |
|
| 655 |
2) The registration reply includes one or more IPv6 prefix reply |
| 656 |
extensions. |
| 657 |
|
| 658 |
The mobile node MUST match each IPv6 prefix reply extension |
| 659 |
with one of the IPv6 prefix request extensions included |
| 660 |
earlier in the corresponding registration request message. |
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 671 |
|
| 672 |
|
| 673 |
If a matching IPv6 prefix reply extension is not included for |
| 674 |
one or more of corresponding IPv6 prefix request extensions |
| 675 |
included in the registration request message, the mobile node |
| 676 |
MUST assume that these IPv6 prefixes are rejected. |
| 677 |
|
| 678 |
For each matching IPv6 prefix reply extension, the mobile node |
| 679 |
MUST inspect the code field. If the field is set to a |
| 680 |
rejection code, then the corresponding IPv6 prefix |
| 681 |
registration has been rejected. If the code field is set to |
| 682 |
an acceptance code, then the corresponding IPv6 prefix |
| 683 |
registration has been accepted. |
| 684 |
|
| 685 |
If the code field is set to "0", then the mobile node MUST be |
| 686 |
prepared to send/receive IPv6 packets encapsulated in the |
| 687 |
bidirectional tunnel between the home agent address and the |
| 688 |
registered IPv4 home address of the mobile node. |
| 689 |
|
| 690 |
If the code field is set to "1", then the mobile node MUST act |
| 691 |
as follows: |
| 692 |
|
| 693 |
- Assuming the co-located care-of address mode is used, the |
| 694 |
mobile node MUST be prepared to send/receive IPv6 packets |
| 695 |
over the bidirectional tunnel between the home agent |
| 696 |
address and its co-located care-of address. Otherwise, the |
| 697 |
mobile node SHOULD act as in the case where the code field |
| 698 |
is set to "0". |
| 699 |
|
| 700 |
The mobile node SHOULD include exactly one IPv6 tunneling mode |
| 701 |
extension if it uses the co-located care-of address model and it |
| 702 |
wants to request that IPv6 packets are tunneled to its co-located |
| 703 |
care-of address. If the mobile node uses the co-located care-of |
| 704 |
address model but it does not include the IPv6 tunneling mode |
| 705 |
extension, the home agent will tunnel IPv6 traffic to the mobile |
| 706 |
node's IPv4 home address. The mobile node MUST NOT include an IPv6 |
| 707 |
tunneling mode extension if it uses the foreign agent care-of address |
| 708 |
mode of operation. Note that if the mobile node includes an IPv6 |
| 709 |
tunneling mode extension in this case, IPv6 packets could be tunneled |
| 710 |
to the FA by the HA. The FA is then likely to drop them since it |
| 711 |
will not have appropriate state to process them. |
| 712 |
|
| 713 |
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Tunneling Impacts</span> |
| 714 |
|
| 715 |
When IPv6 runs over an IPv4 tunnel, the IPv6 tunnel endpoints can |
| 716 |
treat the IPv4 tunnel as a single hop link as defined in [<a href="./rfc4213" title=""Basic Transition Mechanisms for IPv6 Hosts and Routers"">RFC4213</a>]. |
| 717 |
The two tunnel endpoints, e.g., mobile node and home agent, MUST |
| 718 |
configure link-local IPv6 addresses as defined in <a href="#section-3.7">Section 3.7</a> of |
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 727 |
|
| 728 |
|
| 729 |
[<a href="./rfc4213" title=""Basic Transition Mechanisms for IPv6 Hosts and Routers"">RFC4213</a>], while they MUST also adhere to the neighbor discovery |
| 730 |
requirements of the same specification, <a href="#section-3.8">Section 3.8</a>, and the hop |
| 731 |
limit requirements of <a href="#section-3.3">Section 3.3</a>. |
| 732 |
|
| 733 |
With respect to the Tunnel MTU, an implementation MUST support the |
| 734 |
Static Tunnel MTU approach as defined in <a href="./rfc4213#section-3.2">Section 3.2 of [RFC4213]</a>. |
| 735 |
Implementation and use of the Dynamic Tunnel MTU method defined in |
| 736 |
the same section of [<a href="./rfc4213" title=""Basic Transition Mechanisms for IPv6 Hosts and Routers"">RFC4213</a>] is OPTIONAL. |
| 737 |
|
| 738 |
To accommodate traffic that uses Explicit Congestion Notification |
| 739 |
(ECN), it is RECOMMENDED that the ECN and Diffserv Code Point (DSCP) |
| 740 |
information is copied between the inner and outer header as defined |
| 741 |
in [<a href="./rfc3168" title=""The Addition of Explicit Congestion Notification (ECN) to IP"">RFC3168</a>] and [<a href="./rfc2983" title=""Differentiated Services and Tunnels"">RFC2983</a>]. It is RECOMMENDED that the full- |
| 742 |
functionality option defined in <a href="./rfc3168#section-9.1.1">Section 9.1.1 of [RFC3168]</a> be used to |
| 743 |
deal with ECN. |
| 744 |
|
| 745 |
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. IPv6 Prefixes</span> |
| 746 |
|
| 747 |
An implementation can use any number of mechanisms to allocate IPv6 |
| 748 |
prefixes to a mobile node. Once one or more IPv6 prefixes are |
| 749 |
allocated, they can be registered using the extensions and mechanism |
| 750 |
already described in this specification. |
| 751 |
|
| 752 |
How a home agent decides to accept an IPv6 prefix for a given mobile |
| 753 |
node is out of scope of this specification. Local configuration or |
| 754 |
external authorization via an authorization system, e.g., Diameter |
| 755 |
[<a href="./rfc3588" title=""Diameter Base Protocol"">RFC3588</a>], or other mechanisms may be used to make such |
| 756 |
determination. |
| 757 |
|
| 758 |
<span class="h4"><a class="selflink" id="section-3.7.1" href="#section-3.7.1">3.7.1</a>. Dynamic IPv6 Prefix Delegation</span> |
| 759 |
|
| 760 |
A dual-stack mobile node MAY use prefix delegation as defined in |
| 761 |
DHCPv6 Prefix Delegation [<a href="./rfc3633" title=""IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6"">RFC3633</a>] to get access to IPv6 prefixes. |
| 762 |
In that case, if the mobile node is not directly attached to its home |
| 763 |
agent, the mobile node MUST first register its IPv4 home address as |
| 764 |
per MIPv4 [<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>]. When that is done, the mobile node can generate |
| 765 |
a link-local IPv6 address as per <a href="./rfc4213#section-3.7">Section 3.7 of [RFC4213]</a>. The |
| 766 |
mobile node then sends a registration request to its home agent, |
| 767 |
including an IPv6 prefix request extension with the prefix length |
| 768 |
field set to 255 and setting the Mobile IPv6 Network Prefix field to |
| 769 |
the locally generated link-local address. If the registration reply |
| 770 |
message includes an IPv6 prefix reply extension with the code field |
| 771 |
set to a success code, the mobile node can use the tunnel to send and |
| 772 |
receive IPv6 link-local packets. The mobile node can now send DHCPv6 |
| 773 |
messages according to [<a href="./rfc3633" title=""IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6"">RFC3633</a>]. All IPv6 messages at this stage |
| 774 |
MUST be tunneled over the IPv4 tunnel between the mobile node's IPv4 |
| 775 |
home address and the home agent's IPv4 address. |
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 783 |
|
| 784 |
|
| 785 |
Once prefixes are delegated, and assuming explicit mode is used, the |
| 786 |
mobile node SHOULD send a registration request with the appropriate |
| 787 |
IPv6 prefix request extensions to the home agent to register the |
| 788 |
delegated prefixes. |
| 789 |
|
| 790 |
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. Deregistration of IPv6 Prefix</span> |
| 791 |
|
| 792 |
The mobile IP registration lifetime included in the registration |
| 793 |
request header is valid for all the bindings created by the |
| 794 |
registration request, which may include bindings for IPv6 prefix(es). |
| 795 |
|
| 796 |
A registration request with a zero lifetime can be used to remove all |
| 797 |
bindings from the home agent. |
| 798 |
|
| 799 |
A re-registration request with non-zero lifetime can be used to |
| 800 |
deregister some of the registered IPv6 prefixes by not including |
| 801 |
corresponding IPv6 prefix request extensions in the registration |
| 802 |
request message. |
| 803 |
|
| 804 |
<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a>. Registration with a Private CoA</span> |
| 805 |
|
| 806 |
If the care-of address is a private address, then Mobile IP NAT |
| 807 |
Traversal as [<a href="./rfc3519" title=""Mobile IP Traversal of Network Address Translation (NAT) Devices"">RFC3519</a>] MAY be used in combination with the extensions |
| 808 |
described in this specification. In that case, to transport IPv6 |
| 809 |
packets, the next header field of the Mobile Tunnel Data message |
| 810 |
header [<a href="./rfc3519" title=""Mobile IP Traversal of Network Address Translation (NAT) Devices"">RFC3519</a>] MUST be set to the value for IPv6. Note that in |
| 811 |
that case, the encapsulation field of the UDP Tunnel Request |
| 812 |
Extension defined in [<a href="./rfc3519" title=""Mobile IP Traversal of Network Address Translation (NAT) Devices"">RFC3519</a>] MUST be set to zero. |
| 813 |
|
| 814 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span> |
| 815 |
|
| 816 |
This specification operates in the security constraints and |
| 817 |
requirements of [<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>]. It extends the operations defined in |
| 818 |
[<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>] for IPv4 home addresses to cover home IPv6 prefixes and |
| 819 |
provides the same level of security for both IP address versions. |
| 820 |
|
| 821 |
Home agents MUST perform appropriate checks for reverse-tunneled IPv6 |
| 822 |
packets similar to what is defined in [<a href="./rfc3024" title=""Reverse Tunneling for Mobile IP, revised"">RFC3024</a>] for IPv4 packets. |
| 823 |
The check defined in [<a href="./rfc3024" title=""Reverse Tunneling for Mobile IP, revised"">RFC3024</a>] requires that the outer header's |
| 824 |
source address is set to a registered care-of address for the mobile |
| 825 |
node and as such the same check protects from attacks whether the |
| 826 |
encapsulated (inner) header is IPv4 or IPv6. |
| 827 |
|
| 828 |
In addition to that, the home agent MUST check that the source |
| 829 |
address of the inner header is a registered IPv4 home address or IPv6 |
| 830 |
prefix for this mobile node. If that is not the case, the home agent |
| 831 |
SHOULD silently discard the packet and log the event as a security |
| 832 |
exception. |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 839 |
|
| 840 |
|
| 841 |
Security devices should look for IPv6 packets encapsulated over IPv4 |
| 842 |
either directly to the mobile node's care-of address or via double |
| 843 |
encapsulation first to the mobile node's IPv4 home address and then |
| 844 |
to the mobile node's care-of address. Interactions with Mobile IPv4 |
| 845 |
and IPsec have been covered elsewhere, for instance in [<a href="./rfc5265" title=""Mobile IPv4 Traversal across IPsec-Based VPN Gateways"">RFC5265</a>] and |
| 846 |
[<a href="./rfc5266" title=""Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE)"">RFC5266</a>]. |
| 847 |
|
| 848 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span> |
| 849 |
|
| 850 |
A new type number (152) for DSMIPv4 extensions has been registered |
| 851 |
from the space of numbers for skippable mobility extensions (i.e., |
| 852 |
128-255), defined for Mobile IPv4 [<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>]. This registry is |
| 853 |
available from <a href="http://www.iana.org">http://www.iana.org</a> under "Extensions appearing in |
| 854 |
Mobile IP control messages". |
| 855 |
|
| 856 |
A new subtype space for the type number of this extension has been |
| 857 |
created: "DSMIPv4 Extension subtypes". The subtype values 1, 2, and |
| 858 |
3 are defined in this specification, while the rest of the subtypes |
| 859 |
are reserved and available for allocation based on Expert Review. |
| 860 |
|
| 861 |
Finally, a new space for the code field of the IPv6 prefix reply |
| 862 |
extension has been created: "IPv6 Prefix Reply Extension Codes". |
| 863 |
Values 0, 1, 8, and 9 are defined in this specification. Values 2-7 |
| 864 |
are reserved for accept codes, and values 10-255 are reserved for |
| 865 |
reject codes. |
| 866 |
|
| 867 |
Similar to the procedures specified for Mobile IPv4 [<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>] number |
| 868 |
spaces, future allocations from the two number spaces require Expert |
| 869 |
Review [<a href="./rfc5226" title="">RFC5226</a>]. |
| 870 |
|
| 871 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span> |
| 872 |
|
| 873 |
Thanks to Pat Calhoun, Paal Engelstad, Tom Hiller, and Pete McCann |
| 874 |
for earlier work on this subject. Thanks also to Alex Petrescu for |
| 875 |
various suggestions. Special thanks also to Sri Gundavelli and Kent |
| 876 |
Leung for their thorough review and suggestions. |
| 877 |
|
| 878 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 879 |
|
| 880 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span> |
| 881 |
|
| 882 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 883 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 884 |
|
| 885 |
[<a id="ref-RFC2460">RFC2460</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6 |
| 886 |
(IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, December 1998. |
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 895 |
|
| 896 |
|
| 897 |
[<a id="ref-RFC3024">RFC3024</a>] Montenegro, G., "Reverse Tunneling for Mobile IP, |
| 898 |
revised", <a href="./rfc3024">RFC 3024</a>, January 2001. |
| 899 |
|
| 900 |
[<a id="ref-RFC3344">RFC3344</a>] Perkins, C., "IP Mobility Support for IPv4", <a href="./rfc3344">RFC 3344</a>, |
| 901 |
August 2002. |
| 902 |
|
| 903 |
[<a id="ref-RFC3519">RFC3519</a>] Levkowetz, H. and S. Vaarala, "Mobile IP Traversal of |
| 904 |
Network Address Translation (NAT) Devices", <a href="./rfc3519">RFC 3519</a>, |
| 905 |
April 2003. |
| 906 |
|
| 907 |
[<a id="ref-RFC3633">RFC3633</a>] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic |
| 908 |
Host Configuration Protocol (DHCP) version 6", <a href="./rfc3633">RFC 3633</a>, |
| 909 |
December 2003. |
| 910 |
|
| 911 |
[<a id="ref-RFC3775">RFC3775</a>] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support |
| 912 |
in IPv6", <a href="./rfc3775">RFC 3775</a>, June 2004. |
| 913 |
|
| 914 |
[<a id="ref-RFC3963">RFC3963</a>] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. |
| 915 |
Thubert, "Network Mobility (NEMO) Basic Support Protocol", |
| 916 |
<a href="./rfc3963">RFC 3963</a>, January 2005. |
| 917 |
|
| 918 |
[<a id="ref-RFC4213">RFC4213</a>] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms |
| 919 |
for IPv6 Hosts and Routers", <a href="./rfc4213">RFC 4213</a>, October 2005. |
| 920 |
|
| 921 |
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an |
| 922 |
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, |
| 923 |
May 2008. |
| 924 |
|
| 925 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span> |
| 926 |
|
| 927 |
[<a id="ref-RFC2004">RFC2004</a>] Perkins, C., "Minimal Encapsulation within IP", <a href="./rfc2004">RFC 2004</a>, |
| 928 |
October 1996. |
| 929 |
|
| 930 |
[<a id="ref-RFC2710">RFC2710</a>] Deering, S., Fenner, W., and B. Haberman, "Multicast |
| 931 |
Listener Discovery (MLD) for IPv6", <a href="./rfc2710">RFC 2710</a>, |
| 932 |
October 1999. |
| 933 |
|
| 934 |
[<a id="ref-RFC2784">RFC2784</a>] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. |
| 935 |
Traina, "Generic Routing Encapsulation (GRE)", <a href="./rfc2784">RFC 2784</a>, |
| 936 |
March 2000. |
| 937 |
|
| 938 |
[<a id="ref-RFC2983">RFC2983</a>] Black, D., "Differentiated Services and Tunnels", |
| 939 |
<a href="./rfc2983">RFC 2983</a>, October 2000. |
| 940 |
|
| 941 |
[<a id="ref-RFC3168">RFC3168</a>] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition |
| 942 |
of Explicit Congestion Notification (ECN) to IP", |
| 943 |
<a href="./rfc3168">RFC 3168</a>, September 2001. |
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Tsirtsis, et al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc5454">RFC 5454</a> Dual-Stack Mobile IPv4 March 2009</span> |
| 951 |
|
| 952 |
|
| 953 |
[<a id="ref-RFC3588">RFC3588</a>] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. |
| 954 |
Arkko, "Diameter Base Protocol", <a href="./rfc3588">RFC 3588</a>, September 2003. |
| 955 |
|
| 956 |
[<a id="ref-RFC3810">RFC3810</a>] Vida, R. and L. Costa, "Multicast Listener Discovery |
| 957 |
Version 2 (MLDv2) for IPv6", <a href="./rfc3810">RFC 3810</a>, June 2004. |
| 958 |
|
| 959 |
[<a id="ref-RFC5265">RFC5265</a>] Vaarala, S. and E. Klovning, "Mobile IPv4 Traversal across |
| 960 |
IPsec-Based VPN Gateways", <a href="./rfc5265">RFC 5265</a>, June 2008. |
| 961 |
|
| 962 |
[<a id="ref-RFC5266">RFC5266</a>] Devarapalli, V. and P. Eronen, "Secure Connectivity and |
| 963 |
Mobility Using Mobile IPv4 and IKEv2 Mobility and |
| 964 |
Multihoming (MOBIKE)", <a href="https://www.rfc-editor.org/bcp/bcp136">BCP 136</a>, <a href="./rfc5266">RFC 5266</a>, June 2008. |
| 965 |
|
| 966 |
Authors' Addresses |
| 967 |
|
| 968 |
George Tsirtsis |
| 969 |
Qualcomm |
| 970 |
|
| 971 |
EMail: [email protected] |
| 972 |
|
| 973 |
|
| 974 |
Vincent Park |
| 975 |
Qualcomm |
| 976 |
|
| 977 |
Phone: +908-947-7084 |
| 978 |
EMail: [email protected] |
| 979 |
|
| 980 |
|
| 981 |
Hesham Soliman |
| 982 |
Elevate Technologies |
| 983 |
|
| 984 |
Phone: +614-111-410-445 |
| 985 |
EMail: [email protected] |
| 986 |
|
| 987 |
|
| 988 |
|
| 989 |
|
| 990 |
|
| 991 |
|
| 992 |
|
| 993 |
|
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
Tsirtsis, et al. Standards Track [Page 18] |
| 1005 |
</pre> |