RFC 4640: Problem Statement for bootstrapping Mobile IPv6 (MIPv6)
In plain English — editorial summary, not part of the RFC
A mobile node needs at least the following information: a home address, a home agent address, and a security association with home agent to register with the home agent. The process of obtaining this information is called bootstrapping. This document discusses issues involved with how the mobile node can be bootstrapped for Mobile IPv6 (MIPv6) and various potential deployment scenarios for mobile node bootstrapping. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4640
- Published
- September 2006
- Authors
- A. Patel; G. Giaretta
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4068Fast Handovers for Mobile IPv6Obsoleted
July 2005
- RFC 4620IPv6 Node Information QueriesCurrent
August 2006
- RFC 4449Securing Mobile IPv6 Route Optimization Using a Static Shared KeyCurrent
June 2006
- RFC 4429Optimistic Duplicate Address Detection (DAD) for IPv6Updated
April 2006
- RFC 4862IPv6 Stateless Address AutoconfigurationUpdated
September 2007
- RFC 4944Transmission of IPv6 Packets over IEEE 802.15.4 NetworksUpdated
September 2007
- RFC 4311IPv6 Host-to-Router Load SharingCurrent
November 2005
- RFC 4294IPv6 Node RequirementsObsoleted
April 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?