RFC 4651: A Taxonomy and Analysis of Enhancements to Mobile IPv6 Route Optimization
In plain English — editorial summary, not part of the RFC
This document describes and evaluates strategies to enhance Mobile IPv6 Route Optimization, on the basis of existing proposals, in order to motivate and guide further research in this context. This document is a product of the IP Mobility Optimizations (MobOpts) Research Group. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4651
- Published
- February 2007
- Authors
- C. Vogt; J. Arkko
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 31
- Also known as
- —
Topics
- Mobile IPv6
- Route Optimization
- Enhancement
- Mobility
- Handoff
- IP Address Tests
- Protected Tunnels
- Optimistic Behavior
- Proactive IP Address Tests
- Concurrent Care-of Address Tests
- Diverted Routing
- Credit-Based Authorization
- Heuristic Monitoring
- Crypto-Based Identifiers
- Pre-Configuration
- Semi-Permanent Security Associations
- Delegation
- Mobile Networks
- Location Privacy
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4866Enhanced Route Optimization for Mobile IPv6Current
May 2007
- RFC 5522Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile NetworksCurrent
October 2009
- RFC 6179The Internet Routing Overlay Network (IRON)Current
March 2011
- RFC 6252A Framework of Media-Independent Pre-Authentication (MPA) for Inter-Domain Handover OptimizationCurrent
June 2011
- RFC 4487Mobile IPv6 and Firewalls: Problem StatementCurrent
May 2006
- RFC 4980Analysis of Multihoming in Network Mobility SupportCurrent
October 2007
- RFC 5169Handover Key Management and Re-Authentication Problem StatementCurrent
March 2008
- RFC 5177Network Mobility (NEMO) Extensions for Mobile IPv4Updated
April 2008
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?