Debian Codegraph @

rfc6611.html

raw
1 <pre>Internet Engineering Task Force (IETF) K. Chowdhury, Ed.
2 Request for Comments: 6611 Radio Mobile Access, Inc.
3 Category: Standards Track A. Yegin
4 ISSN: 2070-1721 Samsung
5 May 2012
6
7
8 <span class="h1">Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario</span>
9
10 Abstract
11
12 Mobile IPv6 bootstrapping can be categorized into two primary
13 scenarios: the split scenario and the integrated scenario. In the
14 split scenario, the mobile node's mobility service is authorized by a
15 different service authorizer than the network access authorizer. In
16 the integrated scenario, the mobile node's mobility service is
17 authorized by the same service authorizer as the network access
18 service authorizer. This document defines a method for home agent
19 information discovery for the integrated scenario.
20
21 Status of This Memo
22
23 This is an Internet Standards Track document.
24
25 This document is a product of the Internet Engineering Task Force
26 (IETF). It represents the consensus of the IETF community. It has
27 received public review and has been approved for publication by the
28 Internet Engineering Steering Group (IESG). Further information on
29 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
30
31 Information about the current status of this document, any errata,
32 and how to provide feedback on it may be obtained at
33 <a href="http://www.rfc-editor.org/info/rfc6611">http://www.rfc-editor.org/info/rfc6611</a>.
34
35 Copyright Notice
36
37 Copyright (c) 2012 IETF Trust and the persons identified as the
38 document authors. All rights reserved.
39
40 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
41 Provisions Relating to IETF Documents
42 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
43 publication of this document. Please review these documents
44 carefully, as they describe your rights and restrictions with respect
45 to this document. Code Components extracted from this document must
46 include Simplified BSD License text as described in Section 4.e of
47 the Trust Legal Provisions and are provided without warranty as
48 described in the Simplified BSD License.
49
50
51
52 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
55
56
57 This document may contain material from IETF Documents or IETF
58 Contributions published or made publicly available before November
59 10, 2008. The person(s) controlling the copyright in some of this
60 material may not have granted the IETF Trust the right to allow
61 modifications of such material outside the IETF Standards Process.
62 Without obtaining an adequate license from the person(s) controlling
63 the copyright in such materials, this document may not be modified
64 outside the IETF Standards Process, and derivative works of it may
65 not be created outside the IETF Standards Process, except to format
66 it for publication as an RFC or to translate it into languages other
67 than English.
68
69 Table of Contents
70
71 <a href="#section-1">1</a>. Introduction and Scope ..........................................<a href="#page-2">2</a>
72 <a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
73 <a href="#section-3">3</a>. Assumptions and Conformance .....................................<a href="#page-4">4</a>
74 <a href="#section-4">4</a>. Solution Overview ...............................................<a href="#page-5">5</a>
75 <a href="#section-4.1">4.1</a>. Logical View of the Integrated Scenario ....................<a href="#page-5">5</a>
76 <a href="#section-4.2">4.2</a>. Bootstrapping Message Sequence .............................<a href="#page-6">6</a>
77 <a href="#section-4.2.1">4.2.1</a>. Home Agent Allocation in the MSP ....................<a href="#page-7">7</a>
78 <a href="#section-4.2.2">4.2.2</a>. Home Agent Allocation in the ASP ....................<a href="#page-9">9</a>
79 <a href="#section-4.3">4.3</a>. Bootstrapping Message Sequence: Fallback Case .............<a href="#page-10">10</a>
80 4.4. HoA and IKEv2 SA Bootstrapping in the Integrated
81 Scenario ..................................................<a href="#page-10">10</a>
82 <a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-10">10</a>
83 <a href="#section-6">6</a>. Acknowledgements ...............................................<a href="#page-11">11</a>
84 <a href="#section-7">7</a>. Contributors ...................................................<a href="#page-11">11</a>
85 <a href="#section-8">8</a>. References .....................................................<a href="#page-11">11</a>
86 <a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-11">11</a>
87 <a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-12">12</a>
88
89 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction and Scope</span>
90
91 The Mobile IPv6 protocol [<a href="./rfc6275" title="&quot;Mobility Support in IPv6&quot;">RFC6275</a>] requires the mobile node to have
92 the following information:
93
94 o the Home Address (HoA),
95
96 o the home agent address, and
97
98 o the cryptographic materials for establishing an IPsec security
99 association with the home agent.
100
101
102
103
104
105
106
107
108 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
111
112
113 The cryptographic materials need to be established prior to
114 initiating the registration process. The mechanism via which the
115 mobile node obtains this information is called "Mobile IPv6
116 bootstrapping". In order to allow a flexible deployment model for
117 Mobile IPv6, it is desirable to define a bootstrapping mechanism for
118 the mobile node to acquire these parameters dynamically. [<a href="./rfc4640" title="&quot;Problem Statement for bootstrapping Mobile IPv6 (MIPv6)&quot;">RFC4640</a>]
119 describes the problem statement for Mobile IPv6 bootstrapping. It
120 also defines the bootstrapping scenarios based on the relationship
121 between the entity that authenticates and authorizes the mobile node
122 for network access (i.e., the Access Service Authorizer, ASA) and the
123 entity that authenticates and authorizes the mobile node for mobility
124 service (i.e., the Mobility Service Authorizer, MSA). The scenario
125 in which the Access Service Authorizer is not the Mobility Service
126 Authorizer is called the "split" scenario. The bootstrapping
127 solution for the split scenario is defined in [<a href="./rfc5026" title="&quot;Mobile IPv6 Bootstrapping in Split Scenario&quot;">RFC5026</a>]. The
128 scenario in which the Access Service Authorizer is also the Mobility
129 Service Authorizer is called the "integrated" scenario. This
130 document defines a bootstrapping solution for the integrated
131 scenario.
132
133 [<a id="ref-RFC5026">RFC5026</a>] identifies four different components of the bootstrapping
134 problem: home agent address discovery, HoA assignment, IPsec Security
135 Association [<a href="./rfc4301" title="&quot;Security Architecture for the Internet Protocol&quot;">RFC4301</a>] setup, and Authentication and Authorization
136 with the MSA. This document defines a mechanism for home agent
137 address discovery. The other components of bootstrapping are as per
138 [<a href="./rfc5026" title="&quot;Mobile IPv6 Bootstrapping in Split Scenario&quot;">RFC5026</a>].
139
140 In the integrated scenario, the bootstrapping of the home agent
141 information can be achieved via DHCPv6. This document defines the
142 MIPv6 bootstrapping procedures for the integrated scenario. It
143 enables home agent assignment in the integrated scenario by utilizing
144 DHCP and Authentication, Authorization, and Accounting (AAA)
145 protocols. The specification utilizes DHCP and AAA options and
146 attribute-value pairs (AVPs) that are defined in [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>] and
147 [<a href="./rfc5447" title="&quot;Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction&quot;">RFC5447</a>]. This document specifies the interworking among Mobile
148 Node (MN), Network Access Server (NAS), DHCP, and AAA entities for
149 the bootstrapping procedure in the integrated scenario.
150
151 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
152
153 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
154 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
155 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>].
156
157
158
159
160
161
162
163
164 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
167
168
169 General mobility terminology can be found in [<a href="./rfc3753" title="&quot;Mobility Related Terminology&quot;">RFC3753</a>]. The
170 following additional terms, as defined in [<a href="./rfc4640" title="&quot;Problem Statement for bootstrapping Mobile IPv6 (MIPv6)&quot;">RFC4640</a>], are used in this
171 document:
172
173 Access Service Authorizer (ASA): A network operator that
174 authenticates a mobile node and establishes the mobile node's
175 authorization to receive Internet service.
176
177 Access Service Provider (ASP): A network operator that provides
178 direct IP packet forwarding to and from the mobile node.
179
180 Mobility Service Authorizer (MSA): A service provider that authorizes
181 Mobile IPv6 service.
182
183 Mobility Service Provider (MSP): A service provider that provides
184 Mobile IPv6 service. An MSP is called a "home MSP" when MSP == MSA.
185 In this document, the term MSP means a Mobility Service Provider that
186 has a roaming relationship with the MSA but it is not the MSA.
187
188 Split Scenario: A scenario where the mobility service and the network
189 access service are authorized by different entities.
190
191 Integrated Scenario: A scenario where the mobility service and the
192 network access service are authorized by the same entity.
193
194 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Assumptions and Conformance</span>
195
196 The following assumptions are made in this document:
197
198 (a) MSA == ASA.
199
200 (b) MSA and MSP have a roaming relationship.
201
202 (c) DHCP relay and NAS are either co-located or there is a mechanism
203 to transfer received AAA information from the NAS to the DHCP
204 relay.
205
206 Note: If assignment of a home agent in the home MSP is not
207 required by a deployment, co-location of the NAS and the DHCP
208 relay functions or a mechanism to transfer received AAA
209 information from the NAS to the DHCP relay won't be
210 necessary. In such a case, only the implementation of the
211 options and procedures defined in [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>] should suffice.
212
213 (d) The NAS shall support MIPv6-specific AAA attributes as specified
214 in [<a href="./rfc5447" title="&quot;Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction&quot;">RFC5447</a>].
215
216
217
218
219
220 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
223
224
225 (e) The AAA server in the home domain (AAAH) used for network access
226 authentication (ASA) has access to the same database as the AAAH
227 used for the mobility service authentication (MSA).
228
229 If home agent assignment is required only in the ASP by the
230 deployment, a minimal implementation of this specification MAY only
231 support the delivery of information from the DHCP server to the DHCP
232 client through [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>]. However, if home agent assignment in the
233 MSP is required by the deployment, an implementation conforming to
234 this specification SHALL be able to transfer the information received
235 from the AAA server to the NAS, and from the NAS to the DHCP relay
236 function. This can be achieved either by co-locating the NAS and the
237 DHCP relay functions or via an interface between these functions.
238 The details of this interface are out of the scope of this
239 specification.
240
241 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Solution Overview</span>
242
243 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Logical View of the Integrated Scenario</span>
244
245 In the integrated scenario, the mobile node utilizes the network
246 access authentication process to bootstrap Mobile IPv6. It is
247 assumed that the access service authorizer is mobility service aware.
248 This allows for Mobile IPv6 bootstrapping at the time of access
249 authentication and authorization. Also, the mechanism defined in
250 this document requires the NAS to support MIP6-specific AAA
251 attributes and a co-located DHCP relay agent.
252
253 Figure 1 shows the AAA infrastructure with a AAA client (NAS), a AAA
254 proxy in the visited network (AAAV), and a AAA server in the home
255 network (AAAH).
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
279
280
281 |
282 ASP(/MSP) | ASA/MSA(/MSP)
283 |
284 |
285 +-------+ | +-------+
286 | | | | |
287 |AAAV |-----------|--------|AAAH |
288 | | | | |
289 +-------+ | +-------+
290 | |
291 | |
292 | |
293 | |
294 +-----+ +------+ |
295 +----+ | NAS/| |DHCP | |
296 | MN |------|DHCP |----|Server| |
297 +----+ |Relay| | | |
298 +-----+ +------+ |
299 |
300 |
301 +--------+ | +--------+
302 | HA | | | HA |
303 | in ASP | | |in MSP |
304 +--------+ | +--------+
305
306 Figure 1: Integrated Scenario, Network Diagram with DHCP Server
307
308 The user's home network authorizes the mobile node for network access
309 and mobility services. Note that usage of a home agent with the
310 mobile node might be selected in the access service provider's
311 network or alternatively in the mobility service provider's network.
312
313 The MSP may be co-located with the ASP, or the ASA/MSA, or
314 independent of the two.
315
316 The mobile node interacts with the DHCP server via the relay agent
317 after the network access authentication as part of the mobile node
318 configuration procedure.
319
320 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Bootstrapping Message Sequence</span>
321
322 In this case, the mobile node is able to acquire the home agent
323 address via a DHCPv6 query. In the integrated scenario, the ASA and
324 the MSA are the same; it can be safely assumed that the AAAH used for
325 network access authentication (ASA) has access to the same database
326 as the AAAH used for the mobility service authentication (MSA).
327 Hence, the same AAAH can authorize the mobile node for network access
328
329
330
331
332 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
335
336
337 and mobility service at the same time. When the MN performs Mobile
338 IPv6 registration, the AAAH ensures that the MN is accessing the
339 assigned home agent for that MSP.
340
341 Figure 2 shows the message sequence for home agent allocation in both
342 scenarios -- HA in the ASP (which is co-located with the MSP), or HA
343 in an MSP that is separate from ASP and possibly from the ASA/MSA as
344 well.
345
346 |
347 --------------ASP------&gt;|&lt;--ASA+MSA--
348 |
349 +----+ +------+ +-------+ +-----+
350 | | | | | | | |
351 | MN/| |NAS/ | | DHCP | |AAAH |
352 |User| |DHCP | | Server| | |
353 | | |relay | | | | |
354 +----+ +------+ +-------+ +-----+
355 | | | |
356 | 1 | 1 | |
357 |&lt;-------------&gt;|&lt;----------------------&gt;|
358 | | | |
359 | | | |
360 | 2 | | |
361 |--------------&gt;| | |
362 | | | |
363 | | 3 | |
364 | |------------&gt;| |
365 | | | |
366 | | 4 | |
367 | |&lt;------------| |
368 | | | |
369 | 5 | | |
370 |&lt;--------------| | |
371 | | | |
372
373 Figure 2: Message Sequence for Home Agent Allocation
374
375 <span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. Home Agent Allocation in the MSP</span>
376
377 This section describes a scenario where the home agent is allocated
378 in the mobile node's MSP network(s) that is (are) not co-located with
379 the ASP. In order to provide the mobile node with information about
380 the assigned home agent, the AAAH conveys the assigned home agent's
381 information to the NAS via a AAA protocol, e.g., [<a href="./rfc5447" title="&quot;Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction&quot;">RFC5447</a>].
382
383 Figure 2 shows the message sequence for home agent allocation. In
384 the scenario with HA in the MSP, the following details apply.
385
386
387
388 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
391
392
393 (1) The mobile node executes the network access authentication
394 procedure (e.g., IEEE 802.11i/802.1X), and it interacts with the
395 NAS. The NAS is in the ASP, and it interacts with the AAAH,
396 which is in the ASA/MSA, to authenticate the mobile node. In
397 the process of authorizing the mobile node, the AAAH verifies in
398 the AAA profile that the mobile node is allowed to use the
399 Mobile IPv6 service. The AAAH assigns a home agent in the home
400 MSP, and it assigns one or more home agents in other authorized
401 MSPs and returns this information to the NAS. The NAS may keep
402 the received information for a configurable duration, or it may
403 keep the information for as long as the MN is connected to the
404 NAS.
405
406 (2) The mobile node sends a DHCPv6 Information-request message
407 [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] to the All_DHCP_Relay_Agents_and_Servers multicast
408 address. In this message, the mobile node (DHCP client) SHALL
409 include the following:
410
411 * the Option Code for the Visited Home Network Information
412 option [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>] in the OPTION_ORO.
413
414 * Client Home Network ID FQDN option identifying the MSP.
415
416 * the OPTION_CLIENTID to identify itself to the DHCP server
417
418 (3) The relay agent intercepts the Information Request from the
419 mobile node and forwards it to the DHCP server. The relay agent
420 also includes the received home agent information from the AAAH
421 in the Relay-Supplied Options option [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>]. If a NAS
422 implementation does not store the received information as long
423 as the MN's session remains in the ASP, and if the MN delays
424 sending a DHCP request, the NAS/DHCP relay does not include the
425 Relay-Supplied Options option in the Relay Forward message.
426
427 (4) The DHCP server:
428
429 * identifies the client by looking at the DHCP Unique
430 Identifier (DUID) for the client in the OPTION_CLIENTID.
431
432 * determines that the mobile node is requesting home agent
433 information in the MSP by looking at the Home Network ID FQDN
434 option.
435
436 * determines that the home agent is allocated by the AAAH by
437 looking at the Relay-Supplied Options option.
438
439
440
441
442
443
444 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
447
448
449 * extracts the allocated home agent information from the Relay-
450 Supplied Options option and includes it in the Identified
451 Home Network Information option [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>] in the Reply
452 Message. If the requested information is not available in
453 the DHCP server, it follows the behavior described in
454 [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>].
455
456 (5) The relay agent relays the Reply Message from the DHCP server to
457 the mobile node. At this point, the mobile node has the home
458 agent information that it requested.
459
460 <span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Home Agent Allocation in the ASP</span>
461
462 This section describes a scenario where the mobile node requests home
463 agent allocation in the ASP by setting the id-type field to zero in
464 the Home Network Identifier Option [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>] in the DHCPv6 request
465 message. In this scenario, the ASP becomes the MSP for the duration
466 of the network access authentication session.
467
468 Figure 2 shows the message sequence for home agent allocation. In
469 the scenario with HA in the ASP, the following details apply.
470
471 (1) The mobile node executes the network access authentication
472 procedure (e.g., IEEE 802.11i/802.1X) and interacts with the
473 NAS. The NAS is in the ASP, and it interacts with the AAAH,
474 which is in the ASA/MSA, to authenticate the mobile node. In
475 the process of authorizing the mobile node, the AAAH verifies in
476 the AAA profile that the mobile node is allowed to use the
477 Mobile IPv6 services. The AAAH assigns a home agent in the home
478 MSP, and it assigns one or more home agents in other authorized
479 MSPs and returns this information to the NAS. Note that the
480 AAAH is not aware of the fact that the mobile node prefers a
481 home agent allocation in the ASP. Therefore, the assigned home
482 agent may not be used by the mobile node. This leaves the
483 location of the mobility anchor point decision to the mobile
484 node.
485
486 (2) The mobile node sends a DHCPv6 Information Request message
487 [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] to the All_DHCP_Relay_Agents_and_Servers multicast
488 address. In this message, the mobile node (DHCP client) SHALL
489 include the following:
490
491 * the Option Code for the Home Network Identifier Option
492 [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>] in the OPTION_ORO.
493
494 * the OPTION_CLIENTID to identify itself to the DHCP server.
495
496
497
498
499
500 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
503
504
505 (3) The relay agent (which is the NAS) intercepts the Information
506 Request from the mobile node and forwards it to the DHCP server.
507 The relay agent also includes the received AAA AVP from the AAAH
508 in the Relay-Supplied Options option [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>].
509
510 (4) The DHCP server identifies the client by looking at the DUID for
511 the client in the OPTION_CLIENTID. The DHCP server also
512 determines that the mobile node is requesting home agent
513 information in the ASP by looking at the Visited Home Network
514 Information option. If configured to do so, the DHCP server
515 allocates a home agent from its configured list of home agents
516 and includes it in the Visited Home Network Information Option
517 [<a href="./rfc6610" title="&quot;DHCP Option for Home Agent Discovery in Mobile IPv6 (MIPv6)&quot;">RFC6610</a>] in the Reply Message. Note that in this case, the
518 DHCP server does not use the received information in the Relay-
519 Supplied Options option.
520
521 (5) The relay agent relays the Reply Message from the DHCP server to
522 the mobile node. At this point, the mobile node has the home
523 agent information that it requested.
524
525 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Bootstrapping Message Sequence: Fallback Case</span>
526
527 In the fallback case, the mobile node is not able to acquire the home
528 agent information via DHCPv6. The mobile node MAY perform DNS
529 queries to discover the home agent address as defined in [<a href="./rfc5026" title="&quot;Mobile IPv6 Bootstrapping in Split Scenario&quot;">RFC5026</a>].
530 To perform DNS-based home agent discovery, the mobile node needs to
531 know the DNS server address. The details of how the MN is configured
532 with the DNS server address are outside the scope of this document.
533
534 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. HoA and IKEv2 SA Bootstrapping in the Integrated Scenario</span>
535
536 In the integrated scenario, the HoA, IPsec Security Association
537 setup, and Authentication and Authorization with the MSA are
538 bootstrapped via the same mechanism as described in the bootstrapping
539 solution for the split scenario [<a href="./rfc5026" title="&quot;Mobile IPv6 Bootstrapping in Split Scenario&quot;">RFC5026</a>].
540
541 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
542
543 The transport of the assigned home agent information via the AAA
544 infrastructure (i.e., from the AAA server to the AAA client) to the
545 NAS may only be integrity protected as per standard Diameter or other
546 AAA protocol security mechanisms. No additional security
547 considerations are imposed by the usage of this document. The
548 security mechanisms provided by [<a href="./rfc3588" title="&quot;Diameter Base Protocol&quot;">RFC3588</a>] are applicable for this
549 purpose. This document does not introduce any new security issues to
550 Mobile IPv6.
551
552
553
554
555
556 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
559
560
561 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
562
563 The authors would like to thank Kilian Weniger, Vidya Narayanan, and
564 George Tsirtsis for their review and comments. Thanks to Alfred
565 Hoenes for thorough review and valuable suggestions to improve the
566 readability of the document.
567
568 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Contributors</span>
569
570 This contribution is a joint effort of the bootstrapping solution
571 design team of the MEXT WG. The contributors include Jari Arkko,
572 Julien Bournelle, Kuntal Chowdhury, Vijay Devarapalli, Gopal Dommety,
573 Gerardo Giaretta, Junghoon Jee, James Kempf, Alpesh Patel, Basavaraj
574 Patil, Hannes Tschofenig, and Alper Yegin.
575
576 The design team members can be reached at the following email
577 addresses:
578
579 Jari Arkko [email protected]
580 Julien Bournelle [email protected]
581 Kuntal Chowdhury [email protected]
582 Vijay Devarapalli [email protected]
583 Gopal Dommety [email protected]
584 Gerardo Giaretta [email protected]
585 Junghoon Jee [email protected]
586 James Kempf [email protected]
587 Alpesh Patel [email protected]
588 Basavaraj Patil [email protected]
589 Hannes Tschofenig [email protected]
590 Alper Yegin [email protected]
591
592 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
593
594 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
595
596 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
597 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
598
599 [<a id="ref-RFC3315">RFC3315</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
600 and M. Carney, "Dynamic Host Configuration Protocol for
601 IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003.
602
603 [<a id="ref-RFC3588">RFC3588</a>] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
604 Arkko, "Diameter Base Protocol", <a href="./rfc3588">RFC 3588</a>, September 2003.
605
606
607
608
609
610
611
612 <span class="grey">Chowdhury &amp; Yegin 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="./rfc6611">RFC 6611</a> MIPv6 Bootstrapping Integrated Scenario May 2012</span>
615
616
617 [<a id="ref-RFC5026">RFC5026</a>] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6
618 Bootstrapping in Split Scenario", <a href="./rfc5026">RFC 5026</a>, October 2007.
619
620 [<a id="ref-RFC5447">RFC5447</a>] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C.,
621 and K. Chowdhury, "Diameter Mobile IPv6: Support for
622 Network Access Server to Diameter Server Interaction",
623 <a href="./rfc5447">RFC 5447</a>, February 2009.
624
625 [<a id="ref-RFC6275">RFC6275</a>] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support
626 in IPv6", <a href="./rfc6275">RFC 6275</a>, July 2011.
627
628 [<a id="ref-RFC6610">RFC6610</a>] Jang, H., Yegin, A., Chowdhury, K., Choi, J., and T.
629 Lemon, "DHCP Option for Home Agent Discovery in Mobile
630 IPv6 (MIPv6)", <a href="./rfc6610">RFC 6610</a>, May 2012.
631
632 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
633
634 [<a id="ref-RFC3753">RFC3753</a>] Manner, J. and M. Kojo, "Mobility Related Terminology",
635 <a href="./rfc3753">RFC 3753</a>, June 2004.
636
637 [<a id="ref-RFC4301">RFC4301</a>] Kent, S. and K. Seo, "Security Architecture for the
638 Internet Protocol", <a href="./rfc4301">RFC 4301</a>, December 2005.
639
640 [<a id="ref-RFC4640">RFC4640</a>] Patel, A. and G. Giaretta, "Problem Statement for
641 bootstrapping Mobile IPv6 (MIPv6)", <a href="./rfc4640">RFC 4640</a>,
642 September 2006.
643
644 Authors' Addresses
645
646 Kuntal Chowdhury (editor)
647 Radio Mobile Access, Inc.
648 100 Ames Pond Dr.
649 Tewksbury MA 01876
650
651 EMail: [email protected]
652
653
654 Alper Yegin
655 Samsung
656 Istanbul
657 Turkey
658
659 EMail: [email protected]
660
661
662
663
664
665
666
667
668 Chowdhury &amp; Yegin Standards Track [Page 12]
669 </pre>