Debian Codegraph @

rfc5270.html

raw
1 <pre>Network Working Group H. Jang
2 Request for Comments: 5270 SAMSUNG
3 Category: Informational J. Jee
4 ETRI
5 Y. Han
6 KUT
7 S. Park
8 SAMSUNG Electronics
9 J. Cha
10 ETRI
11 June 2008
12
13
14 <span class="h1">Mobile IPv6 Fast Handovers over IEEE 802.16e Networks</span>
15
16 Status of This Memo
17
18 This memo provides information for the Internet community. It does
19 not specify an Internet standard of any kind. Distribution of this
20 memo is unlimited.
21
22 Abstract
23
24 This document describes how a Mobile IPv6 Fast Handover can be
25 implemented on link layers conforming to the IEEE 802.16e suite of
26 specifications. The proposed scheme tries to achieve seamless
27 handover by exploiting the link-layer handover indicators and thereby
28 synchronizing the IEEE 802.16e handover procedures with the Mobile
29 IPv6 fast handover procedures efficiently.
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">Jang, et al. Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
60 <a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-3">3</a>. IEEE 802.16e Handover Overview . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
62 <a href="#section-4">4</a>. Network Topology Acquisition and Network Selection . . . . . . <a href="#page-5">5</a>
63 <a href="#section-5">5</a>. Interaction between FMIPv6 and IEEE 802.16e . . . . . . . . . <a href="#page-6">6</a>
64 <a href="#section-5.1">5.1</a>. Access Router Discovery . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
65 <a href="#section-5.2">5.2</a>. Handover Preparation . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
66 <a href="#section-5.3">5.3</a>. Handover Execution . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
67 <a href="#section-5.4">5.4</a>. Handover Completion . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
68 <a href="#section-6">6</a>. The Examples of Handover Scenario . . . . . . . . . . . . . . <a href="#page-10">10</a>
69 <a href="#section-6.1">6.1</a>. Predictive Mode . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
70 <a href="#section-6.2">6.2</a>. Reactive Mode . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
71 <a href="#section-7">7</a>. IEEE 802.21 Considerations . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
72 <a href="#section-8">8</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
73 <a href="#section-9">9</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
74 <a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
75 <a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
76 <a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
77
78 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
79
80 Mobile IPv6 Fast Handover protocol (FMIPv6) [<a href="./rfc5268" title="&quot;Mobile IPv6 Fast Handovers&quot;">RFC5268</a>] was proposed to
81 complement the Mobile IPv6 (MIPv6) [<a href="./rfc3775" title="&quot;Mobility Support in IPv6&quot;">RFC3775</a>] by reducing the handover
82 latency for the real-time traffic. FMIPv6 assumes the support from
83 the link-layer technology; however, the specific link-layer
84 information available and its available timing differs according to
85 the particular link-layer technology in use, as pointed out in
86 [<a href="./rfc4260" title="&quot;Mobile IPv6 Fast Handovers for 802.11 Networks&quot;">RFC4260</a>], which provides an FMIPv6 solution for the IEEE 802.11
87 networks. So, this document is proposed to provide an informational
88 guide to the developers about how to optimize the FMIPv6 handover
89 procedures, specifically in the IEEE 802.16e networks
90 [<a href="#ref-IEEE802.16" title="&quot;IEEE Standard for Local and Metropolitan Area Networks, Part 16: Air Interface for Fixed Broadband Wireless Access Systems&quot;">IEEE802.16</a>][IEEE802.16e].
91
92 The proposed scheme achieves seamless handover by exploiting the
93 link-layer handover indicators and designing an efficient
94 interleaving scheme of the 802.16e and the FMIPv6 handover
95 procedures. The scheme targets a hard handover, which is the default
96 handover type of IEEE 802.16e. For the other handover types, i.e.,
97 the Macro Diversity Handover (MDHO) and Fast Base Station Switching
98 (FBSS), the base stations in the same diversity set are likely to
99 belong to the same subnet for diversity, and FMIPv6 might not be
100 needed. Regarding the MDHO and the FBSS deployment with FMIPv6,
101 further discussion will be needed and is not in the scope of this
102 document.
103
104
105
106
107
108 <span class="grey">Jang, et al. Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
111
112
113 We begin with a summary of handover procedures of [<a href="#ref-IEEE802.16e" title="&quot;IEEE Standard for Local and Metropolitan Area Networks, Amendment 2: Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands and Corrigendum 1&quot;">IEEE802.16e</a>] and
114 then present the optimized complete FMIPv6 handover procedures by
115 using the link-layer handover indicators. The examples of handover
116 scenarios are described for both the predictive mode and reactive
117 mode.
118
119 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
120
121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
123 document is to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
124
125 Most of terms used in this document are defined in MIPv6 [<a href="./rfc3775" title="&quot;Mobility Support in IPv6&quot;">RFC3775</a>]
126 and FMIPv6 [<a href="./rfc5268" title="&quot;Mobile IPv6 Fast Handovers&quot;">RFC5268</a>].
127
128 The following terms come from the IEEE 802.16e specification
129 [<a href="#ref-IEEE802.16e" title="&quot;IEEE Standard for Local and Metropolitan Area Networks, Amendment 2: Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands and Corrigendum 1&quot;">IEEE802.16e</a>].
130
131 MOB_NBR-ADV
132
133 An IEEE 802.16e neighbor advertisement message sent
134 periodically by a base station.
135
136 MOB_MSHO-REQ
137
138 An IEEE 802.16e handover request message sent by a mobile node.
139
140 MOB_BSHO-RSP
141
142 An IEEE 802.16e handover response message sent by a base
143 station.
144
145 MOB_BSHO-REQ
146
147 An IEEE 802.16e handover request message sent by a base
148 station.
149
150 MOB_HO-IND
151
152 An IEEE 802.16e handover indication message sent by a mobile
153 node.
154
155 BSID
156
157 An IEEE 802.16e base station identifier.
158
159
160
161
162
163
164 <span class="grey">Jang, et al. Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
167
168
169 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IEEE 802.16e Handover Overview</span>
170
171 Compared with the handover in the WLAN (Wireless Local Area Network),
172 the IEEE 802.16e handover mechanism consists of more steps since the
173 802.16e embraces the functionality for elaborate parameter adjustment
174 and procedural flexibility.
175
176 When a mobile node (MN) stays in a link, it listens to the Layer 2
177 neighbor advertisement messages, named MOB_NBR-ADV, from its serving
178 base station (BS). A BS broadcasts them periodically to identify the
179 network and announce the characteristics of neighbor BSs. Receiving
180 this, the MN decodes this message to find out information about the
181 parameters of neighbor BSs for its future handover. With the
182 provided information in a MOB_NBR-ADV, the MN may minimize the
183 handover latency by obtaining the channel number of neighbors and
184 reducing the scanning time, or may select the better target BS based
185 on the signal strength, Quality-of-Service (QoS) level, service
186 price, etc.
187
188 The handover procedure is conceptually divided into two steps:
189 "handover preparation" and "handover execution" [<a href="#ref-SH802.16e" title="&quot;A Seamless Handover Mechanism for IEEE 802.16e Broadband Wireless Access&quot;">SH802.16e</a>]. The
190 handover preparation can be initiated by either an MN or a BS.
191
192 During this period, neighbors are compared by the metrics such as
193 signal strength or QoS parameters, and a target BS is selected among
194 them. If necessary, the MN may try to associate (initial ranging)
195 with candidate BSs to expedite a future handover. Once the MN
196 decides to handover, it notifies its intent by sending a MOB_MSHO-REQ
197 message to the serving BS (s-BS). The BS then replies with a
198 MOB_BSHO-RSP containing the recommended BSs to the MN after
199 negotiating with candidates. Optionally, it may confirm handover to
200 the target BS (t-BS) over backbone when the target is decided.
201 Alternatively, the BS may trigger handover with a MOB_BSHO-REQ
202 message.
203
204 After handover preparation, handover execution starts. The MN sends
205 a MOB_HO-IND message to the serving BS as a final indication of its
206 handover. Once it makes a new attachment, it conducts 802.16e
207 ranging through which it can acquire physical parameters from the
208 target BS, tuning its parameters to the target BS. After ranging
209 with the target BS successfully, the MN negotiates basic capabilities
210 such as maximum transmit power and modulator/demodulator type. It
211 then performs authentication and key exchange procedures, and finally
212 registers with the target BS. If the target BS has already learned
213 some contexts such as authentication or capability parameters through
214 backbone, it may omit the corresponding procedures. For the details
215 of the 802.16 handover procedures, refer to Section 6.3.22 of
216 [<a href="#ref-IEEE802.16e" title="&quot;IEEE Standard for Local and Metropolitan Area Networks, Amendment 2: Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands and Corrigendum 1&quot;">IEEE802.16e</a>]. After completing registration, the target BS starts
217
218
219
220 <span class="grey">Jang, et al. Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
223
224
225 to serve the MN and communication via target BS is available.
226 However, in case the MN moves to a different subnet, it should
227 reconfigure a new IP address and reestablish an IP connection. To
228 resume the active session of the previous link, the MN should also
229 perform IP layer handover.
230
231 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Network Topology Acquisition and Network Selection</span>
232
233 This section describes how discovery of adjacent networks and
234 selection of target network work in the IEEE 802.16e for background
235 information.
236
237 An MN can learn the network topology and acquire the link information
238 in several ways. First of all, it can do that via L2 neighbor
239 advertisements. A BS supporting mobile functionality shall broadcast
240 a MOB_NBR-ADV message periodically that includes the network topology
241 information (its maximum interval is 1 second). This message
242 includes BSIDs and channel information of neighbor BSs, and it is
243 used to facilitate the MN's synchronization with neighbor BSs. An MN
244 can collect the necessary information of the neighbor BSs through
245 this message for its future handover.
246
247 Another method for acquisition of network topology is scanning, which
248 is the process to seek and monitor available BSs in order to find
249 suitable handover targets. While a MOB_NBR-ADV message includes
250 static information about neighbor BSs, scanning provides rather
251 dynamic parameters such as link quality parameters. Since the
252 MOB_NBR-ADV message delivers a list of neighbor BSIDs periodically
253 and scanning provides a way to sort out some adequate BSs, it is
254 recommended that when new BSs are found in the advertisement, the MN
255 identifies them via scanning and resolves their BSIDs to the
256 information of the subnet where the BS is connected. The
257 association, an optional initial ranging procedure occurring during
258 scanning, is one of the helpful methods to facilitate the impending
259 handover. The MN is able to get ranging parameters and service
260 availability information for the purpose of proper selection of the
261 target BS and expediting a potential future handover to it. The
262 detailed explanation of association is described in Section 6.3.22 of
263 [<a href="#ref-IEEE802.16e" title="&quot;IEEE Standard for Local and Metropolitan Area Networks, Amendment 2: Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands and Corrigendum 1&quot;">IEEE802.16e</a>].
264
265 Besides the methods provided by 802.16e, the MN may rely on other
266 schemes. For instance, the topology information may be provided
267 through the MIIS (Media Independent Information Service)
268 [<a href="#ref-IEEE802.21" title="&quot;Draft IEEE Standard for Local and Metropolitan Area Networks: Media Independent Handover Services&quot;">IEEE802.21</a>], which has been developed by the IEEE 802.21 working
269 group. The MIIS is a framework by which the MN or network can obtain
270 network information to facilitate network selection and handovers.
271
272
273
274
275
276 <span class="grey">Jang, et al. Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
279
280
281 After learning about neighbors, the MN may compare them to find a BS,
282 which can serve better than the serving BS. The target BS may be
283 determined by considering various criteria such as required QoS,
284 cost, user preference, and policy. How to select the target BS is
285 not in the scope of this document.
286
287 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Interaction between FMIPv6 and IEEE 802.16e</span>
288
289 In this section, a set of primitives is introduced for an efficient
290 interleaving of the IEEE 802.16e and the FMIPv6 procedures as below.
291 The following sections present the handover procedures in detail by
292 using them.
293
294 o NEW_LINK_DETECTED (NLD)
295
296 A trigger from the link layer to the IP layer in the MN to
297 report that a new link has been detected.
298
299 o LINK_HANDOVER_IMPEND (LHI)
300
301 A trigger from the link layer to the IP layer in the MN to
302 report that a link-layer handover decision has been made and
303 its execution is imminent.
304
305 o LINK_SWITCH (LSW)
306
307 A control command from the IP layer to the link layer in the MN
308 in order to force the MN to switch from an old BS to a new BS.
309
310 o LINK_UP (LUP)
311
312 A trigger from the link layer to the IP layer in the MN to
313 report that the MN completes the link-layer connection
314 establishment with a new BS.
315
316 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Access Router Discovery</span>
317
318 Once a new BS is detected through reception of a MOB_NBR-ADV and
319 scanning, an MN may try to learn the associated access router (AR)
320 information as soon as possible. In order to enable its quick
321 discovery in the IP layer, the link layer (802.16) triggers a
322 NEW_LINK_DETECTED primitive to the IP layer (FMIPv6) on detecting a
323 new BS.
324
325 Receiving the NEW_LINK_DETECTED from the link layer, the IP layer
326 tries to learn the associated AR information by exchanging an RtSolPr
327 (Router Solicitation for Proxy Advertisement) and a PrRtAdv (Proxy
328 Router Advertisement) with the PAR (Previous Access Router).
329
330
331
332 <span class="grey">Jang, et al. Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
335
336
337 According to [<a href="./rfc5268" title="&quot;Mobile IPv6 Fast Handovers&quot;">RFC5268</a>], the MN may send an RtSolPr at any convenient
338 time. However, this proposal recommends that, if feasible, the MN
339 send it as soon as possible after receiving the NEW_LINK_DETECTED for
340 quick router discovery because detection of a new BS usually implies
341 MN's movement, which may result in handover.
342
343 Transmission of RtSolPr messages may cause the signaling overhead
344 problem that is mentioned in <a href="./rfc4907#section-2">Section&nbsp;2 of [RFC4907]</a>. To rate-limit
345 the retransmitted RtSolPr messages, FMIPv6 provides a back-off
346 mechanism. It is also possible that attackers may forge a MOB_NBR-
347 ADV message so that it can contain a bunch of bogus BSIDs or may send
348 a flood of MOB_NBR-ADV messages each of which contains different
349 BSIDs. This problem is mentioned in <a href="#section-8">Section 8</a>.
350
351 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Handover Preparation</span>
352
353 When the MN decides to change links based on its policy such as the
354 degrading signal strength or increasing packet loss rate, it
355 initiates handover by sending a MOB_MSHO-REQ to the BS and will
356 receive a MOB_BSHO-RSP from the BS as a response. Alternatively, the
357 BS may initiate handover by sending a MOB_BSHO-REQ to the MN.
358
359 On receiving either a MOB_BSHO-RSP or a MOB_BSHO-REQ, the link layer
360 triggers a LINK_HANDOVER_IMPEND in order to signal the IP layer of
361 arrival of MOB_BSHO-REQ/MOB_BSHO-RSP quickly. At this time, the
362 target BS decided in the link layer is delivered to the IP layer as a
363 parameter of the primitive. The primitive is used to report that a
364 link-layer handover decision has been made and its execution is
365 imminent. It can be helpfully used for FMIPv6 as an indication to
366 start the handover preparation procedure, that is to send an FBU
367 (Fast Binding Update) message to the PAR.
368
369 To avoid erroneous results due to unreliable and inconsistent
370 characteristics of link, for instance, to move to the unpredicted
371 network or to stay in the current network after sending an FBU,
372 <a href="./rfc4907#section-2">Section&nbsp;2 of [RFC4907]</a> advises the use of a combination of signal
373 strength data with other techniques rather than relying only on
374 signal strength for handover decision. For example, the
375 LINK_HANDOVER_IMPEND may be sent after validating filtered signal
376 strength measurements with other indications of link loss such as
377 lack of beacon reception.
378
379 Once the IP layer receives the LINK_HANDOVER_IMPEND, it checks
380 whether or not the specified target network belongs to a different
381 subnet based on the information collected during the Access Router
382 Discovery step. If the target proves to be in the same subnet, the
383 MN can continue to use the current IP address after handover, and
384 there is no need to perform FMIPv6. Otherwise, the IP layer
385
386
387
388 <span class="grey">Jang, et al. Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
391
392
393 formulates a prospective NCoA (New Care-of Address) with the
394 information provided in the PrRtAdv message and sends an FBU message
395 to the PAR.
396
397 When the FBU message arrives in the PAR successfully, the PAR and the
398 NAR (New Access Router) process it according to [<a href="./rfc5268" title="&quot;Mobile IPv6 Fast Handovers&quot;">RFC5268</a>]. The PAR
399 sets up a tunnel between the PCoA (Previous Care-of Address) and NCoA
400 by exchanging HI (Handover Initiate) and HAck (Handover Acknowledge)
401 messages with the NAR, forwarding the packets destined for the MN to
402 the NCoA. The NCoA is confirmed or re-assigned by the NAR in the
403 HAck and, finally delivered to the MN through the FBack (Fast Binding
404 Acknowledgment) in case of predictive mode.
405
406 After the MN sends a MOB_HO-IND to the serving BS, data packet
407 transfer between the MN and the BS is no longer allowed. Note that
408 when a MOB_HO-IND is sent out before an FBack arrives in the MN, it
409 is highly probable that the MN will operate in reactive mode because
410 the serving BS releases all the MN's connections and resources after
411 receiving a MOB_HO-IND. Therefore, if possible, the MN should
412 exchange FBU and FBack messages with the PAR before sending a MOB_HO-
413 IND to the BS so as to operate in predictive mode.
414
415 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Handover Execution</span>
416
417 If the MN receives an FBack message on the previous link, it runs in
418 predictive mode after handover. Otherwise, it should run in reactive
419 mode. In order for the MN to operate in predictive mode as far as
420 possible after handover, implementations may allow use of a
421 LINK_SWITCH primitive. The LINK_SWITCH is a command in order to
422 force the MN to switch from an old BS to a new BS and the similar
423 concept has introduced for the wireless LAN in [<a href="./rfc5184" title="&quot;Unified Layer 2 (L2) Abstractions for Layer 3 (L3)-Driven Fast Handover&quot;">RFC5184</a>]. When it is
424 applied, the MN's IP layer issues a LINK_SWITCH primitive to the link
425 layer on receiving the FBack message in the previous link. Until it
426 occurs, the link layer keeps the current (previous) link if feasible
427 and postpones sending a MOB_HO-IND message while waiting for the
428 FBack message.
429
430 After switching links, the MN synchronizes with the target BS and
431 performs the 802.16e network entry procedure. The MN exchanges the
432 RNG-REQ/RSP, SBC-REQ/RSP, PKM-REQ/RSP, and REG-REQ/RSP messages with
433 the target BS. Some of these messages may be omitted if the
434 (previously) serving BS transferred the context to the target BS over
435 the backbone beforehand. When the network entry procedure is
436 completed and the link layer is ready for data transmission, it
437 informs the IP layer of the fact with a LINK_UP primitive.
438
439
440
441
442
443
444 <span class="grey">Jang, et al. Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
447
448
449 <a href="./rfc4907#section-2">Section&nbsp;2 of [RFC4907]</a> recommends that link indications should be
450 designed with built-in damping. The LINK_UP primitive defined in
451 this document is generated by the link layer state machine based on
452 the 802.16e link layer message exchanges, that is, the IEEE 802.16e
453 network entry and the service flow creation procedures. Therefore,
454 the LINK_UP is typically less sensitive to changes in transient link
455 conditions. The link may experience an intermittent loss. Even in
456 such a case, the following FMIPv6 operation is performed only when
457 the MN handovers to the link with a different subnet and there is no
458 signaling overhead as a result of a intermittent loss.
459
460 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Handover Completion</span>
461
462 When the MN's IP layer receives a LINK_UP primitive from the link
463 layer, it should check whether it has moved into the target network
464 predicted by FMIPv6. In case the target BS is within the same
465 subnet, the MN does not perform the FMIPv6 operation.
466
467 * If the MN discovers itself in the predicted target network and
468 receives an FBack message in the previous link, the MN's IP
469 layer sends an UNA (Unsolicited Neighbor Advertisement) to the
470 NAR (predictive mode).
471
472 * If the MN has moved to the target network without receiving an
473 FBack message in the previous link, the IP layer sends an UNA
474 and also an FBU message immediately after sending the UNA
475 message (reactive mode). The NAR may provide a different IP
476 address by using an RA (Router Advertisement) with a NAACK
477 (Neighbor Advertisement Acknowledge) option other than the
478 formulated NCoA by the MN.
479
480 * The MN may discover itself in the unpredicted network
481 (erroneous movement). If this is the case, the MN moves to the
482 network that is not the target specified in the
483 LINK_HANDOVER_IMPEND primitive. For the recovery from such an
484 invalid indication, which is mentioned in <a href="./rfc4907#section-2">Section&nbsp;2 of
485 [RFC4907]</a>, the MN should send a new FBU to the PAR according to
486 <a href="./rfc5268#section-5.6">Section&nbsp;5.6 of [RFC5268]</a> so that the PAR can update the
487 existing binding entry and redirect the packets to the new
488 confirmed location.
489
490 In both cases of predictive and reactive modes, once the MN has moved
491 into the new link, it uses the NCoA formulated by the MN as a source
492 address of the UNA, irrespective of NCoA availability. It then
493 starts a Duplicate Address Detection (DAD) probe for NCoA according
494 to [<a href="./rfc4862" title="&quot;IPv6 Stateless Address Autoconfiguration&quot;">RFC4862</a>]. In case the NAR provides the MN with a new NCoA, the
495 MN MUST use the provided NCoA instead of the NCoA formulated by the
496 MN.
497
498
499
500 <span class="grey">Jang, et al. Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
503
504
505 When the NAR receives an UNA message, it deletes its proxy neighbor
506 cache entry if it exists, and forwards buffered packets to the MN
507 after updating the neighbor cache properly. Detailed UNA processing
508 rules are specified in <a href="./rfc5268#section-6.4">Section&nbsp;6.4 of [RFC5268]</a>.
509
510 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. The Examples of Handover Scenario</span>
511
512 In this section, the recommended handover procedures over 802.16e
513 network are shown for both predictive and reactive modes. It is
514 assumed that the MN handovers to the network that belongs to a
515 different subnet.
516
517 In the following figures, the messages between the MN's Layer 2 (MN
518 L2) and the BS are the IEEE 802.16 messages, while messages between
519 the MN's Layer 3 (MN L3) and the PAR and messages between PAR and NAR
520 are the FMIPv6 messages. The messages between the MN L2 and the MN
521 L3 are primitives introduced in this document.
522
523 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Predictive Mode</span>
524
525 The handover procedures in the predictive mode are briefly described
526 as follows. Figure 3 illustrates these procedures.
527
528 1. A BS broadcasts a MOB_NBR-ADV periodically.
529
530 2. If the MN discovers a new neighbor BS in this message, it may
531 perform scanning for the BS.
532
533 3. When a new BS is found through the MOB_NBR-ADV and scanning,
534 the MN's link layer notifies it to the IP layer by a
535 NEW_LINK_DETECTED primitive.
536
537 4. The MN tries to resolve the new BS's BSID to the associated
538 AR by exchange of RtSolPr and PrRtAdv messages with the PAR.
539
540 5. The MN initiates handover by sending a MOB_MSHO-REQ message
541 to the BS and receives a MOB_BSHO-RSP from the BS.
542 Alternatively, the BS may initiate handover by sending a
543 MOB_BSHO-REQ to the MN.
544
545 6. When the MN receives either a MOB_BSHO-RSP or a MOB_BSHO-REQ
546 from the BS, its link layer triggers a LINK_HANDOVER_IMPEND
547 primitive to the IP layer.
548
549
550
551
552
553
554
555
556 <span class="grey">Jang, et al. Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
559
560
561 7. On reception of the LINK_HANDOVER_IMPEND, the MN's IP layer
562 identifies that the target delivered along with the
563 LINK_HANDOVER_IMPEND belongs to a different subnet and sends
564 an FBU message to the PAR. On receiving this message, the
565 PAR establishes tunnel between the PCoA and the NCoA by
566 exchange of HI and HAck messages with the NAR, and it
567 forwards packets destined for the MN to the NCoA. During
568 this time, the NAR may confirm NCoA availability in the new
569 link via HAck.
570
571 8. The MN receives the FBack message before its handover and
572 sends a MOB_HO-IND message as a final indication of handover.
573 Issue of a MOB_HO-IND may be promoted optionally by using a
574 LINK_SWITCH command from the IP layer. Afterwards it
575 operates in predictive mode in the new link.
576
577 9. The MN conducts handover to the target BS and performs the
578 IEEE 802.16e network entry procedure.
579
580 10. As soon as the network entry procedure is completed, the MN's
581 link layer signals the IP layer with a LINK_UP. On receiving
582 this, the IP layer identifies that it has moved to a
583 predicted target network and received the FBack message in
584 the previous link. It issues an UNA to the NAR by using the
585 NCoA as a source IP address. At the same time, it starts to
586 perform DAD for the NCoA.
587
588 11. When the NAR receives the UNA from the MN, it delivers the
589 buffered packets to the MN.
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Jang, et al. Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
615
616
617 (MN L3 MN L2) s-BS PAR t-BS NAR
618 | | | | | |
619 1-2. | |&lt;---MOB_NBR-ADV --------| | | |
620 | |&lt;-------Scanning-------&gt;| | | |
621 3. |&lt;-NLD-| | | | |
622 4. |--------------(RtSolPr)--------------&gt;| | |
623 |&lt;--------------PrRtAdv----------------| | |
624 | | | | | |
625 5. | |------MOB_MSHO-REQ-----&gt;| | | |
626 | |&lt;-----MOB_BSHO-RSP------| | | |
627 | | or | | | |
628 | |&lt;-----MOB_BSHO-REQ------| | | |
629 6. |&lt;-LHI-| | | | |
630 7. |------------------FBU----------------&gt;| | |
631 | | | |--------HI--------&gt;|
632 | | | |&lt;------HACK--------|
633 |&lt;-----------------FBack---------------|--&gt; | |
634 | | | Packets==============&gt;|
635 8. |(LSW)&gt;|-------MOB_HO-IND------&gt;| | | |
636 disconnect| | | | |
637 connect | | | | |
638 9. | |&lt;---------IEEE 802.16 network entry--------&gt;| |
639 10. |&lt;-LUP-| | | | |
640 |----------------------------UNA--------------------------&gt;|
641 11. |&lt;==================================================== Packets
642 | | | | |
643
644 Figure 3. Predictive Fast Handover in 802.16e
645
646 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Reactive Mode</span>
647
648 The handover procedures in the reactive mode are described as
649 follows. Figure 4 is illustrating these procedures.
650
651 1. ~ 7. The same as procedures of predictive mode.
652
653 8. The MN does not receive the FBack message before handover and
654 sends a MOB_HO-IND message as a final indication of handover.
655 Afterwards, it operates in reactive mode in the new link.
656
657 9. The MN conducts handover to the target network and performs
658 the 802.16e network entry procedure.
659
660
661
662
663
664
665
666
667
668 <span class="grey">Jang, et al. Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
671
672
673 10. As soon as the network entry procedure is completed, the MN's
674 link layer signals the IP layer with a LINK_UP. On receiving
675 this, the IP layer identifies that it has moved to the
676 predicted target network without receiving the FBack in the
677 previous link. The MN issues an UNA to the NAR by using NCoA
678 as a source IP address and starts to perform DAD for the
679 NCoA. Additionally, it sends an FBU to the PAR in the
680 reactive mode.
681
682 11. When the NAR receives the UNA and the FBU from the MN, it
683 forwards the FBack to the PAR. The FBack and Packets are
684 forwarded from the PAR and delivered to the MN (NCoA) through
685 the NAR. The NAR may supply a different IP address than the
686 NCoA by sending an RA with a NAACK option to the MN.
687
688 (MN L3 MN L2) s-BS PAR t-BS NAR
689 | | | | | |
690 1-2. | |&lt;---MOB_NBR-ADV &amp; Scan--| | | |
691 | |&lt;-------Scanning-------&gt;| | | |
692 3. |&lt;-NLD-| | | | |
693 4. |--------------(RtSolPr)--------------&gt;| | |
694 |&lt;--------------PrRtAdv----------------| | |
695 | | | | | |
696 5. | |------MOB_MSHO-REQ-----&gt;| | | |
697 | |&lt;-----MOB_BSHO-RSP------| | | |
698 | | or | | | |
699 | |&lt;-----MOB_BSHO-REQ------| | | |
700 6. |&lt;-LHI-| | | | |
701 7. |--------FBU----X---&gt; | | | |
702 8. | |-------MOB_HO-IND------&gt;| | | |
703 disconnect| | | | |
704 connect | | | | |
705 9. | |&lt;---------IEEE 802.16 network entry--------&gt;| |
706 10. |&lt;-LUP-| | | | |
707 |----------------------------UNA--------------------------&gt;|
708 |----------------------------FBU--------------------------)|
709 11. | | | |&lt;-------FBU-------)|
710 | | | |&lt;-----HI/HAck-----&gt;|
711 | | | | (if necessary) |
712 | | | Packets &amp; FBack=========&gt;|
713 |&lt;=========================================================|
714 | | | | | |
715
716 Figure 4. Reactive Fast Handover in 802.16e
717
718
719
720
721
722
723
724 <span class="grey">Jang, et al. Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
727
728
729 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IEEE 802.21 Considerations</span>
730
731 It is worth noting that great research has been conducted on defining
732 generic services in the IEEE 802.21 working group that facilitate
733 handovers between heterogeneous access links. The standard works are
734 named as a Media Independent Handover (MIH) Service [<a href="#ref-IEEE802.21" title="&quot;Draft IEEE Standard for Local and Metropolitan Area Networks: Media Independent Handover Services&quot;">IEEE802.21</a>], and
735 propose three kinds of services: Media Independent Event Service
736 (MIES), Media Independent Command Service (MICS), and Media
737 Independent Information Service (MIIS).
738
739 An MIES defines the events triggered from lower layers (physical and
740 link) to higher layers (network and above) in order to report changes
741 of physical and link-layer conditions. On the other hand, an MICS
742 supports the commands sent from higher layers to lower layers, and it
743 provides users with a way of managing the link behavior relevant to
744 handovers and mobility. An MIIS provides a framework by which the MN
745 or network can obtain network information to facilitate network
746 selection and handovers.
747
748 Although the purpose of IEEE 802.21 has been developed to enhance the
749 user experience of MNs roaming between heterogeneous networks, the
750 results may be utilized to optimize the handover performance in a
751 homogeneous network. When the MIH primitives are available for
752 handover in the 802.16e network, the MN can use them instead of the
753 primitives proposed in this document. Table 1 shows examples of the
754 mapping between the proposed primitives and the MIH primitives.
755
756 +-------------------------+-------------------------+
757 | Proposed primitives | MIH primitives |
758 +===================================================+
759 | NEW_LINK_DETECTED | LINK_DETECTED |
760 +---------------------------------------------------+
761 | LINK_HANDOVER_IMPEND | LINK_HANDOVER_IMMINENT |
762 +---------------------------------------------------+
763 | LINK_SWITCH | HANDOVER_COMMIT |
764 +---------------------------------------------------+
765 | LINK_UP | LINK_UP |
766 +---------------------------------------------------+
767
768 Table 1. The Proposed Primitives and MIH Primitives
769
770 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
771
772 The primitives defined in this document are used only for local
773 indication inside of the MN, so no security mechanism is required to
774 protect those primitives. However, FMIPv6 messages and IEEE 802.16e
775 messages, which may trigger the primitives, need to be protected.
776
777
778
779
780 <span class="grey">Jang, et al. Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
783
784
785 Security considerations of the FMIPv6 specification [<a href="./rfc5268" title="&quot;Mobile IPv6 Fast Handovers&quot;">RFC5268</a>] are
786 applicable to this document. It is also worthwhile to note that the
787 IEEE802.16e has a security sub-layer that provides subscribers with
788 privacy and authentication over the broadband wireless network. This
789 layer has two main component protocols: a privacy key management
790 protocol (PKM) for key management and authentication and an
791 encapsulation protocol for encrypting data. From the perspective of
792 the 802.16e, FMIPv6 messages are considered as data and are delivered
793 securely by using those protocols.
794
795 However, some of IEEE 802.16e management messages are sent without
796 authentication. For example, there is no protection to secure
797 802.16e broadcast messages. It may be possible for the attacker to
798 maliciously forge a MOB_NBR-ADV message so that it contains the bogus
799 BSIDs, or send a flood of MOB_NBR-ADV messages having different bogus
800 BSIDs toward the MN. As a result, the MN may trigger a bunch of
801 NEW_LINK_DETECTED primitives and send useless consecutive RtSolPr
802 messages to the PAR, finally resulting in wasting the air resources.
803 Therefore, the MN SHOULD perform scanning when detecting new BSs in
804 the received MOB_NBR-ADV messages in order to assure the included
805 neighbor information.
806
807 It is also possible that attackers try a DoS (Denial-of-Service)
808 attack by sending a flood of MOB_BSHO-REQ messages and triggering
809 LINK_HANDOVER_IMPEND primitives in the MN. But the IEEE 802.16e
810 provides a message authentication scheme for management messages
811 involved in handover as well as network entry procedures by using a
812 message authentication code (MAC) such as HMAC/CMAC (hashed/cipher
813 MAC). Thus, those management messages are protected from the
814 malicious use by attackers who intend to trigger LINK_HANDOVER_IMPEND
815 or LINK_UP primitives in the MN.
816
817 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgments</span>
818
819 Many thanks to the IETF Mobility Working Group members of KWISF
820 (Korea Wireless Internet Standardization Forum) for their efforts on
821 this work. In addition, we would like to thank Alper E. Yegin,
822 Jinhyeock Choi, Rajeev Koodli, Jonne Soininen, Gabriel Montenegro,
823 Singh Ajoy, Yoshihiro Ohba, Behcet Sarikaya, Vijay Devarapalli, and
824 Ved Kafle who have provided technical advice.
825
826 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
827
828 <span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
829
830 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
831 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
832
833
834
835
836 <span class="grey">Jang, et al. Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
839
840
841 [<a id="ref-RFC3775">RFC3775</a>] Johnson, D., Perkins, C., and J. Arkko, "Mobility
842 Support in IPv6", <a href="./rfc3775">RFC 3775</a>, June 2004.
843
844 [<a id="ref-RFC4862">RFC4862</a>] Thomson, S., Narten, T., and T. Jinmei, "IPv6
845 Stateless Address Autoconfiguration", <a href="./rfc4862">RFC 4862</a>,
846 September 2007.
847
848 [<a id="ref-RFC5268">RFC5268</a>] Koodli, R., Ed., "Mobile IPv6 Fast Handovers",
849 <a href="./rfc5268">RFC 5268</a>, June 2008.
850
851 [<a id="ref-IEEE802.16">IEEE802.16</a>] "IEEE Standard for Local and Metropolitan Area
852 Networks, Part 16: Air Interface for Fixed Broadband
853 Wireless Access Systems", IEEE Std 802.16-2004,
854 October 2004.
855
856 [<a id="ref-IEEE802.16e">IEEE802.16e</a>] "IEEE Standard for Local and Metropolitan Area
857 Networks, Amendment 2: Physical and Medium Access
858 Control Layers for Combined Fixed and Mobile Operation
859 in Licensed Bands and Corrigendum 1", IEEE
860 Std 802.16e-2005 and IEEE Std 802.16-2004/Cor 1-2005,
861 February 2006.
862
863 <span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
864
865 [<a id="ref-RFC4260">RFC4260</a>] McCann, P., "Mobile IPv6 Fast Handovers for 802.11
866 Networks", <a href="./rfc4260">RFC 4260</a>, November 2005.
867
868 [<a id="ref-RFC5184">RFC5184</a>] Teraoka, F., Gogo, K., Mitsuya, K., Shibui, R., and K.
869 Mitani, "Unified Layer 2 (L2) Abstractions for Layer 3
870 (L3)-Driven Fast Handover", <a href="./rfc5184">RFC 5184</a>, May 2008.
871
872 [<a id="ref-RFC4907">RFC4907</a>] Aboba, B., "Architectural Implications of Link
873 Indications", <a href="./rfc4907">RFC 4907</a>, June 2007.
874
875 [<a id="ref-IEEE802.21">IEEE802.21</a>] "Draft IEEE Standard for Local and Metropolitan Area
876 Networks: Media Independent Handover Services", IEEE
877 Std P802.21 D9.0, February 2008.
878
879 [<a id="ref-SH802.16e">SH802.16e</a>] Kim, K., Kim, C., and T. Kim, "A Seamless Handover
880 Mechanism for IEEE 802.16e Broadband Wireless Access",
881 International Conference on Computational Science vol.
882 2, pp.527-534, 2005.
883
884
885
886
887
888
889
890
891
892 <span class="grey">Jang, et al. Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
895
896
897 Authors' Addresses
898
899 Heejin Jang
900 SAMSUNG Advanced Institute of Technology
901 P.O. Box 111
902 Suwon 440-600
903 Korea
904
905 EMail: [email protected]
906
907
908 Junghoon Jee
909 Electronics and Telecommunications Research Institute
910 161 Gajeong-dong, Yuseong-gu
911 Daejon 305-350
912 Korea
913
914 EMail: [email protected]
915
916
917 Youn-Hee Han
918 Korea University of Technology and Education
919 Gajeon-ri, Byeongcheon-myeon
920 Cheonan 330-708
921 Korea
922
923 EMail: [email protected]
924
925
926 Soohong Daniel Park
927 SAMSUNG Electronics
928 416 Maetan-3dong, Yeongtong-gu
929 Suwon 442-742
930 Korea
931
932 EMail: [email protected]
933
934
935 Jaesun Cha
936 Electronics and Telecommunications Research Institute
937 161 Gajeong-dong, Yuseong-gu
938 Daejon 305-350
939 Korea
940
941 EMail: [email protected]
942
943
944
945
946
947
948 <span class="grey">Jang, et al. Informational [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc5270">RFC 5270</a> FMIPv6 over 802.16e June 2008</span>
951
952
953 Full Copyright Statement
954
955 Copyright (C) The IETF Trust (2008).
956
957 This document is subject to the rights, licenses and restrictions
958 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
959 retain all their rights.
960
961 This document and the information contained herein are provided on an
962 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
963 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
964 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
965 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
966 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
967 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
968
969 Intellectual Property
970
971 The IETF takes no position regarding the validity or scope of any
972 Intellectual Property Rights or other rights that might be claimed to
973 pertain to the implementation or use of the technology described in
974 this document or the extent to which any license under such rights
975 might or might not be available; nor does it represent that it has
976 made any independent effort to identify any such rights. Information
977 on the procedures with respect to rights in RFC documents can be
978 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>.
979
980 Copies of IPR disclosures made to the IETF Secretariat and any
981 assurances of licenses to be made available, or the result of an
982 attempt made to obtain a general license or permission for the use of
983 such proprietary rights by implementers or users of this
984 specification can be obtained from the IETF on-line IPR repository at
985 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
986
987 The IETF invites any interested party to bring to its attention any
988 copyrights, patents or patent applications, or other proprietary
989 rights that may cover technology that may be required to implement
990 this standard. Please address the information to the IETF at
991 [email protected].
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004 Jang, et al. Informational [Page 18]
1005 </pre>