Debian Codegraph @

rfc4988.html

raw
1 <pre>Network Working Group R. Koodli
2 Request for Comments: 4988 C. Perkins
3 Category: Experimental Nokia Siemens Networks
4 October 2007
5
6
7 <span class="h1">Mobile IPv4 Fast Handovers</span>
8
9 Status of This Memo
10
11 This memo defines an Experimental Protocol for the Internet
12 community. It does not specify an Internet standard of any kind.
13 Discussion and suggestions for improvement are requested.
14 Distribution of this memo is unlimited.
15
16 Abstract
17
18 This document adapts the Mobile IPv6 Fast Handovers to improve delay
19 and packet loss resulting from Mobile IPv4 handover operations.
20 Specifically, this document addresses movement detection, IP address
21 configuration, and location update latencies during a handover. For
22 reducing the IP address configuration latency, the document proposes
23 that the new Care-of Address is always made to be the new access
24 router's IP address.
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Koodli &amp; Perkins Experimental [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</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-2">2</a>. Terminology .....................................................<a href="#page-4">4</a>
61 <a href="#section-3">3</a>. Factors Affecting Handover ......................................<a href="#page-5">5</a>
62 <a href="#section-4">4</a>. Protocol ........................................................<a href="#page-6">6</a>
63 <a href="#section-4.1">4.1</a>. Overview ...................................................<a href="#page-6">6</a>
64 <a href="#section-4.2">4.2</a>. Operation ..................................................<a href="#page-7">7</a>
65 <a href="#section-5">5</a>. Message Formats ................................................<a href="#page-10">10</a>
66 <a href="#section-5.1">5.1</a>. Fast Binding Update (FBU) .................................<a href="#page-10">10</a>
67 <a href="#section-5.2">5.2</a>. Fast Binding Acknowledgment (FBAck) .......................<a href="#page-12">12</a>
68 <a href="#section-5.3">5.3</a>. Router Solicitation for Proxy Advertisement (RtSolPr) .....<a href="#page-13">13</a>
69 <a href="#section-5.4">5.4</a>. Proxy Router Advertisement (PrRtAdv) ......................<a href="#page-14">14</a>
70 <a href="#section-5.5">5.5</a>. Handover Initiate (HI) ....................................<a href="#page-17">17</a>
71 <a href="#section-5.6">5.6</a>. Handover Acknowledge (HAck) ...............................<a href="#page-19">19</a>
72 <a href="#section-6">6</a>. Option Formats .................................................<a href="#page-20">20</a>
73 <a href="#section-6.1">6.1</a>. Link-Layer Address Option Format ..........................<a href="#page-20">20</a>
74 <a href="#section-6.2">6.2</a>. New IPv4 Address Option Format ............................<a href="#page-22">22</a>
75 <a href="#section-6.3">6.3</a>. New Router Prefix Information Option ......................<a href="#page-22">22</a>
76 <a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-23">23</a>
77 <a href="#section-8">8</a>. IANA Considerations ............................................<a href="#page-24">24</a>
78 <a href="#section-9">9</a>. Acknowledgments ................................................<a href="#page-25">25</a>
79 <a href="#section-10">10</a>. References ....................................................<a href="#page-25">25</a>
80 <a href="#section-10.1">10.1</a>. Normative References .....................................<a href="#page-25">25</a>
81 <a href="#section-10.2">10.2</a>. Informative References ...................................<a href="#page-26">26</a>
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Koodli &amp; Perkins Experimental [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 This document adapts the fast handover specification [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>] to
116 IPv4 networks. The fast handover protocol specified in this document
117 is particularly interesting for operation over links such as IEEE 802
118 wireless links. Fast handovers are not typically needed for wired
119 media due to the relatively large delays attributable to establishing
120 new connections in today's wired networks. Mobile IPv4 [<a href="./rfc3344" title="&quot;IP Mobility Support for IPv4&quot;">rfc3344</a>]
121 registration messages are reused (with new type numbers) in this
122 document to enable faster implementation using existing Mobile IPv4
123 software. This document does not require link-layer triggers for
124 protocol operation, but performance will typically be enhanced by
125 using the appropriate triggers when they are available. This
126 document assumes that the reader is familiar with the basic operation
127 and terminology of Mobile IPv4 [<a href="./rfc3344" title="&quot;IP Mobility Support for IPv4&quot;">rfc3344</a>] and Fast Handovers for
128 Mobile IPv6 [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>].
129
130 The active agents that enable continued packet delivery to a mobile
131 node (MN) are the access routers on the networks that the mobile node
132 connects to. Handover means that the mobile node changes its network
133 connection, and we consider the scenario in which this change means
134 change in access routers. The mobile node utilizes the access
135 routers as default routers in the normal sense, but also as partners
136 in mobility management. Thus, when the mobile node moves to a new
137 network, it processes handover-related signaling in order to identify
138 and develop a relationship with a new access router. In this
139 document, we call the previous access router PAR and the new access
140 router NAR, consistent with the terminology in [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>]. Unless
141 otherwise mentioned, a PAR is also a Previous Foreign Agent (PFA) and
142 a NAR is also a New Foreign Agent (NFA).
143
144 On a particular network, a mobile node may obtain its IP address via
145 DHCP [<a href="./rfc2131" title="&quot;Dynamic Host Configuration Protocol&quot;">rfc2131</a>] (i.e., Co-located Care-of Address) or use the Foreign
146 Agent CoA. During a handover, the new CoA (NCoA) is always made to
147 be that of NAR. This allows a mobile node to receive and send
148 packets using its previous CoA (PCoA), so that delays resulting from
149 IP configuration (such as DHCP address acquisition delay) subsequent
150 to attaching to the new link are disengaged from affecting the
151 existing sessions.
152
153 Unlike in Mobile IPv6, a Mobile IPv4 host may rely on its Foreign
154 Agent to provide a Care-of Address. Using the protocol specified in
155 this document, the binding at the PAR is always established between
156 the on-link address the mobile node is using and a new CoA that it
157 can use on the NAR's link. When FA-CoA is used, the on-link address
158 is the MN's home address, not the FA-CoA itself, which needs to be
159
160
161
162
163
164 <span class="grey">Koodli &amp; Perkins Experimental [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
167
168
169 bound to the NCoA. So, when we say "a binding is established between
170 PCoA and NCoA", it is actually the home address of the mobile node
171 that is bound to the NCoA in the FA-CoA mode.
172
173 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
174 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
175 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
176
177 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
178
179 The terminology used in this document in based on [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>] and
180 [<a href="./rfc3344" title="&quot;IP Mobility Support for IPv4&quot;">rfc3344</a>]. We provide some definitions below for convenience.
181
182 Mobile Node (MN): A Mobile IPv4 host.
183
184 Access Point (AP): A Layer 2 device connected to an IP subnet that
185 offers wireless connectivity to an MN. An Access Point Identifier
186 (AP-ID) refers to the AP's L2 address. Sometimes, AP-ID is also
187 referred to as a Base Station Subsystem ID (BSSID).
188
189 Access Router (AR): The MN's default router.
190
191 Previous Access Router (PAR): The MN's default router prior to its
192 handover.
193
194 New Access Router (NAR): The MN's default router subsequent to its
195 handover.
196
197 Previous CoA (PCoA): The IP address of the MN valid on PAR's
198 subnet.
199
200 New CoA (NCoA): The MN's Care-of Address valid on NAR's subnet.
201
202 Handover: A process of terminating existing connectivity and
203 obtaining new IP connectivity.
204
205 (AP-ID, AR-Info) tuple: Contains an access router's L2 and IP
206 addresses, and the prefix valid on the interface to which the
207 Access Point (identified by AP-ID) is attached. The triplet
208 [Router's L2 address, Router's IP address, Prefix] is called
209 "AR-Info".
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Koodli &amp; Perkins Experimental [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
223
224
225 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Factors Affecting Handover</span>
226
227 Both link-layer operations and IP-layer procedures affect the
228 perceived handover performance. However, the overall performance is
229 also (always) a function of specific implementation of the technology
230 as well as the system configuration. This document only specifies IP
231 layer protocol operations. The purpose of this section is to provide
232 an illustration of events that affect handover performance, but it is
233 purely informative.
234
235 The IP-layer handover delay and packet loss are influenced by
236 latencies due to movement detection, IP address configuration, and
237 the Mobile IP registration procedure. Movement detection latency
238 comes from the need to reliably detect movement to a new subnet.
239 This is a function of the frequency of router advertisements as well
240 as default agent reachability. IP address configuration latency
241 depends on the particular IP CoA being used. If co-located mode with
242 DHCP is used, the latency is quite likely going to be higher and
243 potentially unacceptable for real-time applications such as Voice
244 over IP. Finally, the Mobile IP registration procedure introduces a
245 round-trip of delay between the Mobile Node and its Home Agent over
246 the Internet. This delay is incurred after the mobile node performs
247 movement detection and IP configuration.
248
249 Underlying the IP operations are link-layer procedures. These are
250 technology-specific. For instance, in IEEE 802.11, the handover
251 operation typically involves scanning access points over all
252 available channels, selecting a suitable access point, and
253 associating with it. It may also involve performing access control
254 operations such as those specified in IEEE 802.1X [<a href="#ref-ieee-802.1x" title="&quot;IEEE Standards for Local and Metropolitan Area Networks: Port-based Network Access Control, IEEE Std 802.1X-2001&quot;">ieee-802.1x</a>].
255 These delays contribute to the handover performance. See [<a href="#ref-fh-ccr" title="&quot;Fast Handovers and Context Transfers in Mobile Networks&quot;">fh-ccr</a>]
256 and Chapters 20 and 22 in [<a href="#ref-mi-book" title="&quot;Mobile Internetworking with IPv6: Concepts, Principles and Practices&quot;">mi-book</a>]. Optimizations are being
257 proposed for standardization in IEEE; for instance, see
258 [<a href="#ref-ieee-802.11r" title="&quot;IEEE Standard for Local and Metropolitan Area Networks: Fast Roaming/Fast BSS Transition, IEEE Std 802.11r&quot;">ieee-802.11r</a>] and [<a href="#ref-ieee-802.21">ieee-802.21</a>]. Together with appropriate
259 implementation techniques, these optimizations can provide the
260 required level of delay support at the link-layer for real-time
261 applications.
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Koodli &amp; Perkins Experimental [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
279
280
281 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Protocol</span>
282
283 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Overview</span>
284
285 The design of the protocol is the same as for Mobile IPv6 [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>].
286 Readers should consult [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>] for details; here we provide a
287 summary.
288
289 The protocol avoids the delay due to movement detection and IP
290 configuration and disengages Mobile IP registration delay from the
291 time-critical path. The protocol provides the surrounding network
292 neighborhood information so that a mobile node can determine whether
293 it is moving to a new subnet even before the handover. The
294 information provided and the signaling exchanged between the local
295 mobility agents allow the mobile node to send and receive packets
296 immediately after handover. In order to disengage the Mobile IP
297 registration latency, the protocol provides routing support for the
298 continued use of a mobile node's previous CoA.
299
300 After a mobile node obtains its IPv4 Care-of Address, it builds a
301 neighborhood access point and subnet map using the Router
302 Solicitation for Proxy Advertisement (RtSolPr) and Proxy Router
303 Advertisement (PrRtAdv) messages. The mobile node may scan for
304 access points (APs) based on the configuration policy in operation
305 for its wireless network interface. If a scan detects a new AP, the
306 mobile node resolves the corresponding AP Identifier to subnet
307 information using the RtSolPr and PrRtAdv messages mentioned above.
308
309 At some point, the mobile node decides to undergo handover. It sends
310 a Fast Binding Update (FBU) message to PAR from the previous link or
311 from the new link. An FBU message enables creation of a binding
312 between the mobile node's previous CoA and the new CoA.
313
314 The coordination between the access routers is done by way of the
315 Handover Initiate (HI) and Handover Acknowledge (HAck) messages
316 defined in [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>]. After these signals have been exchanged
317 between the previous and new access routers (PAR and NAR), data
318 arriving at PAR will be tunneled to NAR for delivery to the newly
319 arrived mobile node. The purpose of HI is to securely deliver the
320 routing parameters for establishing this tunnel. The tunnel is
321 created by the access routers in response to the delivery of the FBU
322 from the mobile node.
323
324
325
326
327
328
329
330
331
332 <span class="grey">Koodli &amp; Perkins Experimental [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
335
336
337 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Operation</span>
338
339 In response to a handover trigger or indication, the mobile node
340 sends a Fast Binding Update message to the Previous Access Router
341 (PAR) (see <a href="#section-5.1">Section 5.1</a>). Depending on the Mobile IP mode of
342 operation, the source IP address is either the Home Address (in FA
343 CoA mode) or co-located CoA (in CCoA mode). The FBU message SHOULD
344 (when possible) be sent while the mobile node is still connected to
345 PAR. When sent in this "predictive" mode, the fields in the FBU MUST
346 be set as follows:
347
348 The Home Address field is either the Home Address or the co-
349 located CoA whenever the mobile node has a co-located CoA.
350
351 The Home Agent field is set to PAR's IP address.
352
353 The Care-of Address field is the NAR's IP address (as discovered
354 via a PrRtAdv message).
355
356 The fields in the IP header MUST be set as follows:
357
358 The Destination IP address is PAR's IP address.
359
360 The Source IP address is either the Home Address or the co-located
361 CoA whenever the mobile node has a co-located CoA.
362
363 As a result of processing the FBU, PAR creates a binding between the
364 address given by the mobile node in the Home Address field and NAR's
365 IP address in its routing table. The PAR sends an FBack message (see
366 <a href="#section-5.2">Section 5.2</a>) as a response to the mobile node.
367
368 The timeline for the predictive mode of operation (adapted from
369 [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>]) is shown in Figure 1.
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Koodli &amp; Perkins Experimental [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
391
392
393 MN PAR NAR
394 | | |
395 |------RtSolPr-------&gt;| |
396 |&lt;-----PrRtAdv--------| |
397 | | |
398 |------FBU-----------&gt;|--------HI---------&gt;|
399 | |&lt;------HAck---------|
400 | &lt;--FBack---|--FBack---&gt; |
401 | | |
402 disconnect forward |
403 | packets===============&gt;|
404 | | |
405 | | |
406 connect | |
407 | | |
408 |--------- FBU ---------------------------&gt;|
409 |&lt;=================================== deliver packets
410 | | (including FBack)
411 | |&lt;-----FBU-----------|
412
413 Figure 1: Predictive Fast Handover
414
415 The mobile node sends the FBU, regardless of its previous
416 transmission, when attachment to a new link is detected. This
417 minimally allows NAR to detect the mobile node's attachment, but also
418 the retransmission of FBU when an FBack has not been received yet.
419 When sent in this "reactive" mode, the Destination IP address in the
420 IP header MUST be NAR's IP address; the rest of the fields in the FBU
421 are the same as in the "predictive" case.
422
423 When NAR receives FBU, it may already have processed the HI message
424 and created a host route entry for the mobile node, using either the
425 home address or the co-located care-of address as provided by PAR.
426 In that case, NAR SHOULD immediately forward arriving and buffered
427 packets as well as the FBAck message. In any case, NAR MUST forward
428 the contents of the FBU message, starting from the Type field, to
429 PAR; the Source and Destination IP addresses in the new packet now
430 contain the IP addresses of NAR and PAR, respectively.
431
432 The reactive mode of operation (adapted from [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>]) is
433 illustrated in Figure 2. Even though the Figure does not show the HI
434 and HAck messages illustrated in Figure 1, these messages could
435 already have been exchanged (in the case when the PAR has already
436 processed the FBU sent from the previous link); if not, the PAR sends
437 a HI message to the NAR. The FBack packet is forwarded by the NAR to
438 the MN along with the data packets.
439
440
441
442
443
444 <span class="grey">Koodli &amp; Perkins Experimental [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
447
448
449 MN PAR NAR
450 | | |
451 |------RtSolPr-------&gt;| |
452 |&lt;-----PrRtAdv--------| |
453 | | |
454 disconnect | |
455 | | |
456 | | |
457 connect | |
458 |-----------FBU-------|-------------------&gt;|
459 | |&lt;-----FBU-----------|
460 | |------FBack--------&gt;|
461 | forward |
462 | packets===============&gt;|
463 | | |
464 |&lt;=================================== deliver packets
465 | (including FBack)
466 | |
467
468 Figure 2: Reactive Fast Handover
469
470 The Handover Initiate (HI) and Handover Acknowledge (HAck) messages
471 serve to establish a bidirectional tunnel between the routers to
472 support packet forwarding for PCoA. The tunnel itself is established
473 as a response to the FBU message. The PAR sends the HI message with
474 Code = 0 when it receives FBU with source IP address set to PCoA.
475 The PAR sends HI with Code = 1 when it receives FBU with source IP
476 address not set to PCoA (i.e., when received from NAR). This allows
477 NAR to disambiguate HI message processing sent as a response to
478 predictive and reactive modes of operation. If NAR receives a HI
479 message with Code = 1, and it has already set up a host route entry
480 and a reverse tunnel for PCoA, it SHOULD still respond with a HAck
481 message, using an appropriate Code value defined in <a href="#section-5.6">Section 5.6</a>.
482
483 The protocol provides an option for NAR to return NCoA for use by the
484 mobile node. When NAR can provide an NCoA for exclusive use of the
485 mobile node, the address is supplied in the HAck message. The PAR
486 includes this NCoA in FBack. Exactly how NAR manages the address
487 pool from which it supplies NCoA is not specified in this document.
488 Nevertheless, the MN should be prepared to use this address instead
489 of performing DHCP or similar operations to obtain an IPv4 address.
490
491 Even though the mobile node can obtain this NCoA from the NAR, it is
492 unaware of the address at the time it sends an FBU. Hence, it binds
493 PCoA to NAR's IP address as before.
494
495
496
497
498
499
500 <span class="grey">Koodli &amp; Perkins Experimental [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
503
504
505 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Message Formats</span>
506
507 This section specifies the formats for messages used in this
508 protocol. The Code values below are the same as those in [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>],
509 and do not require any assignment from IANA.
510
511 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Fast Binding Update (FBU)</span>
512
513 The FBU format is bitwise identical to the Registration Request
514 format in [<a href="./rfc3344" title="&quot;IP Mobility Support for IPv4&quot;">rfc3344</a>]. The same destination port number, 434, is used,
515 but the FBU and FBAck messages in this specification have new message
516 type numbers.
517
518 0 1 2 3
519 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
520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
521 | Type |x|x|D|M|G|r|T|x| reserved | Lifetime |
522 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
523 | Home Address |
524 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
525 | Home Agent |
526 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
527 | Care-of Address |
528 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
529 | |
530 + Identification +
531 | |
532 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
533 | Extensions ...
534 +-+-+-+-+-+-+-+-
535
536 Figure 3: Fast Binding Update (FBU) Message
537
538 IP Fields:
539
540 Source address: The interface address from which the message is
541 sent. Either PCoA (co-located or Home Address), or NAR's IP
542 address (when forwarded from NAR to PAR).
543
544 Destination Address: The IP address of the Previous Access
545 Router (PAR) or the New Access Router (NAR).
546
547 Source Port: variable
548
549 Destination port: 434
550
551
552
553
554
555
556 <span class="grey">Koodli &amp; Perkins Experimental [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
559
560
561 Message Fields:
562
563 Type: 20
564
565 Flags: See [<a href="./rfc3344" title="&quot;IP Mobility Support for IPv4&quot;">rfc3344</a>]. The 'S' and 'B' flags in [<a href="./rfc3344" title="&quot;IP Mobility Support for IPv4&quot;">rfc3344</a>] are
566 sent as zero, and ignored on reception.
567
568 reserved: Sent as zero, ignored on reception
569
570 Lifetime: The number of seconds remaining before the binding
571 expires. This value MUST NOT exceed 10 seconds.
572
573 Home Address: MUST be either the co-located CoA or the Home
574 Address itself (in FA-CoA mode)
575
576 Home Agent: The Previous Access Router's global IP address
577
578 Care-of Address: The New Access Router's global IP address.
579 Even when a New CoA is provided to the MN (see <a href="#section-5.4">Section 5.4</a>),
580 NAR's IP address MUST be used for this field.
581
582 Identification: a 64-bit number used for matching an FBU with
583 FBack. Identical to usage in [<a href="./rfc3344" title="&quot;IP Mobility Support for IPv4&quot;">rfc3344</a>]
584
585 Extensions: MUST contain the MN-PAR Authentication Extension
586 (see <a href="#section-8">Section 8</a>)
587
588 The MN-PAR Authentication Extension is the Generalized Mobile IP
589 Authentication Extension in [<a href="./rfc4721" title="&quot;Mobile IPv4 Challenge/Response Extensions (Revised)&quot;">rfc4721</a>] with a new Subtype for MN-PAR
590 Authentication. The Authenticator field in the Generalized Mobile IP
591 Authentication Extension is calculated using a shared key between the
592 MN and the PAR. However, the key distribution itself is beyond the
593 scope of this document, and is assumed to be performed by other means
594 (for example, using [<a href="./rfc3957" title="&quot;Authentication, Authorization, and Accounting (AAA) Registration Keys for Mobile IPv4&quot;">rfc3957</a>]).
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Koodli &amp; Perkins Experimental [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
615
616
617 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Fast Binding Acknowledgment (FBAck)</span>
618
619 The FBAck format is bitwise identical to the Registration Reply
620 format in [<a href="./rfc3344" title="&quot;IP Mobility Support for IPv4&quot;">rfc3344</a>].
621
622 0 1 2 3
623 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
624 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
625 | Type | Code | reserved | Lifetime |
626 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
627 | Home Address |
628 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
629 | Home Agent |
630 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
631 | |
632 + Identification +
633 | |
634 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
635 | Extensions ...
636 +-+-+-+-+-+-+-+-
637
638 Figure 4: Fast Binding Acknowledgment (FBAck)
639
640 IP Fields:
641
642 Message Source address: Typically copied from the destination
643 address of the FBU message
644
645 Destination Address: Copied from the Source IP address in FBU
646 message
647
648 Source Port: variable
649
650 Destination port: Copied from the source port in FBU message
651
652 Message Fields:
653
654 Type: 21
655
656 Code: Indicates the result of processing FBU message.
657
658 0: FBU Accepted
659 1: FBU Accepted, NCoA supplied
660 128: FBU Not Accepted, reason unspecified
661 129: Administratively prohibited
662 130: Insufficient resources
663
664 reserved: Sent as zero, ignored on reception
665
666
667
668 <span class="grey">Koodli &amp; Perkins Experimental [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
671
672
673 Lifetime: The granted number of seconds remaining before
674 binding expires.
675
676 Home Address: either the co-located CoA or the Home Address
677 itself (in FA-Coa mode)
678
679 Home Agent: The Previous Access Router's global IP address
680
681 Identification: a 64-bit number used for matching FBU. Copied
682 from the field in FBU for which this FBack is a reply.
683
684 Extensions: The MN-PAR Authentication extension MUST be present
685 (see <a href="#section-8">Section 8</a>). In addition, a New IPv4 Address Option, with
686 Option-Code 2, MUST be present when NAR supplies the NCoA (see
687 <a href="#section-6.2">Section 6.2</a>).
688
689 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Router Solicitation for Proxy Advertisement (RtSolPr)</span>
690
691 Mobile Nodes send Router Solicitation for Proxy Advertisement in
692 order to prompt routers for Proxy Router Advertisements. All the
693 link-layer address options have the format defined in <a href="#section-6.1">Section 6.1</a>.
694 The message format and processing rules are identical to those
695 defined in [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>].
696
697 0 1 2 3
698 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
699 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
700 | Type | Code | Checksum |
701 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
702 | Subtype | Reserved | Identifier |
703 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
704 | Options ...
705 +-+-+-+-+-+-+-+-+-+-+-+-
706
707 Figure 5: Router Solicitation for Proxy Advertisement (RtSolPr)
708 Message
709
710 IP Fields:
711
712 Source Address: An IP address assigned to the sending interface
713
714 Destination Address: The address of the Access Router or the
715 all routers multicast address.
716
717 Time-to-Live: At least 1. See [<a href="./rfc1256" title="&quot;ICMP Router Discovery Messages&quot;">rfc1256</a>].
718
719
720
721
722
723
724 <span class="grey">Koodli &amp; Perkins Experimental [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
727
728
729 ICMP Fields:
730
731 Type: 41. See <a href="./rfc4065#section-3">Section&nbsp;3 in [rfc4065]</a>.
732
733 Code: 0
734
735 Checksum: The 16-bit one's complement of the one's complement
736 sum of the ICMP message, starting with the ICMP Type. For
737 computing the checksum, the Checksum and the Reserved fields
738 are set to 0. See [<a href="./rfc1256" title="&quot;ICMP Router Discovery Messages&quot;">rfc1256</a>].
739
740 Subtype: 6
741
742 Reserved: MUST be set to zero by the sender and ignored by the
743 receiver.
744
745 Identifier: MUST be set by the sender so that replies can be
746 matched to this Solicitation.
747
748 Valid Options:
749
750 New Access Point Link-layer Address: The link-layer address or
751 identification of the access point for which the MN requests
752 routing advertisement information. It MUST be included in all
753 RtSolPr messages. More than one such address or identifier can
754 be present. This field can also be a wildcard address (see
755 <a href="#section-6.1">Section 6.1</a>).
756
757 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Proxy Router Advertisement (PrRtAdv)</span>
758
759 Access routers send out a Proxy Router Advertisement message
760 gratuitously if the handover is network-initiated or as a response to
761 RtSolPr message from a mobile node, providing the link-layer address,
762 IP address, and subnet prefixes of neighboring access routers. All
763 the link-layer address options have the format defined in <a href="#section-6.1">Section</a>
764 <a href="#section-6.1">6.1</a>.
765
766 The message format and processing rules are identical to those
767 defined in [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>].
768
769
770
771
772
773
774
775
776
777
778
779
780 <span class="grey">Koodli &amp; Perkins Experimental [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
783
784
785 0 1 2 3
786 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
787 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
788 | Type | Code | Checksum |
789 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
790 | Subtype | Reserved | Identifier |
791 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
792 | Options ...
793 +-+-+-+-+-+-+-+-+-+-+-+-
794
795 Figure 6: Proxy Router Advertisement (PrRtAdv) Message
796
797 IP Fields:
798
799 Source Address: An IP address assigned to the sending interface
800
801 Destination Address: The Source Address of an invoking Router
802 Solicitation for Proxy Advertisement or the address of the node
803 the Access Router is instructing to handover.
804
805 Time-to-Live: At least 1. See [<a href="./rfc1256" title="&quot;ICMP Router Discovery Messages&quot;">rfc1256</a>].
806
807 ICMP Fields:
808
809 Type: 41. See <a href="./rfc4065#section-3">Section&nbsp;3 in [rfc4065]</a>.
810
811 Code 0, 1, 2, 3, or 4. See below.
812
813 Checksum: The 16-bit one's complement of the one's complement
814 sum of the ICMP message, starting with the ICMP Type. For
815 computing the checksum, the Checksum and the Reserved fields
816 are set to 0. See [<a href="./rfc1256" title="&quot;ICMP Router Discovery Messages&quot;">rfc1256</a>].
817
818 Subtype: 7
819
820 Reserved: MUST be set to zero by the sender and ignored by the
821 receiver.
822
823 Identifier: Copied from Router Solicitation for Proxy
824 Advertisement or set to Zero if unsolicited.
825
826 Valid Options in the following order:
827
828 New Access Point Link-layer Address: The link-layer address
829 (LLA) or identification of the access point. When there is no
830 wildcard in RtSolPr, this is copied from the LLA (for which the
831 router is supplying the [AP-ID, AR-Info] tuple) present in
832
833
834
835
836 <span class="grey">Koodli &amp; Perkins Experimental [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
839
840
841 RtSolPr. When a wildcard is present in RtSolPr, PAR uses its
842 neighborhood information to populate this field. This option
843 MUST be present.
844
845 New Router's Link-layer Address: The link-layer address of the
846 Access Router for which this message is proxied. This option
847 MUST be included when Code is 0 or 1.
848
849 New Router's IP Address: The IP address of NAR. This option
850 MUST be included when Code is 0 or 1.
851
852 New Router Prefix Information Option: The number of leading
853 bits that define the network number of the corresponding
854 Router's IP Address option (see above).
855
856 New CoA Option: MAY be present, typically when PrRtAdv is sent
857 unsolicited. PAR MAY compute new CoA by communicating with the
858 NAR or by means not specified in this document. In any case,
859 the MN should be prepared to use this address instead of
860 performing DHCP or similar operations to obtain an IPv4
861 address. Even when it uses the New CoA provided, the MN MUST
862 bind its current on-link address (PCoA) to that of NAR in the
863 FBU message.
864
865 A PrRtAdv with Code 0 means that the MN should use the [AP-ID,
866 AR-Info] tuple present in the options above. In this case, the
867 Option-Code field (see <a href="#section-6.1">Section 6.1</a>) in the New AP LLA option is 1,
868 reflecting the LLA of the access point for which the rest of the
869 options are related, and the Option-Code for the New Router's LLA
870 option is 3. Multiple tuples may be present.
871
872 A PrRtAdv with Code 1 means that the message is sent unsolicited. If
873 a New IPv4 option (see Figure 10) is present following the New Router
874 Prefix Information option (see <a href="#section-6.3">Section 6.3</a>), the MN SHOULD use the
875 supplied NCoA and send the FBU immediately or else stand to lose
876 service. This message acts as a network-initiated handover trigger.
877 The Option-Code field (see <a href="#section-6.1">Section 6.1</a>) in the New AP LLA option in
878 this case is 1 reflecting the LLA of the access point for which the
879 rest of the options are related.
880
881 A Proxy Router Advertisement with Code 2 means that no new router
882 information is present. The LLA option contains an Option-Code value
883 that indicates a specific reason (see <a href="#section-6.1">Section 6.1</a>).
884
885 A Proxy Router Advertisement with Code 3 means that new router
886 information is only present for a subset of access points requested.
887 The Option-Code values in the LLA option distinguish different
888 outcomes (see <a href="#section-6.1">Section 6.1</a>).
889
890
891
892 <span class="grey">Koodli &amp; Perkins Experimental [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
895
896
897 A Proxy Router Advertisement with Code 4 means that the subnet
898 information regarding neighboring access points is sent unsolicited,
899 but the message is not a handover trigger, unlike when the message is
900 sent with Code 1. Multiple tuples may be present.
901
902 When a wildcard AP identifier is supplied in the RtSolPr message, the
903 PrRtAdv message should include all available [Access Point
904 Identifier, Link-Layer Address option, Prefix Information Option]
905 tuples corresponding to the PAR's neighborhood.
906
907 The New CoA option may also be used when the PrRtAdv is sent as a
908 response to a RtSolPr message. However, the solicited RtSolPr and
909 PrRtAdv exchange for neighborhood discovery is logically decoupled
910 from the actual handover phase involving the FBU and FBack messages
911 (above) as well as HI and HAck messages (see below). This means the
912 access routers have to carefully manage the supplied address due to
913 the relative scarcity of addresses in IPv4.
914
915 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Handover Initiate (HI)</span>
916
917 The Handover Initiate (HI) is an ICMP message sent by an Access
918 Router (typically PAR) to another Access Router (typically NAR) to
919 initiate the process of a mobile node's handover.
920
921 The message format and processing rules are identical to those
922 defined in [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>].
923
924 0 1 2 3
925 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
926 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
927 | Type | Code | Checksum |
928 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
929 | Subtype |S|U| Reserved | Identifier |
930 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
931 | Options ...
932 +-+-+-+-+-+-+-+-+-+-+-+-
933
934 Figure 7: Handover Initiate (HI) Message
935
936 IP Fields:
937
938 Source Address: The IP address of the PAR
939
940 Destination Address: The IP address of the NAR
941
942 Time-to-Live: At least 1. See [<a href="./rfc1256" title="&quot;ICMP Router Discovery Messages&quot;">rfc1256</a>].
943
944
945
946
947
948 <span class="grey">Koodli &amp; Perkins Experimental [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
951
952
953 ICMP Fields:
954
955 Type: 41. See <a href="./rfc4065#section-3">Section&nbsp;3 in [rfc4065]</a>.
956
957 Code: 0 or 1. See below
958
959 Checksum: The 16-bit one's complement of the one's complement
960 sum of the ICMP message, starting with the ICMP Type. For
961 computing the checksum, the Checksum and the Reserved fields
962 are set to 0. See [<a href="./rfc1256" title="&quot;ICMP Router Discovery Messages&quot;">rfc1256</a>].
963
964 Subtype: 8
965
966 S: Assigned address configuration flag. When set, this message
967 requests a new CoA to be returned by the destination. May be
968 set when Code = 0. MUST be 0 when Code = 1.
969
970 U: Buffer flag. When set, the destination SHOULD buffer any
971 packets towards the node indicated in the options of this
972 message. Used when Code = 0, SHOULD be set to 0 when Code = 1.
973
974 Reserved: MUST be set to zero by the sender and ignored by the
975 receiver.
976
977 Identifier: MUST be set by the sender so replies can be matched
978 to this message.
979
980 Valid Options:
981
982 Link-layer address of MN: The link-layer address of the MN that
983 is undergoing handover to the destination (i.e., NAR). This
984 option MUST be included so that the destination can recognize
985 the MN.
986
987 Previous Care-of Address: The IP address used by the MN while
988 attached to the originating router. This option MUST be
989 included so that a host route can be established on the NAR.
990
991 New Care-of Address: This option MAY be present when the MN
992 wishes to use a new IP address when connected to the
993 destination. When the 'S' bit is set, NAR MAY provide this
994 address in HAck, in which case the MN should be prepared to use
995 this address instead of performing DHCP or similar operations
996 to obtain an IPv4 address.
997
998 PAR uses Code = 0 when it processes the FBU received with PCoA as
999 source IP address. PAR uses Code = 1 when the FBU is received with
1000 NAR's IP address as the source IP address.
1001
1002
1003
1004 <span class="grey">Koodli &amp; Perkins Experimental [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
1007
1008
1009 <span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. Handover Acknowledge (HAck)</span>
1010
1011 The Handover Acknowledgment message is a new ICMP message that MUST
1012 be sent (typically by NAR to PAR) as a reply to the Handover Initiate
1013 (HI) (see <a href="#section-5.5">Section 5.5</a>) message.
1014
1015 The message format and processing rules are identical to those
1016 defined in [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>].
1017
1018 0 1 2 3
1019 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
1020 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1021 | Type | Code | Checksum |
1022 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1023 | Subtype | Reserved | Identifier |
1024 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1025 | Options ...
1026 +-+-+-+-+-+-+-+-+-+-+-+-
1027
1028 Figure 8: Handover Acknowledge (HAck) Message
1029
1030 IP Fields:
1031
1032 Source Address: Copied from the destination address of the
1033 Handover Initiate Message to which this message is a response.
1034
1035 Destination Address: Copied from the source address of the
1036 Handover Initiate Message to which this message is a response.
1037
1038 Time-to-Live: At least 1. See [<a href="./rfc1256" title="&quot;ICMP Router Discovery Messages&quot;">rfc1256</a>].
1039
1040 ICMP Fields:
1041
1042 Type: 41. See <a href="./rfc4065#section-3">Section&nbsp;3 in [rfc4065]</a>.
1043
1044 Code:
1045
1046 0: Handover Accepted
1047 1: Handover Accepted, NCoA not valid
1048 2: Handover Accepted, NCoA in use
1049 3: Handover Accepted, NCoA assigned (used in Assigned
1050 addressing)
1051 4: Handover Accepted, NCoA not assigned
1052 128: Handover Not Accepted, reason unspecified
1053 129: Administratively prohibited
1054 130: Insufficient resources
1055
1056
1057
1058
1059
1060 <span class="grey">Koodli &amp; Perkins Experimental [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
1063
1064
1065 Checksum: The 16-bit one's complement of the one's complement
1066 sum of the ICMP message, starting with the ICMP Type. For
1067 computing the checksum, the Checksum and the Reserved fields
1068 are set to 0. See [<a href="./rfc1256" title="&quot;ICMP Router Discovery Messages&quot;">rfc1256</a>].
1069
1070 Subtype: 9
1071
1072 Reserved: MUST be set to zero by the sender and ignored by the
1073 receiver.
1074
1075 Identifier: Copied from the corresponding field in the Handover
1076 Initiate message this message is in response to.
1077
1078 Valid Options:
1079
1080 New Care-of Address: If the 'S' flag in the HI message is set,
1081 this option MUST be used to provide NCoA the MN should use when
1082 connected to this router. This option MAY be included even
1083 when 'S' bit is not set, e.g., Code 2 above. The MN should be
1084 prepared to use this address instead of performing DHCP or
1085 similar operations to obtain an IPv4 address.
1086
1087 The Code 0 is the expected average case of a handover being accepted
1088 and the routing support provided for the use of PCoA. The rest of
1089 the Code values pertain to the use of NCoA (which is common in
1090 [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>]). Code values 1 and 2 are for cases when the MN proposes
1091 an NCoA and the NAR provides a response. Code 3 is when the NAR
1092 provides NCoA (which could be the same as that proposed by the MN).
1093 Code 4 is when the NAR does not provide NCoA, but instead provides
1094 routing support for PCoA.
1095
1096 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Option Formats</span>
1097
1098 The options in this section are specified as extensions for the HI
1099 and HAck messages, as well as for the PrRtSol and PrRtAdv messages.
1100 The Option-Code values below are the same as those in [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>], and
1101 do not require any assignment from IANA.
1102
1103 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Link-Layer Address Option Format</span>
1104
1105 0 1 2 3
1106 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
1107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1108 | Type | Length | Option-Code | LLA ...
1109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1110
1111 Figure 9: Link-Layer Address Option Format
1112
1113
1114
1115
1116 <span class="grey">Koodli &amp; Perkins Experimental [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
1119
1120
1121 Fields:
1122
1123 Type: 20
1124
1125 Option-Code:
1126
1127 0: Wildcard requesting resolution for all nearby access
1128 points
1129 1: Link-Layer Address of the New Access Point
1130 2: Link-Layer Address of the MN
1131 3: Link-Layer Address of the NAR
1132 4: Link-Layer Address of the source of the RtSolPr or
1133 PrRtAdv message
1134 5: The access point identified by the LLA belongs to the
1135 current interface of the router
1136 6: No prefix information available for the access point
1137 identified by the LLA
1138 7: No fast handovers support available for the access point
1139 identified by the LLA
1140
1141 Length: The length of the option (including the Type, Length
1142 and Option-Code fields) in units of 8 octets.
1143
1144 Link-Layer Address: The variable-length link-layer address.
1145 The content and format of this field (including byte and bit
1146 ordering) depends on the specific link-layer in use.
1147
1148 There is no length field for the LLA itself. Implementations MUST
1149 determine the length of the LLA based on the specific link technology
1150 where the protocol is run. The total size of the LLA option itself
1151 MUST be a multiple of 8 octets. Hence, padding may be necessary
1152 depending on the size of the LLA used. In such a case, the padN
1153 option [<a href="./rfc2460" title="&quot;Internet Protocol, Version 6 (IPv6) Specification&quot;">rfc2460</a>] MUST be used. As an example, when the LLA is 6
1154 bytes (meaning 7 bytes of padding is necessary to bring the LLA
1155 option length to 2), the padN option will have a length field of 5
1156 and 5 bytes of zero-valued octets (see [<a href="./rfc2460" title="&quot;Internet Protocol, Version 6 (IPv6) Specification&quot;">rfc2460</a>]).
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Koodli &amp; Perkins Experimental [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
1175
1176
1177 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. New IPv4 Address Option Format</span>
1178
1179 This option is used to provide the new router's IPv4 address or the
1180 NCoA in PrRtAdv, as well as PCoA and NCoA in HI and HAck messages.
1181
1182 0 1 2 3
1183 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
1184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1185 | Type | Length | Option-Code | Reserved |
1186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1187 | New IPv4 Address |
1188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1189
1190 Figure 10: New IPv4 Address Option Format
1191
1192 Fields:
1193
1194 Type: 21
1195
1196 Length: The length of the option (including the Type, Length
1197 and Option-Code fields) in units of 8 octets.
1198
1199 Option-Code:
1200
1201 1: Previous CoA
1202 2: New CoA
1203 3: NAR's IP Address
1204
1205 Reserved: Set to zero.
1206
1207 New IPv4 Address: NAR's IPv4 address or the NCoA assigned by
1208 NAR.
1209
1210 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. New Router Prefix Information Option</span>
1211
1212 This option is used in the PrRtAdv message.
1213
1214 0 1 2 3
1215 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
1216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1217 | Type | Length | Option-Code | Prefix-Length |
1218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1219 | Reserved |
1220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1221
1222 Figure 11: New Router Prefix Information Option Format
1223
1224
1225
1226
1227
1228 <span class="grey">Koodli &amp; Perkins Experimental [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
1231
1232
1233 Fields:
1234
1235 Type: 22
1236
1237 Length: The length of the option (including the Type, Length
1238 and Option-Code fields) in units of 8 octets.
1239
1240 Option-Code: 0
1241
1242 Prefix-Length The number of leading bits that define the
1243 network number of the corresponding Router's IP Address option.
1244
1245 Reserved: Set to zero.
1246
1247 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
1248
1249 As outlined in [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>], the following vulnerabilities are
1250 identified and the solutions mentioned.
1251
1252 Insecure FBU:
1253
1254 Failure to protect the FBU message could result in packets meant for
1255 an address being stolen or redirected to some unsuspecting node.
1256 This concern is similar to that in Mobile Node and Home Agent
1257 relationship.
1258
1259 Hence, the FBU and FBack messages MUST be protected using a security
1260 association shared between a mobile node and its access router. In
1261 particular, the MN-PAR Authentication Extension MUST be present in
1262 each of these messages. This document does not specify how the
1263 security association is established between an MN and the AR/FA.
1264
1265 Secure FBU, malicious or inadvertent redirection:
1266
1267 Even if the MN-PAR authentication extension is present in an FBU, an
1268 MN may inadvertently or maliciously attempt to bind its PCoA to an
1269 unintended address on NAR's link, and cause traffic flooding to an
1270 unsuspecting node.
1271
1272 This vulnerability is avoided by always binding the PCoA to the NAR's
1273 IP address, even when the NAR supplies an NCoA to use for the MN. It
1274 is still possible to jam NAR's buffer with redirected traffic.
1275 However, the handover state corresponding to the MN's PCoA has a
1276 finite lifetime, and can be configured to be a few multiples of the
1277 anticipated handover latency. Hence, the extent of this
1278 vulnerability is small. It is possible to trace the culprit MN with
1279 an established security association at the access router.
1280
1281
1282
1283
1284 <span class="grey">Koodli &amp; Perkins Experimental [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
1287
1288
1289 Communication between the access routers:
1290
1291 The access routers communicate using HI and HAck messages in order to
1292 establish a temporary routing path for the MN undergoing handover.
1293 This message exchange needs to be secured to ensure routing updates
1294 take place as intended.
1295
1296 The HI and HAck messages need to be secured using a preexisting
1297 security association between the access routers to ensure at least
1298 message integrity and authentication, and SHOULD also include
1299 encryption. IPsec ESP SHOULD be used.
1300
1301 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
1302
1303 The IANA assignments made for messages, extensions, and options
1304 specified in this document are described in the following paragraphs.
1305
1306 This document defines two new messages that use the Mobile IPv4
1307 control message format [<a href="./rfc3344" title="&quot;IP Mobility Support for IPv4&quot;">rfc3344</a>]. These message details are as
1308 follows:
1309
1310 +------+-------------+-------------+
1311 | Type | Description | Reference |
1312 +------+-------------+-------------+
1313 | 20 | FBU | <a href="#section-5.1">Section 5.1</a> |
1314 | 21 | FBAck | <a href="#section-5.2">Section 5.2</a> |
1315 +------+-------------+-------------+
1316
1317 This document defines four new experimental ICMP messages that use
1318 the ICMP Type 41 for IPv4. See <a href="./rfc4065#section-3">Section&nbsp;3 in [rfc4065]</a>. The new
1319 messages specified in this document have been assigned Subtypes from
1320 the registry in [<a href="./rfc4065" title="&quot;Instructions for Seamoby and Experimental Mobility Protocol IANA Allocations&quot;">rfc4065</a>]:
1321
1322 +---------+-------------+-------------+
1323 | Subtype | Description | Reference |
1324 +---------+-------------+-------------+
1325 | 6 | RtSolPr | <a href="#section-5.3">Section 5.3</a> |
1326 | 7 | PrRtAdv | <a href="#section-5.4">Section 5.4</a> |
1327 | 8 | HI | <a href="#section-5.5">Section 5.5</a> |
1328 | 9 | HAck | <a href="#section-5.6">Section 5.6</a> |
1329 +---------+-------------+-------------+
1330
1331 This document defines three new options that have been assigned Types
1332 from the Mobile IP Extensions for ICMP Router Discovery messages
1333 [<a href="./rfc3344" title="&quot;IP Mobility Support for IPv4&quot;">rfc3344</a>]. These options are as follows:
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Koodli &amp; Perkins Experimental [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
1343
1344
1345 +------+------------------+-------------+
1346 | Type | Description | Reference |
1347 +------+------------------+-------------+
1348 | 20 | LLA | <a href="#section-6.1">Section 6.1</a> |
1349 | 21 | New IPv4 Address | <a href="#section-6.2">Section 6.2</a> |
1350 | 22 | NAR Prefix Info | <a href="#section-6.3">Section 6.3</a> |
1351 +------+------------------+-------------+
1352
1353 The MN-PAR Authentication Extension described in Sections <a href="#section-5.1">5.1</a> and <a href="#section-5.2">5.2</a>
1354 is a Generalized Mobile IP Authentication Extension defined in
1355 <a href="./rfc4721#section-5">Section&nbsp;5 of [rfc4721]</a>. The MN-PAR Authentication has been assigned
1356 a Subtype from the registry specified in [<a href="./rfc4721" title="&quot;Mobile IPv4 Challenge/Response Extensions (Revised)&quot;">rfc4721</a>]. The Extension
1357 details are as follows:
1358
1359 +---------+-----------------------+--------------------------+
1360 | Subtype | Description | Reference |
1361 +---------+-----------------------+--------------------------+
1362 | 4 | MN-PAR Auth Extension | <a href="#section-5.1">Section 5.1</a> |
1363 +---------+-----------------------+--------------------------+
1364
1365 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgments</span>
1366
1367 Thanks to all those who expressed interest in having a Fast Handovers
1368 for Mobile IPv4 protocol along the lines of [<a href="./rfc4068" title="&quot;Fast Handovers for Mobile IPv6&quot;">rfc4068</a>]. Thanks to
1369 Vijay Devarapalli, Kent Leung, and Domagoj Premec for their review
1370 and input. Kumar Viswanath and Uday Mohan implemented an early
1371 version of this protocol. Many thanks to Alex Petrescu for his
1372 thorough review that improved this document. Thanks to Pete McCann
1373 for the proofreading, and to Jari Arkko for the review, which have
1374 helped improve this document. Thanks to Francis Dupont and Hannes
1375 Tschofenig for the GEN-ART and TSV-DIR reviews.
1376
1377 Sending FBU from the new link (i.e., reactive mode) is similar to
1378 using the extension defined in [<a href="#ref-mip4-ro" title="&quot;Route Optimization in Mobile IP&quot;">mip4-ro</a>]; however, this document also
1379 addresses movement detection and router discovery latencies.
1380
1381 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
1382
1383 <span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
1384
1385 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
1386 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
1387
1388 [<a id="ref-rfc1256">rfc1256</a>] Deering, S., Ed., "ICMP Router Discovery Messages",
1389 <a href="./rfc1256">RFC 1256</a>, September 1991.
1390
1391 [<a id="ref-rfc2460">rfc2460</a>] Deering, S. and R. Hinden, "Internet Protocol, Version
1392 6 (IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, December 1998.
1393
1394
1395
1396 <span class="grey">Koodli &amp; Perkins Experimental [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
1399
1400
1401 [<a id="ref-rfc3344">rfc3344</a>] Perkins, C., Ed., "IP Mobility Support for IPv4", <a href="./rfc3344">RFC</a>
1402 <a href="./rfc3344">3344</a>, August 2002.
1403
1404 [<a id="ref-rfc4065">rfc4065</a>] Kempf, J., "Instructions for Seamoby and Experimental
1405 Mobility Protocol IANA Allocations", <a href="./rfc4065">RFC 4065</a>, July
1406 2005.
1407
1408 [<a id="ref-rfc4068">rfc4068</a>] Koodli, R., Ed., "Fast Handovers for Mobile IPv6", <a href="./rfc4068">RFC</a>
1409 <a href="./rfc4068">4068</a>, July 2005.
1410
1411 [<a id="ref-rfc4721">rfc4721</a>] Perkins, C., Calhoun, P., and J. Bharatia, "Mobile
1412 IPv4 Challenge/Response Extensions (Revised)", <a href="./rfc4721">RFC</a>
1413 <a href="./rfc4721">4721</a>, January 2007.
1414
1415 <span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
1416
1417 [<a id="ref-fh-ccr">fh-ccr</a>] R. Koodli and C. E. Perkins, "Fast Handovers and
1418 Context Transfers in Mobile Networks", ACM Computer
1419 Communications Review Special Issue on Wireless
1420 Extensions to the Internet, October 2001.
1421
1422 [<a id="ref-ieee-802.11r">ieee-802.11r</a>] IEEE, "IEEE Standard for Local and Metropolitan Area
1423 Networks: Fast Roaming/Fast BSS Transition, IEEE Std
1424 802.11r", September 2006.
1425
1426 [<a id="ref-ieee-802.1x">ieee-802.1x</a>] IEEE, "IEEE Standards for Local and Metropolitan Area
1427 Networks: Port-based Network Access Control, IEEE Std
1428 802.1X-2001", June 2001.
1429
1430 [<a id="ref-ieee-802.21">ieee-802.21</a>] The IEEE 802.21 group, <a href="http://www.ieee802.org/21">http://www.ieee802.org/21</a>.
1431
1432 [<a id="ref-mi-book">mi-book</a>] R. Koodli and C. E. Perkins, "Mobile Internetworking
1433 with IPv6: Concepts, Principles and Practices", John
1434 Wiley &amp; Sons, June 2007.
1435
1436 [<a id="ref-mip4-ro">mip4-ro</a>] Perkins, C. and D. Johnson, "Route Optimization in
1437 Mobile IP", Work in Progress, September 2001.
1438
1439 [<a id="ref-rfc2131">rfc2131</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC</a>
1440 <a href="./rfc2131">2131</a>, March 1997.
1441
1442 [<a id="ref-rfc3957">rfc3957</a>] Perkins, C. and P. Calhoun, "Authentication,
1443 Authorization, and Accounting (AAA) Registration Keys
1444 for Mobile IPv4", <a href="./rfc3957">RFC 3957</a>, March 2005.
1445
1446
1447
1448
1449
1450
1451
1452 <span class="grey">Koodli &amp; Perkins Experimental [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
1455
1456
1457 Authors' Addresses
1458
1459 Rajeev Koodli
1460 Nokia Siemens Networks
1461 313 Fairchild Driive
1462 Mountain View, CA 94043
1463 USA
1464
1465 EMail: [email protected]
1466
1467
1468 Charles Perkins
1469 Nokia Siemens Networks
1470 313 Fairchild Driive
1471 Mountain View, CA 94043
1472 USA
1473
1474 EMail: [email protected]
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508 <span class="grey">Koodli &amp; Perkins Experimental [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc4988">RFC 4988</a> MIP4 Fast Handovers October 2007</span>
1511
1512
1513 Full Copyright Statement
1514
1515 Copyright (C) The IETF Trust (2007).
1516
1517 This document is subject to the rights, licenses and restrictions
1518 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
1519 retain all their rights.
1520
1521 This document and the information contained herein are provided on an
1522 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1523 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
1524 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
1525 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
1526 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1527 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1528
1529 Intellectual Property
1530
1531 The IETF takes no position regarding the validity or scope of any
1532 Intellectual Property Rights or other rights that might be claimed to
1533 pertain to the implementation or use of the technology described in
1534 this document or the extent to which any license under such rights
1535 might or might not be available; nor does it represent that it has
1536 made any independent effort to identify any such rights. Information
1537 on the procedures with respect to rights in RFC documents can be
1538 found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
1539
1540 Copies of IPR disclosures made to the IETF Secretariat and any
1541 assurances of licenses to be made available, or the result of an
1542 attempt made to obtain a general license or permission for the use of
1543 such proprietary rights by implementers or users of this
1544 specification can be obtained from the IETF on-line IPR repository at
1545 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
1546
1547 The IETF invites any interested party to bring to its attention any
1548 copyrights, patents or patent applications, or other proprietary
1549 rights that may cover technology that may be required to implement
1550 this standard. Please address the information to the IETF at
1551 [email protected].
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564 Koodli &amp; Perkins Experimental [Page 28]
1565 </pre>