Debian Codegraph @

rfc5142.html

raw
1 <pre>Network Working Group B. Haley
2 Request for Comments: 5142 Hewlett-Packard
3 Category: Standards Track V. Devarapalli
4 Azaire Networks
5 H. Deng
6 China Mobile
7 J. Kempf
8 DoCoMo USA Labs
9 January 2008
10
11
12 <span class="h1">Mobility Header Home Agent Switch Message</span>
13
14 Status of This Memo
15
16 This document specifies an Internet standards track protocol for the
17 Internet community, and requests discussion and suggestions for
18 improvements. Please refer to the current edition of the "Internet
19 Official Protocol Standards" (STD 1) for the standardization state
20 and status of this protocol. Distribution of this memo is unlimited.
21
22 Abstract
23
24 This document specifies a new Mobility Header message type that can
25 be used between a home agent and mobile node to signal to a mobile
26 node that it should acquire a new home agent.
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">Haley, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 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>. Scenarios .......................................................<a href="#page-3">3</a>
62 <a href="#section-3.1">3.1</a>. Overloaded .................................................<a href="#page-3">3</a>
63 <a href="#section-3.2">3.2</a>. Load Balancing .............................................<a href="#page-3">3</a>
64 <a href="#section-3.3">3.3</a>. Maintenance ................................................<a href="#page-3">3</a>
65 <a href="#section-3.4">3.4</a>. Functional Load Balancing ..................................<a href="#page-3">3</a>
66 <a href="#section-3.5">3.5</a>. Home Agent Renumbering .....................................<a href="#page-4">4</a>
67 <a href="#section-4">4</a>. Home Agent Switch Message .......................................<a href="#page-4">4</a>
68 <a href="#section-5">5</a>. Home Agent Operation ............................................<a href="#page-6">6</a>
69 <a href="#section-5.1">5.1</a>. Sending Home Agent Switch Messages .........................<a href="#page-6">6</a>
70 <a href="#section-5.2">5.2</a>. Retransmissions ............................................<a href="#page-7">7</a>
71 <a href="#section-5.3">5.3</a>. Mobile Node Errors .........................................<a href="#page-7">7</a>
72 <a href="#section-6">6</a>. Mobile Node Operation ...........................................<a href="#page-8">8</a>
73 <a href="#section-6.1">6.1</a>. Receiving Home Agent Switch Messages .......................<a href="#page-8">8</a>
74 <a href="#section-6.2">6.2</a>. Selecting a Home Agent .....................................<a href="#page-9">9</a>
75 <a href="#section-7">7</a>. Operational Considerations ......................................<a href="#page-9">9</a>
76 <a href="#section-8">8</a>. Protocol Constants .............................................<a href="#page-10">10</a>
77 <a href="#section-9">9</a>. IANA Considerations ............................................<a href="#page-10">10</a>
78 <a href="#section-10">10</a>. Security Considerations .......................................<a href="#page-10">10</a>
79 <a href="#section-11">11</a>. References ....................................................<a href="#page-11">11</a>
80 <a href="#section-11.1">11.1</a>. Normative References .....................................<a href="#page-11">11</a>
81 <a href="#section-11.2">11.2</a>. Informative References ...................................<a href="#page-11">11</a>
82 Acknowledgments ...................................................<a href="#page-11">11</a>
83
84 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
85
86 <a href="./rfc3775">RFC 3775</a> [<a href="./rfc3775" title="&quot;Mobility Support in IPv6&quot;">RFC3775</a>] contains no provision to allow a home agent to
87 inform a mobile node that it needs to stop acting as the home agent
88 for the mobile node. For example, a home agent may wish to handoff
89 some of its mobile nodes to another home agent because it has become
90 overloaded or it is going offline.
91
92 This protocol describes a signaling message, called the Home Agent
93 Switch message, that can be used to send a handoff notification
94 between a home agent and mobile node.
95
96 The Home Agent Switch message does not attempt to solve all general
97 problems related to changing the home agent of a mobile node. In
98 particular, this protocol does not attempt to solve:
99
100 o The case where the Home Address of a mobile node must change in
101 order to switch to a new home agent. This operation should be
102 avoided using this message.
103
104
105
106
107
108 <span class="grey">Haley, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
111
112
113 o Determining when a home agent should actively move mobile nodes
114 to another home agent. This decision should be made by a
115 backend protocol, for example, as described in [<a href="#ref-hareliability" title="&quot;Home Agent Reliability Protocol&quot;">hareliability</a>].
116
117 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
118
119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
121 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
122
123 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Scenarios</span>
124
125 Here are some example scenarios where a home agent signaling message
126 would be useful.
127
128 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Overloaded</span>
129
130 There are a number of reasons a home agent might be considered
131 overloaded. One might be that it is at, or near, its limit on the
132 number of home bindings it is willing to accept. Another is that it
133 has reached a pre-determined level of system resource usage --
134 memory, cpu cycles, etc. In either case, it would be desirable for a
135 home agent to reduce the number of home bindings before a failure
136 occurs.
137
138 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Load Balancing</span>
139
140 A home agent might know of other home agents that are not as heavily
141 loaded as itself, learned through some other mechanism outside the
142 scope of this document. An operator may wish to try and balance this
143 load so that a failure would disrupt a smaller percentage of mobile
144 nodes.
145
146 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Maintenance</span>
147
148 Most operators do periodic maintenance in order to maintain
149 reliability. If a home agent is being shutdown for maintenance, it
150 would be desirable to inform mobile nodes so they do not lose
151 mobility service.
152
153 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Functional Load Balancing</span>
154
155 A Mobile IPv6 home agent provides mobile nodes with two basic
156 services. It acts as a rendezvous server where correspondent nodes
157 can find the current care-of address for the mobile node, and as an
158 overlay router to tunnel traffic to/from the mobile node at its
159 current care-of address.
160
161
162
163
164 <span class="grey">Haley, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
167
168
169 A mobility service provider could have two sets of home agents to
170 handle the two functions. The rendezvous function could be handled
171 by a machine specialized for high-speed transaction processing, while
172 the overlay router function could be handled by a machine with high
173 data throughput.
174
175 A mobile node would start on the rendezvous server home agent and
176 stay there if it does route optimization. However, if the original
177 home agent detects that the mobile node is not doing route
178 optimization, but instead reverse-tunneling traffic, it could
179 redirect the mobile node to a home agent with better data throughput.
180
181 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Home Agent Renumbering</span>
182
183 Periodically, a mobility service provider may want to shut-down home
184 agent services at a set of IPv6 addresses and bring service back up
185 at a new set of addresses. Note that this may not involve anything
186 as complex as IPv6 network renumbering [<a href="./rfc4192" title="&quot;Procedures for Renumbering an IPv6 Network without a Flag Day&quot;">RFC4192</a>]; it may just involve
187 changing the addresses of the home agents. With a signaling message,
188 the service provider could inform mobile nodes to look for a new home
189 agent.
190
191 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Home Agent Switch Message</span>
192
193 The Home Agent Switch message is used by the home agent to signal to
194 the mobile node that it needs to stop acting as the home agent for
195 the mobile node, and that it should acquire a new home agent. Home
196 Agent Switch messages are sent as described in <a href="#section-5">Section 5</a>.
197
198 The message described below follows the Mobility Header format
199 specified in <a href="./rfc3775#section-6.1">Section&nbsp;6.1 of [RFC3775]</a>:
200
201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
202 | Payload Proto | Header Len | MH Type | Reserved |
203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
204 | Checksum | |
205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
206 | |
207 . .
208 . Message Data .
209 . .
210 | |
211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
212
213
214
215
216
217
218
219
220 <span class="grey">Haley, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
223
224
225 The Home Agent Switch Message uses the MH Type value (12). When this
226 value is indicated in the MH Type field, the format of the Message
227 Data field in the Mobility Header is as follows:
228
229 0 1 2 3
230 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
231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
232 |# of Addresses | Reserved |
233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
234 | |
235 + +
236 . .
237 . Home Agent Addresses .
238 . .
239 + +
240 | |
241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
242 | |
243 + +
244 . .
245 . Mobility Options .
246 . .
247 + +
248 | |
249 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
250
251 # of Addresses
252
253 An 8-bit unsigned integer indicating the number of IPv6 home agent
254 addresses in the message. If set to zero, the mobile node MUST
255 perform home agent discovery.
256
257 Reserved
258
259 An 8-bit field reserved for future use. The value MUST be
260 initialized to zero by the sender, and MUST be ignored by the
261 receiver.
262
263 Home Agent Addresses
264
265 A list of alternate home agent addresses for the mobile node. The
266 number of addresses present in the list is indicated by the "# of
267 Addresses" field in the Home Agent Switch message.
268
269
270
271
272
273
274
275
276 <span class="grey">Haley, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
279
280
281 Mobility Options
282
283 A Variable-length field of such length that the complete Mobility
284 Header is an integer multiple of 8 octets long. This field
285 contains zero or more TLV-encoded mobility options. The encoding
286 and format of defined options MUST follow the format specified in
287 <a href="./rfc3775#section-6.2">Section&nbsp;6.2 of [RFC3775]</a>. The receiver MUST ignore and skip any
288 options that it does not understand.
289
290 The Binding Refresh Advice mobility option defined in <a href="./rfc3775#section-6.2.4">Section</a>
291 <a href="./rfc3775#section-6.2.4">6.2.4 of [RFC3775]</a> is valid for the Home Agent Switch message.
292
293 If no home agent addresses and no options are present in this
294 message, no padding is necessary and the Header Len field in the
295 Mobility Header will be set to zero.
296
297 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Home Agent Operation</span>
298
299 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Sending Home Agent Switch Messages</span>
300
301 When sending a Home Agent Switch message, the sending node constructs
302 the packet as it would any other Mobility Header, except:
303
304 o The MH Type field MUST be set to (12).
305
306 o If alternative home agent addresses are known, the sending home
307 agent SHOULD include them in the list of suggested alternate
308 home agents. The home agent addresses field should be
309 constructed as described in <a href="./rfc3775#section-10.5.1">Section&nbsp;10.5.1 of [RFC3775]</a>, which
310 will randomize addresses of the same preference in the list.
311
312 o The "# of Addresses" field MUST be filled-in corresponding to
313 the number of home agent addresses included in the message. If
314 no addresses are present, the field MUST be set to zero,
315 forcing the mobile node to perform home agent discovery by some
316 other means.
317
318 o If the home agent is able to continue offering services to the
319 mobile node for some period of time, it MAY include a Binding
320 Refresh Advice mobility option indicating the time (in units of
321 4 seconds) until the binding will be deleted.
322
323 The Home Agent Switch message MUST use the home agent to mobile node
324 IPsec ESP (Encapsulating Security Payload) authentication SA
325 (Security Association) for integrity protection.
326
327
328
329
330
331
332 <span class="grey">Haley, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
335
336
337 A home agent SHOULD send a Home Agent Switch message when a known
338 period of unavailability is pending so the mobile node has sufficient
339 time to find another suitable home agent.
340
341 The sending node does not need to be the current home agent for the
342 mobile node, for example as described in [<a href="#ref-hareliability" title="&quot;Home Agent Reliability Protocol&quot;">hareliability</a>], but it MUST
343 have a security association with the mobile node so the message is
344 not rejected. In this case, the Home Agent Switch message SHOULD
345 only contain the address of the home agent sending the message in the
346 Home Agent Addresses field, which implies that the mobile node should
347 switch to using the sender as its new home agent.
348
349 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Retransmissions</span>
350
351 If the home agent does not receive a response from the mobile node --
352 either a Binding Update message to delete its home binding if it is
353 the current home agent, or a Binding Update message to create a home
354 binding if it is not the current home agent -- then it SHOULD
355 retransmit the message until a response is received. The initial
356 value for the retransmission timer is INITIAL-HA-SWITCH-TIMEOUT.
357
358 The retransmissions by the home agent MUST use an exponential back-
359 off mechanism, in which the timeout period is doubled upon each
360 retransmission, until either the home agent gets a response from the
361 mobile node to delete its binding, or the timeout period reaches the
362 value MAX-HA-SWITCH-TIMEOUT. The home agent MAY continue to send
363 these messages at this slower rate indefinitely.
364
365 If the home agent included a Binding Refresh Advice mobility option,
366 then it SHOULD delay any retransmissions until at least one half of
367 the time period has expired, or INITIAL-HA-SWITCH-TIMEOUT, whichever
368 value is less.
369
370 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Mobile Node Errors</span>
371
372 If a mobile node does not understand how to process a Home Agent
373 Switch message, it will send a Binding Error message as described in
374 <a href="#section-6.1">Section 6.1</a>.
375
376 If a mobile node is unreachable, in other words, it still has a home
377 binding with the home agent after reaching the timeout period of MAX-
378 HA-SWITCH-TIMEOUT, the home agent SHOULD NOT make any conclusions
379 about its status.
380
381 In either case, the home agent SHOULD attempt to continue providing
382 services until the lifetime of the binding expires.
383
384
385
386
387
388 <span class="grey">Haley, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
391
392
393 Attempts by the mobile node to extend the binding lifetime with a
394 Binding Update message SHOULD be rejected, and a Binding
395 Acknowledgement SHOULD be returned with status value 129
396 (Administratively prohibited) as specified in <a href="./rfc3775#section-6.1.8">Section&nbsp;6.1.8 of
397 [RFC3775]</a>.
398
399 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Mobile Node Operation</span>
400
401 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Receiving Home Agent Switch Messages</span>
402
403 Upon receiving a Home Agent Switch message, the Mobility Header MUST
404 be verified as specified in [<a href="./rfc3775" title="&quot;Mobility Support in IPv6&quot;">RFC3775</a>], specifically:
405
406 o The Checksum, MH type, Payload Proto, and Header Len fields
407 MUST meet the requirements of <a href="./rfc3775#section-9.2">Section&nbsp;9.2 of [RFC3775]</a>.
408
409 o The packet MUST be covered by the home agent to mobile node
410 IPsec ESP authentication SA for integrity protection.
411
412 If the packet is dropped due to the above tests, the receiving node
413 MUST follow the processing rules as <a href="./rfc3775#section-9.2">Section&nbsp;9.2 of [RFC3775]</a> defines.
414 For example, it MUST send a Binding Error message with the Status
415 field set to 2 (unrecognized MH Type value) if it does not support
416 the message type.
417
418 Upon receipt of a Home Agent Switch message, the mobile node MUST
419 stop using its current home agent for services and MUST delete its
420 home binding by sending a Binding Update message as described in
421 <a href="./rfc3775#section-11.7.1">Section&nbsp;11.7.1 of [RFC3775]</a>. This acts as an acknowledgement of the
422 Home Agent Switch message. Alternately, if the sender of the message
423 is not the current home agent, sending a Binding Update message to
424 create a home binding will act as an acknowledgement of the Home
425 Agent Switch message. Retransmissions of Binding Update messages
426 MUST use the procedures described in <a href="./rfc3775#section-11.8">Section&nbsp;11.8 of [RFC3775]</a>.
427
428 If a Binding Refresh Advice mobility option is present, the mobile
429 node MAY delay the deletion of its home binding and continue to use
430 its current home agent until the calculated time period has expired.
431
432 If the Home Agent Switch message contains a list of alternate home
433 agent addresses, the mobile node SHOULD select a new home agent as
434 described in <a href="#section-6.2">Section 6.2</a>, and establish the necessary IPsec security
435 associations with the new home agent by whatever means required as
436 part of the mobile node/home agent bootstrapping protocol for the
437 home agent's mobility service provider. If no alternate home agent
438 addresses are included in the list, the mobile node MUST first
439 perform home agent discovery.
440
441
442
443
444 <span class="grey">Haley, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
447
448
449 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Selecting a Home Agent</span>
450
451 In most cases, the home agent addresses in the Home Agent Switch
452 message will be of other home agents on the home link of the mobile
453 node (the computed prefix is the same). In this case, the mobile
454 node SHOULD select a new home agent from the addresses as they are
455 ordered in the list. If the first address in the list is unable to
456 provide service, then the subsequent addresses in the list should be
457 tried in-order.
458
459 In the case that the home agent addresses in the Home Agent Switch
460 message are not all home agents on the home link of the mobile node
461 (the computed prefix is different), the mobile node SHOULD select one
462 with its home network prefix first, if available, followed by home
463 agents with other prefixes. Choosing a home agent with a different
464 prefix might require a change of the home address for the mobile
465 node, which could cause a loss of connectivity for any connections
466 using the current home address.
467
468 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Operational Considerations</span>
469
470 This document does not specify how an operator might use the Home
471 Agent Switch message in its network. However, the following
472 requirements are placed on its usage:
473
474 o The use of this message needs to take into account possible
475 signaling overhead, congestion, load from the mechanism itself,
476 and the resulting registration to another home agent. A home
477 agent may provide service for thousands, if not millions, of
478 mobile nodes. Careless application of the Home Agent Switch
479 message may cause the new home agent, or some other parts of
480 the network, to suffer. As a result, it is REQUIRED that
481 applications of this message either employ a feedback loop
482 between resources of the new home agent and the sending of
483 additional Home Agent Switch messages, or apply a maximum rate
484 at which mobile nodes can be informed of the switch that is far
485 below the designated capacity of new registrations that the set
486 of home agents can process. If no other information is
487 available, this maximum rate should default to MAX-HA-SWITCH-
488 TRANSMIT-RATE.
489
490 o In general, switching the home agent of a mobile node should
491 only be done when absolutely necessary, since it might cause a
492 service disruption if the switch to a new home agent fails, the
493 new home agent is itself under an overload condition, or the
494 network connection of the new home agent is congested.
495
496
497
498
499
500 <span class="grey">Haley, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
503
504
505 Similarly, the path characteristics via the new home agent may
506 be different, which may cause temporary difficulties for end-
507 to-end transport layer operation.
508
509 o If this message is being used for load-balancing between a set
510 of home agents, they should all be configured with the same set
511 of prefixes so a home agent switch does not require a change of
512 the home address for a mobile node. That operation is NOT
513 RECOMMENDED and should be avoided.
514
515 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Protocol Constants</span>
516
517 INITIAL-HA-SWITCH-TIMEOUT 5 seconds
518 MAX-HA-SWITCH-TIMEOUT 20 seconds
519 MAX-HA-SWITCH-TRANSMIT-RATE 1 per second
520
521 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. IANA Considerations</span>
522
523 IANA has assigned a new Mobility Header type for the following new
524 message described in <a href="#section-4">Section 4</a>:
525
526 (12) Home Agent Switch message
527
528 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span>
529
530 As with other messages in [<a href="./rfc3775" title="&quot;Mobility Support in IPv6&quot;">RFC3775</a>], the Home Agent Switch message
531 MUST use the home agent to mobile node ESP encryption SA for
532 confidentiality protection, and MUST use the home agent to mobile
533 node ESP authentication SA for integrity protection.
534
535 The Home Agent Switch message MAY use the IPsec ESP SA in place for
536 Binding Updates and Acknowledgements, as specified in <a href="./rfc3775#section-5.1">Section&nbsp;5.1 of
537 [RFC3775]</a>, in order to reduce the number of configured security
538 associations. This also gives the message authenticity protection.
539
540 Some operators may not want to reveal the list of home agents to on-
541 path listeners. In such a case, the Home Agent Switch message should
542 use the home agent to mobile node IPsec ESP encryption SA for
543 confidentiality protection.
544
545
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Haley, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
559
560
561 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
562
563 <span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
564
565 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
566 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
567
568 [<a id="ref-RFC3775">RFC3775</a>] Johnson, D., Perkins, C., and J. Arkko, "Mobility
569 Support in IPv6", <a href="./rfc3775">RFC 3775</a>, June 2004.
570
571 <span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
572
573 [<a id="ref-RFC4192">RFC4192</a>] Baker, F., Lear, E., and R. Droms, "Procedures for
574 Renumbering an IPv6 Network without a Flag Day", <a href="./rfc4192">RFC</a>
575 <a href="./rfc4192">4192</a>, September 2005.
576
577 [<a id="ref-hareliability">hareliability</a>] Wakikawa, R., Ed., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22Home+Agent+Reliability+Protocol%22'>"Home Agent Reliability Protocol"</a>,
578 Work in Progress, November 2007.
579
580 Acknowledgments
581
582 We would like to thank the authors of a number of previous documents
583 that contributed content to this RFC:
584
585 o Ryuji Wakikawa, Pascal Thubert, and Vijay Devarapalli,
586 "Inter Home Agents Protocol Specification", March 2006.
587
588 o Hui Deng, Brian Haley, Xiaodong Duan, Rong Zhang, and Kai Zhang,
589 "Load Balance for Distributed Home Agents in Mobile IPv6",
590 October 2004.
591
592 o James Kempf, "Extension to <a href="./rfc3775">RFC 3775</a> for Alerting the Mobile Node
593 to Home Agent Unavailability", October 2005.
594
595 o Brian Haley and Sri Gundavelli, "Mobility Header Signaling
596 Message", September 2007.
597
598 Thanks also to Kilian Weniger, Jixing Liu, Alexandru Petrescu, Jouni
599 Korhonen, and Wolfgang Fritsche for their review and feedback.
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Haley, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
615
616
617 Author's Addresses
618
619 Brian Haley
620 Hewlett-Packard Company
621 110 Spitbrook Road
622 Nashua, NH 03062, USA
623 EMail: [email protected]
624
625 Vijay Devarapalli
626 Azaire Networks
627 3121 Jay Street
628 Santa Clara, CA 95054 USA
629 EMail: [email protected]
630
631 James Kempf
632 DoCoMo USA Labs
633 181 Metro Drive
634 Suite 300
635 San Jose, CA 95110 USA
636 EMail: [email protected]
637
638 Hui Deng
639 China Mobile
640 53A, Xibianmennei Ave.
641 Xuanwu District
642 Beijing 100053
643 China
644 EMail: [email protected]
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Haley, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5142">RFC 5142</a> Home Agent Switch Message January 2008</span>
671
672
673 Full Copyright Statement
674
675 Copyright (C) The IETF Trust (2008).
676
677 This document is subject to the rights, licenses and restrictions
678 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
679 retain all their rights.
680
681 This document and the information contained herein are provided on an
682 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
683 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
684 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
685 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
686 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
687 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
688
689 Intellectual Property
690
691 The IETF takes no position regarding the validity or scope of any
692 Intellectual Property Rights or other rights that might be claimed to
693 pertain to the implementation or use of the technology described in
694 this document or the extent to which any license under such rights
695 might or might not be available; nor does it represent that it has
696 made any independent effort to identify any such rights. Information
697 on the procedures with respect to rights in RFC documents can be
698 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>.
699
700 Copies of IPR disclosures made to the IETF Secretariat and any
701 assurances of licenses to be made available, or the result of an
702 attempt made to obtain a general license or permission for the use of
703 such proprietary rights by implementers or users of this
704 specification can be obtained from the IETF on-line IPR repository at
705 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
706
707 The IETF invites any interested party to bring to its attention any
708 copyrights, patents or patent applications, or other proprietary
709 rights that may cover technology that may be required to implement
710 this standard. Please address the information to the IETF at
711 [email protected].
712
713
714
715
716
717
718
719
720
721
722
723
724 Haley, et al. Standards Track [Page 13]
725 </pre>