RFC 4140: Hierarchical Mobile IPv6 Mobility Management (HMIPv6)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5380.
Current version: RFC 5380 — Hierarchical Mobile IPv6 (HMIPv6) Mobility Management
In plain English — editorial summary, not part of the RFC
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. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4140
- Published
- August 2005
- Authors
- H. Soliman; C. Castelluccia; K. El Malki; L. Bellier
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 29
- Also known as
- —
- Obsoleted by:
- RFC 5380
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4429Optimistic Duplicate Address Detection (DAD) for IPv6Updated
April 2006
- RFC 4068Fast Handovers for Mobile IPv6Obsoleted
July 2005
- RFC 4291IP Version 6 Addressing ArchitectureUpdated
February 2006
- RFC 4294IPv6 Node RequirementsObsoleted
April 2006
- RFC 4311IPv6 Host-to-Router Load SharingCurrent
November 2005
- RFC 3769Requirements for IPv6 Prefix DelegationCurrent
June 2004
- RFC 4620IPv6 Node Information QueriesCurrent
August 2006
- RFC 4640Problem Statement for bootstrapping Mobile IPv6 (MIPv6)Current
September 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?