Mobile IPv6 Bootstrapping in Split Scenario
RFC 5026
| Document | Type |
RFC - Proposed Standard
(October 2007; No errata)
Updated by RFC 8553
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5026 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Jari Arkko | ||
| Send notices to | (None) | ||
Network Working Group G. Giaretta, Ed.
Request for Comments: 5026 Qualcomm
Category: Standards Track J. Kempf
DoCoMo Labs USA
V. Devarapalli, Ed.
Azaire Networks
October 2007
Mobile IPv6 Bootstrapping in Split Scenario
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract
A Mobile IPv6 node requires a Home Agent address, a home address, and
IPsec security associations with its Home Agent before it can start
utilizing Mobile IPv6 service. RFC 3775 requires that some or all of
these are statically configured. This document defines how a Mobile
IPv6 node can bootstrap this information from non-topological
information and security credentials pre-configured on the Mobile
Node. The solution defined in this document solves the split
scenario described in the Mobile IPv6 bootstrapping problem statement
in RFC 4640. The split scenario refers to the case where the Mobile
Node's mobility service is authorized by a different service provider
than basic network access. The solution described in this document
is also generically applicable to any bootstrapping case, since other
scenarios are more specific realizations of the split scenario.
Giaretta, et al. Standards Track [Page 1]
RFC 5026 MIP6 Bootstrapping in Split Scenario October 2007
Table of Contents
1. Introduction ....................................................3
2. Terminology .....................................................3
3. Split Scenario ..................................................4
4. Components of the Solution ......................................7
5. Protocol Operations .............................................9
5.1. Home Agent Address Discovery ...............................9
5.1.1. DNS Lookup by Home Agent Name ......................10
5.1.2. DNS Lookup by Service Name .........................10
5.2. IPsec Security Associations Setup .........................11
5.3. Home Address Assignment ...................................11
5.3.1. Home Address Assignment by the Home Agent ..........11
5.3.2. Home Address Auto-Configuration by the
Mobile Node ........................................12
5.4. Authorization and Authentication with MSA .................14
6. Home Address Registration in the DNS ...........................14
7. Summary of Bootstrapping Protocol Flow .........................16
8. Option and Attribute Format ....................................17
8.1. DNS Update Mobility Option ................................17
8.2. MIP6_HOME_PREFIX Attribute ................................19
9. Security Considerations ........................................20
9.1. HA Address Discovery ......................................20
9.2. Home Address Assignment through IKEv2 .....................22
9.3. SA Establishment Using EAP through IKEv2 ..................22
9.4. Backend Security between the HA and AAA Server ............22
9.5. Dynamic DNS Update ........................................23
10. IANA Considerations ...........................................24
11. Contributors ..................................................24
12. Acknowledgements ..............................................25
13. References ....................................................25
13.1. Normative References .....................................25
13.2. Informative References ...................................26
Giaretta, et al. Standards Track [Page 2]
RFC 5026 MIP6 Bootstrapping in Split Scenario October 2007
1. Introduction
Mobile IPv6 [1] requires the Mobile Node to know its Home Agent
Address, its own Home Address, and the cryptographic materials (e.g.,
shared keys or certificates) needed to set up IPsec security
associations with the Home Agent (HA) in order to protect Mobile IPv6
signaling. This is generally referred to as the Mobile IPv6
bootstrapping problem [7].
The Mobile IPv6 base protocol does not specify any method to
automatically acquire this information, which means that network
Show full document text