Hierarchical Mobile IPv6 (HMIPv6) Mobility Management
RFC 5380
| Document | Type |
RFC - Proposed Standard
(October 2008; No errata)
Obsoletes RFC 4140
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-soliman-mipshop-4140bis | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5380 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Jari Arkko | ||
| Send notices to | (None) | ||
Network Working Group H. Soliman
Request for Comments: 5380 Elevate Technologies
Obsoletes: 4140 C. Castelluccia
Category: Standards Track INRIA
K. ElMalki
Athonet
L. Bellier
INRIA
October 2008
Hierarchical Mobile IPv6 (HMIPv6) Mobility Management
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
This document introduces extensions to Mobile IPv6 and IPv6 Neighbour
Discovery to allow for local mobility handling. Hierarchical
mobility management for Mobile IPv6 is designed to reduce the amount
of signalling between the mobile node, its correspondent nodes, and
its home agent. The Mobility Anchor Point (MAP) described in this
document can also be used to improve the performance of Mobile IPv6
in terms of handover speed.
Soliman, et al. Standards Track [Page 1]
RFC 5380 HMIPv6 October 2008
Table of Contents
1. Introduction ....................................................3
2. Terminology .....................................................4
3. Overview of HMIPv6 ..............................................5
3.1. HMIPv6 Operations ..........................................6
4. Mobile IPv6 Extension - Local Binding Update ....................9
5. Neighbour Discovery Extension: The MAP Option ...................9
6. Protocol Operation .............................................10
6.1. Mobile Node Operation .....................................11
6.1.1. Sending Packets to Correspondent Nodes .............12
6.2. MAP Operations ............................................13
6.3. Home Agent Operations .....................................13
6.4. Correspondent Node Operations .............................13
6.5. Local Mobility Management Optimisation within a
MAP Domain ................................................14
6.6. Location Privacy ..........................................14
7. MAP Discovery ..................................................15
7.1. Mobile Node Operation .....................................15
8. Updating Previous MAPs .........................................16
9. Note on MAP Selection by the Mobile Node .......................16
9.1. MAP Selection in Distributed MAP Environment ..............17
9.2. MAP Selection in a Flat Mobility Architecture .............18
10. Detection and Recovery from MAP Failures ......................18
11. Tunelling Impacts on MTU ......................................19
12. Security Considerations .......................................19
12.1. Mobile Node - MAP Security ...............................20
12.2. Mobile Node - Correspondent Node Security ................22
12.3. Mobile Node - Home Agent Security ........................22
13. IANA Considerations ...........................................22
14. Acknowledgements ..............................................22
15. References ....................................................23
15.1. Normative References .....................................23
15.2. Informative References ...................................23
Appendix A. Changes from RFC 4140 .................................24
Soliman, et al. Standards Track [Page 2]
RFC 5380 HMIPv6 October 2008
1. Introduction
This specification introduces the concept of a hierarchical Mobile
IPv6 network, utilising a new node called the Mobility Anchor Point
(MAP).
Mobile IPv6 [RFC3775] allows nodes to move within the Internet
topology while maintaining reachability and ongoing connections
between mobile and correspondent nodes. To do this, a mobile node
sends binding updates (BUs) to its home agent (HA) every time it
moves.
The mobile node may send data packets via its home agent immediately
Show full document text